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
Really late but.. what state is the TCP connection in? Can you take a wireshark/netmon trace on the machine running munin-node at the time the issue occurs and share it?
4949 stays in a listening state if munin-node dies under certain scenarios.
This does not happen often but when it does I need to restart the server running the node to get Munin-node to listen on 4949 correctly again.
Findings:
netstat -nao
TCP 0.0.0.0:4949 0.0.0.0:0 LISTENING 6000
taskkill /PID 6000 /F
ERROR: The process "6000" not found.
Possible solution to avoid endless waits on the socket:
http://msdn.microsoft.com/en-us/library/ms740476%28VS.85%29.aspx
The text was updated successfully, but these errors were encountered: