Passive check timestamp was corrupted
Posted: Thu May 06, 2021 7:23 pm
Hi,
Is there any possibility that the nagios will corrupt the passive check result line?
As explained at https://assets.nagios.com/downloads/nag ... hecks.html, the format should be
But I've found from a Nagios log line like
shows that the head of the line is truncated. And false alerts has come at the same time. That alerts says it occurred at epoch, 1970-01-01 00:00:03.
I don't think the external application writes such broken text to nagios.cmd since parsing it will fail before nagios triggers alerts. I wonder who broke the timestamp part inside Nagios.
Thanks.
Is there any possibility that the nagios will corrupt the passive check result line?
As explained at https://assets.nagios.com/downloads/nag ... hecks.html, the format should be
Code: Select all
[<timestamp>] PROCESS_SERVICE_CHECK_RESULT;...Code: Select all
3] PROCESS_SERVICE_CHECK_RESULT;...I don't think the external application writes such broken text to nagios.cmd since parsing it will fail before nagios triggers alerts. I wonder who broke the timestamp part inside Nagios.
Thanks.