nsca logging as error, ndo2db as debug
Posted: Wed Feb 11, 2015 6:08 am
Hello,
After installing the NLS agent for Linux on my Nagios XI server, it seems like nsca is logging every connection to /var/log/messages with a severity as 'error',even if there does not seem to be an error. Is this 'normal' behaviour. Shouldn't these messages be logged with an informational level, as it kind of makes searching for 'real errors' harder and is causing a non-necessary flow of error severity levels events.
For each message sent over nsca to Nagios XI, it seems NSCA makes three log entries with the exact same datestamp:
Time difference in packet: 0 seconds for host <hostname>
Attempting to write to nagios command pipe
End of connection...
I have no problem with these events being logged, but why are they logged as error? Maybe it should be an error / warning level event if something would not work as expected, or if the time difference would be too high or if it was unable to write to Nagios command pipe.
Another thing I noticed was that ndo2db seems to log an event as debug for every connection and disconnection made to mysql database.
Successfully connected to MySQL database
Successfully disconnected from MySQL database
I would suspect debug is something set when explicitly troubleshooting? Could it be that deugging is somewhere enabled where it shouldn't in ndo2db config?
Thoughts?
Willem
After installing the NLS agent for Linux on my Nagios XI server, it seems like nsca is logging every connection to /var/log/messages with a severity as 'error',even if there does not seem to be an error. Is this 'normal' behaviour. Shouldn't these messages be logged with an informational level, as it kind of makes searching for 'real errors' harder and is causing a non-necessary flow of error severity levels events.
For each message sent over nsca to Nagios XI, it seems NSCA makes three log entries with the exact same datestamp:
Time difference in packet: 0 seconds for host <hostname>
Attempting to write to nagios command pipe
End of connection...
I have no problem with these events being logged, but why are they logged as error? Maybe it should be an error / warning level event if something would not work as expected, or if the time difference would be too high or if it was unable to write to Nagios command pipe.
Another thing I noticed was that ndo2db seems to log an event as debug for every connection and disconnection made to mysql database.
Successfully connected to MySQL database
Successfully disconnected from MySQL database
I would suspect debug is something set when explicitly troubleshooting? Could it be that deugging is somewhere enabled where it shouldn't in ndo2db config?
Thoughts?
Willem