-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[chrony] unix socket connection is broken #15549
Labels
bug
unexpected problem or unintended behavior
Comments
Frankkkkk
added a commit
to Frankkkkk/telegraf
that referenced
this issue
Jun 21, 2024
We must use the DGRAM type when connecting to the chrony socket. On top of that, the socket must be duplicated in order to allow concurrent calls to it. Fixes influxdata#15549 Signed-off-by: Frank Villaro-Dixon <[email protected]>
1 task
Frankkkkk
added a commit
to Frankkkkk/telegraf
that referenced
this issue
Jun 21, 2024
We must use the DGRAM type when connecting to the chrony socket. On top of that, the socket must be duplicated in order to allow concurrent calls to it. Fixes influxdata#15549 Signed-off-by: Frank Villaro-Dixon <[email protected]>
Frankkkkk
added a commit
to Frankkkkk/telegraf
that referenced
this issue
Jun 23, 2024
We must use the DGRAM type when connecting to the chrony socket. On top of that, the socket must be duplicated in order to allow concurrent calls to it. Fixes influxdata#15549 Signed-off-by: Frank Villaro-Dixon <[email protected]>
Frankkkkk
added a commit
to Frankkkkk/telegraf
that referenced
this issue
Jun 24, 2024
We must use the DGRAM type when connecting to the chrony socket. On top of that, the socket must be duplicated in order to allow concurrent calls to it. Fixes influxdata#15549 Signed-off-by: Frank Villaro-Dixon <[email protected]>
Frankkkkk
added a commit
to Frankkkkk/telegraf
that referenced
this issue
Jun 24, 2024
We must use the DGRAM type when connecting to the chrony socket. On top of that, the socket must be duplicated in order to allow concurrent calls to it. Fixes influxdata#15549 Signed-off-by: Frank Villaro-Dixon <[email protected]>
Frankkkkk
added a commit
to Frankkkkk/telegraf
that referenced
this issue
Jun 24, 2024
We must use the DGRAM type when connecting to the chrony socket. On top of that, the socket must be duplicated in order to allow concurrent calls to it. Fixes influxdata#15549 Signed-off-by: Frank Villaro-Dixon <[email protected]>
Thanks for the various issues and PRs next steps: review PR |
Frankkkkk
added a commit
to Frankkkkk/telegraf
that referenced
this issue
Jun 25, 2024
We must use the DGRAM type when connecting to the chrony socket. On top of that, the socket must be duplicated in order to allow concurrent calls to it. Fixes influxdata#15549 Signed-off-by: Frank Villaro-Dixon <[email protected]>
Frankkkkk
added a commit
to Frankkkkk/telegraf
that referenced
this issue
Jun 25, 2024
We must use the DGRAM type when connecting to the chrony socket. On top of that, the socket must be duplicated in order to allow concurrent calls to it. Fixes influxdata#15549 Signed-off-by: Frank Villaro-Dixon <[email protected]>
Frankkkkk
added a commit
to Frankkkkk/telegraf
that referenced
this issue
Jun 26, 2024
Chrony ≥ 4.4 introduces a new ServerStats response with u64 numbers and more fields. Fixes influxdata#15553 NB: The plugin still doesn't work due to influxdata#15549. To test this commit, please make sure you use influxdata#15552. Signed-off-by: Frank Villaro-Dixon <[email protected]>
1 task
Frankkkkk
added a commit
to Frankkkkk/telegraf
that referenced
this issue
Jun 27, 2024
Chrony ≥ 4.4 introduces a new ServerStats response with u64 numbers and more fields. Fixes influxdata#15553 NB: The plugin still doesn't work due to influxdata#15549. To test this commit, please make sure you use influxdata#15552. Signed-off-by: Frank Villaro-Dixon <[email protected]> Signed-off-by: Frank Villaro-Dixon <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Relevant telegraf.conf
Logs from Telegraf
System info
1.13 - 78cbf53
Docker
No response
Steps to reproduce
unix:///var/run/chrony/chronyd.sock
Expected behavior
The chrony plugin should work
Actual behavior
The plugin hangs when using the unix socket when:
The reasons are two fold:
unixgram
) unix socket and not stream (unix
) ones.Here is a working example by facebook
Additional info
I guess this is hard to reproduce, because the unix socket is rarely used as telegraf cannot talk to it (thus it instead connects via UDP to the chrony deamon).
The unix socket is however needed to access the
serverstats
metrics. Most of the other ones can be reached using the udp socket.The text was updated successfully, but these errors were encountered: