upgrade to 4.0.8, cgis not working
Posted: Fri May 08, 2015 2:03 pm
I'm getting the common error
The config test runs clean. The service starts up, and I see it logging some soft warnings on a few hosts, which is usual.
I'm not seeing errors in the apache log about permissions. Googling and checking things others have run into has not produced
a good lead into resolving the error.
Here is the tail of my nagios.log:
after upgrade from 3.5.1 to 4.0.8Whoops!
Error: Could not read host and service status information!
The config test runs clean. The service starts up, and I see it logging some soft warnings on a few hosts, which is usual.
I'm not seeing errors in the apache log about permissions. Googling and checking things others have run into has not produced
a good lead into resolving the error.
Here is the tail of my nagios.log:
Code: Select all
[1431110979] Event broker module 'NERD' deinitialized successfully.
[1431110982] Nagios 4.0.8 starting... (PID=17302)
[1431110982] Local time is Fri May 08 15:49:42 ADT 2015
[1431110982] LOG VERSION: 2.0
[1431110982] qh: Socket '/usr/local/nagios/var/rw/query.sh' successfully initialized
[1431110982] qh: core query handler registered
[1431110982] nerd: Channel hostchecks registered successfully
[1431110982] nerd: Channel servicechecks registered successfully
[1431110982] nerd: Channel opathchecks registered successfully
[1431110982] nerd: Fully initialized and ready to rock!
[1431110982] wproc: Successfully registered manager as @wproc with query handler
[1431110982] wproc: Registry request: name=Core Worker 17304;pid=17304
[1431110982] wproc: Registry request: name=Core Worker 17305;pid=17305
[1431110982] wproc: Registry request: name=Core Worker 17306;pid=17306
[1431110982] wproc: Registry request: name=Core Worker 17308;pid=17308
[1431110982] wproc: Registry request: name=Core Worker 17307;pid=17307
[1431110982] wproc: Registry request: name=Core Worker 17309;pid=17309
[1431110982] Successfully launched command file worker with pid 17310
[1431111000] SERVICE ALERT: divinity-1.mydomain.com;PING;WARNING;SOFT;1;PING WARNING - Packet loss = 0%, RTA = 134.74 ms
[1431111052] SERVICE ALERT: jodreyhall-429-3.mydomain.com;PING;WARNING;SOFT;1;PING WARNING - Packet loss = 28%, RTA = 3.22 ms
[1431111060] SERVICE ALERT: divinity-1.mydomain.com;PING;OK;SOFT;2;PING OK - Packet loss = 0%, RTA = 21.18 ms
[1431111110] SERVICE ALERT: jodreyhall-429-3.mydomain.com;PING;OK;SOFT;2;PING OK - Packet loss = 0%, RTA = 1.57 ms
[1431111262] HOST ALERT: uhall-169-gig1.mydomain.com;DOWN;SOFT;1;PING CRITICAL - Packet loss = 16%, RTA = 241.13 ms
[1431111309] HOST ALERT: uhall-169-gig1.mydomain.com;UP;SOFT;2;PING OK - Packet loss = 0%, RTA = 1.34 ms
[1431111356] SERVICE ALERT: dennis-449-gig1.mydomain.com;PING;WARNING;SOFT;1;PING WARNING - Packet loss = 0%, RTA = 104.46 ms
[1431111362] SERVICE ALERT: chase-a3.mydomain.com;PING;WARNING;SOFT;1;PING WARNING - Packet loss = 16%, RTA = 37.72 ms
[1431111416] SERVICE ALERT: dennis-449-gig1.mydomain.com;PING;OK;SOFT;2;PING OK - Packet loss = 0%, RTA = 1.10 ms
[1431111421] SERVICE ALERT: chase-a3.mydomain.com;PING;OK;SOFT;2;PING OK - Packet loss = 0%, RTA = 2.09 ms