Since Nagios XI upgrade to version 5.4.11 nagios service occasionally hangs after SIGHUP signal observed in /var/log/nagios.log. Then no service/host check is processed and monitoring is not available.
A restart of the nagios service fix the issue.
2017-12-02T21:58:41.918330+00:00 nagxi-01 nagios: Caught SIGHUP, restarting...
2017-12-02T21:58:43.711262+00:00 nagxi-01 nagios: Event broker module 'NERD' deinitialized successfully.
2017-12-02T21:58:43.711299+00:00 nagxi-01 nagios: ndomod: Shutdown complete.
2017-12-02T21:58:43.711305+00:00 nagxi-01 nagios: Event broker module '/usr/local/nagios/bin/ndomod.o' deinitialized successfully.
2017-12-02T21:58:43.775619+00:00 nagxi-01 nagios: Nagios 4.2.4 starting... (PID=24106)
2017-12-02T21:58:43.778623+00:00 nagxi-01 nagios: Local time is Sat Dec 02 21:58:43 UTC 2017
2017-12-02T21:58:43.778645+00:00 nagxi-01 nagios: LOG VERSION: 2.0
2017-12-02T21:58:43.778650+00:00 nagxi-01 nagios: qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
2017-12-02T21:58:43.778654+00:00 nagxi-01 nagios: qh: core query handler registered
2017-12-02T21:58:43.778659+00:00 nagxi-01 nagios: nerd: Channel hostchecks registered successfully
2017-12-02T21:58:43.778663+00:00 nagxi-01 nagios: nerd: Channel servicechecks registered successfully
2017-12-02T21:58:43.778667+00:00 nagxi-01 nagios: nerd: Channel opathchecks registered successfully
2017-12-02T21:58:43.778671+00:00 nagxi-01 nagios: nerd: Fully initialized and ready to rock!
2017-12-02T21:58:43.778675+00:00 nagxi-01 nagios: wproc: Successfully registered manager as @wproc with query handler
while the following is expected after:
2017-12-04T05:28:39.774755+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30589;pid=30589
2017-12-04T05:28:39.778973+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30590;pid=30590
2017-12-04T05:28:39.782604+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30591;pid=30591
2017-12-04T05:28:39.782640+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30592;pid=30592
2017-12-04T05:28:39.782646+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30596;pid=30596
2017-12-04T05:28:39.782916+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30593;pid=30593
2017-12-04T05:28:39.783735+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30600;pid=30600
2017-12-04T05:28:39.784334+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30594;pid=30594
2017-12-04T05:28:39.786160+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30597;pid=30597
2017-12-04T05:28:39.786183+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30598;pid=30598
2017-12-04T05:28:39.786188+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30601;pid=30601
2017-12-04T05:28:39.786201+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30603;pid=30603
2017-12-04T05:28:39.786208+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30595;pid=30595
2017-12-04T05:28:39.787030+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30602;pid=30602
2017-12-04T05:28:39.787061+00:00 nagxi-01 nagios: wproc: Registry request: name=Core Worker 30599;pid=30599
2017-12-04T05:28:39.789204+00:00 nagxi-01 nagios: ndomod: NDOMOD 2.1.2 (11-14-2016) Copyright (c) 2009 Nagios Core Development Team and Community Contributors
2017-12-04T05:28:39.789226+00:00 nagxi-01 nagios: ndomod: Successfully connected to data sink. 0 queued items to flush.2017-12-04T05:28:39.789239+00:00 nagxi-01 nagios: ndomod registered for process data
2017-12-04T05:28:39.789246+00:00 nagxi-01 nagios: ndomod registered for log data'
2017-12-04T05:28:39.789251+00:00 nagxi-01 nagios: ndomod registered for system command data'
2017-12-04T05:28:39.789255+00:00 nagxi-01 nagios: ndomod registered for event handler data'
2017-12-04T05:28:39.789261+00:00 nagxi-01 nagios: ndomod registered for notification data'
2017-12-04T05:28:39.789265+00:00 nagxi-01 nagios: ndomod registered for comment data'
2017-12-04T05:28:39.789269+00:00 nagxi-01 nagios: ndomod registered for downtime data'
2017-12-04T05:28:39.789273+00:00 nagxi-01 nagios: ndomod registered for flapping data'
2017-12-04T05:28:39.789277+00:00 nagxi-01 nagios: ndomod registered for program status data'
2017-12-04T05:28:39.789550+00:00 nagxi-01 nagios: ndomod registered for host status data'
2017-12-04T05:28:39.789569+00:00 nagxi-01 nagios: ndomod registered for service status data'
2017-12-04T05:28:39.789574+00:00 nagxi-01 nagios: ndomod registered for adaptive program data'
2017-12-04T05:28:39.789578+00:00 nagxi-01 nagios: ndomod registered for adaptive host data'
2017-12-04T05:28:39.789582+00:00 nagxi-01 nagios: ndomod registered for adaptive service data'
2017-12-04T05:28:39.789586+00:00 nagxi-01 nagios: ndomod registered for external command data'
2017-12-04T05:28:39.789590+00:00 nagxi-01 nagios: ndomod registered for aggregated status data'
2017-12-04T05:28:39.789594+00:00 nagxi-01 nagios: ndomod registered for retention data'
2017-12-04T05:28:39.789598+00:00 nagxi-01 nagios: ndomod registered for contact data'
2017-12-04T05:28:39.789602+00:00 nagxi-01 nagios: ndomod registered for contact notification data'
2017-12-04T05:28:39.789606+00:00 nagxi-01 nagios: ndomod registered for acknowledgement data'
2017-12-04T05:28:39.791410+00:00 nagxi-01 nagios: ndomod registered for state change data'
2017-12-04T05:28:39.791423+00:00 nagxi-01 nagios: ndomod registered for contact status data'
2017-12-04T05:28:39.791427+00:00 nagxi-01 nagios: ndomod registered for adaptive contact data'
2017-12-04T05:28:39.791432+00:00 nagxi-01 nagios: Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
Nagios XI 5.4.11 hangs
Re: Nagios XI 5.4.11 hangs
I stumbled onto this thread which seems to suggest that Nagios core 4.3.4 will resolve my issue.
https://github.com/NagiosEnterprises/na ... diff=split
Looking at the changelog, Nagios core 4.3.4 is not included in NagiosXI 5.4.13 (I am currently on 5.4.11). Does that mean i would have to do a manual upgrade for the Nagios core from my current 4.2.4 to the 4.3.4 if I want to test the solution?
https://github.com/NagiosEnterprises/na ... diff=split
Looking at the changelog, Nagios core 4.3.4 is not included in NagiosXI 5.4.13 (I am currently on 5.4.11). Does that mean i would have to do a manual upgrade for the Nagios core from my current 4.2.4 to the 4.3.4 if I want to test the solution?
Re: Nagios XI 5.4.11 hangs
Upgrading the Nagios Core engine in XI is not supported. I would recommend waiting until Nagios XI 5.5 is out.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Nagios XI 5.4.11 hangs
Thanks for the info!
Re: Nagios XI 5.4.11 hangs
You are welcome! I am locking this topic. If you have any more questions/issues, please start a new thread.
Be sure to check out our Knowledgebase for helpful articles and solutions!