but my guess is, in the " check_haproxy --help " it says:
-S, --socket /path/to/socket
Path to the socket check_haproxy should connect to (requires
read/write permissions and must be at least user level; no operator
or admin privileges needed).
I assumed that the root:root of the /var/run/haproxy.sock socket was the problem, but it’s rwx for world.
Correct me if I’m wrong, but unix sockets are only accessible on localhost eq. on the same machine.
Data sent through these sockets are handled entirely inside the kernel and not accessible via network.
Unless your LibreNMS runs on the same host it is expected behaviour.
Yes, because your LibreNMS host does not have haproxy, hence no socket to connect to.
Maybe @laf can chime in, and explain better how to get this work.
I think you would need somekind of script (not sure if LibreNMS has one already) on a remote host, which makes poller aware of such remote service.