socket-udp mode not working

[sosop]

A note for the community

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Problem

Sinks is using socket-udp mode, after some time its not working anymore, after restarting vector the mode is working fine again. Please tell me what is going on and how to solve this problem.

Configuration

sources:
safety_log:
type: "socket"
mode: udp
address: 127.0.0.1:6604

transforms:
addmetadata:
type: remap
inputs: ["safety_log"]
source: |-
.id = "xxxx"

sinks:
console:
type: console
inputs:
- addmetadata
encoding:
codec: json

remote:
encoding:
codec: json
type: socket
inputs:
- addmetadata
mode: udp
address: test.com:4590

Version

0.37.0

Debug Output

No response

Example Data

No response

Additional Context

No response

References

No response

[jszwedko]

Hi @sosop ,

Thanks for this report. It is going to be difficult to troubleshoot an issue like this without additional details. Do you mind filling in the other fields mentioned in the issue template? Even better if you can provide a reproduction case.

[sosop]

Hi @sosop ,

Thanks for this report. It is going to be difficult to troubleshoot an issue like this without additional details. Do you mind filling in the other fields mentioned in the issue template? Even better if you can provide a reproduction case.

thanks

sources:
safety_log:
type: "socket"
mode: udp
address: 127.0.0.1:6604

transforms:
addmetadata:
type: remap
inputs: ["safety_log"]
source: |-
.id = "xxxx"

sinks:
console:
type: console
inputs:
- addmetadata
encoding:
codec: json

remote:
encoding:
codec: json
type: socket
inputs:
- addmetadata
mode: udp
address: test.com:4590

[pront]

We are still lacking key info here.

• Do you see any warnings or errors?
• How long are you running this config?
• Did you check if the sockets are still open when this starts happening?
• Do you have a sample source log?
• You can also turn on inspect internal telemetry and see what's going on there

[taikula-8]

The vector service has been running for about a month or so, and from the log messages, there are no warnings or error logs, before restarting the vector service, we used the nc command to check the destination address and port, and it is fine. vector will there be a number of attempts again, and then found that the network is not available, and the subsequent direct deprecation of the sinks? vector's startup commands The startup commands for vector are as follows:

vector -w --allow-empty-config -C /etc/vector

[pront]

Thank you, I appreciate the extra context!

Based on the new info, I don't have any guesses. It is quite challenging to get to the bottom of this since I cannot replicate your environment and it happens after running the process for a very long time.

The vector service has been running for about a month or so

Do you restart the process on an interval?