You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When trying to connect to chronyd via the unix socket, the wrong unix socket type was used meaning that they were unable to communicate.
Steps to reproduce
If possible, provide a recipe for reproducing the error.
Having chronyd running on the same domain
configure chrony reciever to read from socket
run receiver
What did you expect to see?
A clear and concise description of what you expected to see.
Data should be captured from the receiver and be visible via a configured exporter.
What did you see instead?
A clear and concise description of what you saw instead.
The receiver fails to capture data.
What version did you use?
Version: v0.58.0
What config did you use?
Config:
receivers:
chrony:
endpoint: "unix://var/run/chrony/chrony.sock# The rest is ignored because it should be enough to reproduce.
Describe the bug
When trying to connect to chronyd via the unix socket, the wrong unix socket type was used meaning that they were unable to communicate.
Steps to reproduce
If possible, provide a recipe for reproducing the error.
What did you expect to see?
A clear and concise description of what you expected to see.
Data should be captured from the receiver and be visible via a configured exporter.
What did you see instead?
A clear and concise description of what you saw instead.
The receiver fails to capture data.
What version did you use?
Version: v0.58.0
What config did you use?
Config:
Environment
OS: MacOS
Compiler(if manually compiled): go.1.19
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: