Nagios Support Forum

Yes, after removing the comma in the service description, everything in Nagios is working normally. The new server starting with c is in the configs and being checked and reported as expected. The nagios -v nagios.cfg never threw any errors when the cgi's were broken, but this is because one of our ...

Nevermind, I just figured this out. We had a service description with a comma in it. The new server I added was the first server alphabetically for this service as long as it started with 1-9, a, b, c. For some reason the CGIs will work fine with commas in service descriptions as long as the FIRST s...

Sorry for the long delay, I had the server reimaged to make sure it wasn't a filesystem thing. The same error is still occuring after a fresh imaging. Nagios.log contents: $ cat nagios.log [1467833213] Nagios 4.1.1 starting... (PID=4348) [1467833213] Local time is Wed Jul 06 12:26:53 PDT 2016 [14678...

This is going to be tough to explain, but bear with me. I've been using Nagios 4.1.1 for quite a while to monitor some servers. Recently I added a couple new servers to the config files and I noticed that the nagios website started reporting that nagios wasn't running, even though it clearly was, an...