Nagios Support Forum

Lock it up.
Thank you.

Thank you, that seems to have done the trick.

Stopped the service. There was no status.dat but a retention.dat

Looks good!
Thanks a lot!

Oh, I forgot to say that the problem still persists ...

I deleted files, wrote config and verified/applied. There were some minor issues which I corrected (check interval > notification interval). Then I rebooted the server to male sure it has a clean start. Then I ran ps aux | grep nagios with the following output: [root@nagios ~]# ps aux | grep nagios ...

I upgraded to 5.5.1 - the problem persists. In the meantime I removed every trace of the old command from the database. I just don't understand how Nagios 'remembers' a command I used 7 days ago. To me it looks like Nagios queries NSClient with an 'old' command it 'remembers' instead of looking in i...

There is no error in the nsclient.log. The error is the same error it showed before I changed the command syntax. Invalid command line: unrecognised option ... As I said, once I force a check the error is gone. Status switches to ok. If I don't check unknown will go away some time and come back later.

So Nagios 5.5 doesn't like NSClient 0.3.9 anymore. Fine. We move on to 0.5.2. Now it says: Invalid command line: unrecognised option ... Ok, I have to reconstruct the Command (reading Windows Backup entries from the eventlog). Some hours later it's working. But, and here is my grievance, every now a...