Nagios shuts down immediately after launching Core Worker
Posted: Fri Aug 21, 2015 10:46 am
I've installed Nagios, but when I try to start it from /etc/init.d/nagios reload or /etc/init.d/nagios start it ultimately fails. It occurs each time, "Caught SIGSEGV, shutting down...", within a few seconds of trying to start. I've reviewed the ownership of the directories and all are set to nagios:nagios for my nagios install at /data/local/nagios-4.1.
Output is as follows:
[1440171255] Nagios 4.1.0rc1 starting... (PID=22689)
[1440171255] Local time is Fri Aug 21 11:34:15 EDT 2015
[1440171255] LOG VERSION: 2.0
[1440171255] qh: Socket '/data/local/nagios-4.1/var/rw/nagios.qh' successfully initialized
[1440171255] qh: core query handler registered
[1440171255] nerd: Channel hostchecks registered successfully
[1440171255] nerd: Channel servicechecks registered successfully
[1440171255] nerd: Channel opathchecks registered successfully
[1440171255] nerd: Fully initialized and ready to rock!
[1440171255] wproc: Successfully registered manager as @wproc with query handler
[1440171255] wproc: Registry request: name=Core Worker 22693;pid=22693
[1440171255] wproc: Registry request: name=Core Worker 22690;pid=22690
[1440171255] wproc: Registry request: name=Core Worker 22694;pid=22694
[1440171255] wproc: Registry request: name=Core Worker 22695;pid=22695
[1440171255] wproc: Registry request: name=Core Worker 22696;pid=22696
[1440171255] wproc: Registry request: name=Core Worker 22697;pid=22697
[1440171255] wproc: Registry request: name=Core Worker 22698;pid=22698
[1440171256] Successfully launched command file worker with pid 22723
[1440171256] wproc: CHECK job 0 from worker Core Worker 22693 died by signal 9 after 0.01 seconds
[1440171256] Caught SIGSEGV, shutting down...
Anyone else experience this?
Output is as follows:
[1440171255] Nagios 4.1.0rc1 starting... (PID=22689)
[1440171255] Local time is Fri Aug 21 11:34:15 EDT 2015
[1440171255] LOG VERSION: 2.0
[1440171255] qh: Socket '/data/local/nagios-4.1/var/rw/nagios.qh' successfully initialized
[1440171255] qh: core query handler registered
[1440171255] nerd: Channel hostchecks registered successfully
[1440171255] nerd: Channel servicechecks registered successfully
[1440171255] nerd: Channel opathchecks registered successfully
[1440171255] nerd: Fully initialized and ready to rock!
[1440171255] wproc: Successfully registered manager as @wproc with query handler
[1440171255] wproc: Registry request: name=Core Worker 22693;pid=22693
[1440171255] wproc: Registry request: name=Core Worker 22690;pid=22690
[1440171255] wproc: Registry request: name=Core Worker 22694;pid=22694
[1440171255] wproc: Registry request: name=Core Worker 22695;pid=22695
[1440171255] wproc: Registry request: name=Core Worker 22696;pid=22696
[1440171255] wproc: Registry request: name=Core Worker 22697;pid=22697
[1440171255] wproc: Registry request: name=Core Worker 22698;pid=22698
[1440171256] Successfully launched command file worker with pid 22723
[1440171256] wproc: CHECK job 0 from worker Core Worker 22693 died by signal 9 after 0.01 seconds
[1440171256] Caught SIGSEGV, shutting down...
Anyone else experience this?