Page 1 of 1

Scheduled downtime SIGSEGV

Posted: Sat Nov 26, 2016 6:02 am
by kobazik
Hi,

I'm experiencing random nagios crashes.

Code: Select all

[Sat Nov 26 01:00:02 2016] HOST DOWNTIME ALERT: SRV1;STOPPED; Host has exited from a period of scheduled downtime
[Sat Nov 26 01:00:02 2016] HOST DOWNTIME ALERT: SRV2;STOPPED; Host has exited from a period of scheduled downtime
[Sat Nov 26 01:00:02 2016] HOST DOWNTIME ALERT: SRV3;STOPPED; Host has exited from a period of scheduled downtime
[Sat Nov 26 01:00:02 2016] HOST DOWNTIME ALERT: SRV4;STOPPED; Host has exited from a period of scheduled downtime
[Sat Nov 26 01:00:02 2016] HOST DOWNTIME ALERT: SRV5;STOPPED; Host has exited from a period of scheduled downtime
[Sat Nov 26 01:00:02 2016] HOST DOWNTIME ALERT: SRV6;STOPPED; Host has exited from a period of scheduled downtime
[Sat Nov 26 01:00:02 2016] HOST DOWNTIME ALERT: SRV7;STOPPED; Host has exited from a period of scheduled downtime
[Sat Nov 26 01:00:02 2016] HOST DOWNTIME ALERT: SRV8;STOPPED; Host has exited from a period of scheduled downtime
[Sat Nov 26 01:00:02 2016] HOST DOWNTIME ALERT: SRV9;STOPPED; Host has exited from a period of scheduled downtime
[Sat Nov 26 01:00:02 2016] Caught SIGSEGV, shutting down...
[Sat Nov 26 01:17:24 2016] Nagios 4.1.1 starting... (PID=20396)
[Sat Nov 26 01:17:24 2016] Local time is Sat Nov 26 01:17:24 GMT 2016
[Sat Nov 26 01:17:24 2016] LOG VERSION: 2.0
[Sat Nov 26 01:17:24 2016] qh: Socket '/var/nagios/rw/nagios.qh' successfully initialized
[Sat Nov 26 01:17:24 2016] qh: core query handler registered
[Sat Nov 26 01:17:24 2016] nerd: Channel hostchecks registered successfully
[Sat Nov 26 01:17:24 2016] nerd: Channel servicechecks registered successfully
[Sat Nov 26 01:17:24 2016] nerd: Channel opathchecks registered successfully
[Sat Nov 26 01:17:24 2016] nerd: Fully initialized and ready to rock!
[Sat Nov 26 01:17:24 2016] wproc: Successfully registered manager as @wproc with query handler
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20398;pid=20398
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20400;pid=20400
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20399;pid=20399
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20403;pid=20403
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20401;pid=20401
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20402;pid=20402
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20405;pid=20405
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20404;pid=20404
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20407;pid=20407
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20406;pid=20406
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20408;pid=20408
[Sat Nov 26 01:17:24 2016] wproc: Registry request: name=Core Worker 20409;pid=20409
[Sat Nov 26 01:17:24 2016] livestatus: Livestatus 1.2.6p16 by Mathias Kettner. Socket: '/var/nagios/rw/live'
[Sat Nov 26 01:17:24 2016] livestatus: Please visit us at http://mathias-kettner.de/
[Sat Nov 26 01:17:24 2016] livestatus: Hint: please try out OMD - the Open Monitoring Distribution
[Sat Nov 26 01:17:24 2016] livestatus: Please visit OMD at http://omdistro.org
[Sat Nov 26 01:17:24 2016] livestatus: Removed old left over socket file /var/nagios/rw/live
[Sat Nov 26 01:17:24 2016] livestatus: Finished initialization. Further log messages go to /var/log/nagios/livestatus.log
[Sat Nov 26 01:17:24 2016] Event broker module '/usr/local/lib/mk-livestatus/livestatus.o' initialized successfully.
[Sat Nov 26 01:17:24 2016] mod_gearman: initialized version 2.1.2 (libgearman 0.33)
[Sat Nov 26 01:17:24 2016] Event broker module '/usr/lib64/mod_gearman2/mod_gearman2.o' initialized successfully.
Is there is any known bug in combination of nagios , livestatus and mod_gearman versions I'm using?

Thanks

Dom

Re: Scheduled downtime SIGSEGV

Posted: Mon Nov 28, 2016 2:55 pm
by rkennedy
mk_livestatus is not our product, and as NEB modules can definitely affect how Nagios will operate - I would contact them for Support.