ndoutils constantly deinitializes
Posted: Thu May 31, 2018 8:48 am
It seems like one of your old topics has not been resolved "ndoutils constantly deinitializes --- https://support.nagios.com/forum/viewto ... =7&t=45243" causing a SIGTERM.
As requested in the Subject mentioned above I did a tail -100 /var/log/messages see output below:
May 31 09:17:11 <Server Name>dbus[806]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
May 31 09:17:11 <Server Name>dbus-daemon: dbus[806]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
May 31 09:17:11 <Server Name>dbus[806]: [system] Activated service 'org.freedesktop.problems' failed: Process /lib64/dbus-1/dbus-daemon-launch-helper received signal 9
May 31 09:17:11 <Server Name>dbus-daemon: dbus[806]: [system] Activated service 'org.freedesktop.problems' failed: Process /lib64/dbus-1/dbus-daemon-launch-helper received signal 9
May 31 09:17:11 <Server Name>xinetd[1102]: START: nrpe pid=1330 from=::ffff:10.61.164.115
May 31 09:17:11 <Server Name>xinetd[1330]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:17:11 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1330 duration=0(sec)
May 31 09:17:22 <Server Name>xinetd[1102]: START: nrpe pid=1368 from=::ffff:10.61.164.115
May 31 09:17:22 <Server Name>xinetd[1368]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:17:22 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1368 duration=0(sec)
May 31 09:17:26 <Server Name>ndo2db: Trimming timedevents.
May 31 09:17:26 <Server Name>ndo2db: Trimming timedevents.
May 31 09:17:26 <Server Name>ndo2db: Trimming systemcommands.
May 31 09:17:26 <Server Name>ndo2db: Trimming systemcommands.
May 31 09:17:26 <Server Name>ndo2db: Trimming servicechecks.
May 31 09:17:26 <Server Name>ndo2db: Trimming servicechecks.
May 31 09:17:26 <Server Name>ndo2db: Trimming hostchecks.
May 31 09:17:26 <Server Name>ndo2db: Trimming eventhandlers.
May 31 09:17:26 <Server Name>ndo2db: Trimming hostchecks.
May 31 09:17:26 <Server Name>ndo2db: Trimming eventhandlers.
May 31 09:17:36 <Server Name>xinetd[1102]: START: nrpe pid=1431 from=::ffff:10.61.164.115
May 31 09:17:36 <Server Name>xinetd[1431]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:17:36 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1431 duration=0(sec)
May 31 09:18:12 <Server Name>xinetd[1102]: START: nrpe pid=1672 from=::ffff:10.61.164.115
May 31 09:18:12 <Server Name>xinetd[1672]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:18:12 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1672 duration=0(sec)
May 31 09:18:19 <Server Name>xinetd[1102]: START: nrpe pid=1682 from=::ffff:10.61.164.115
May 31 09:18:19 <Server Name>xinetd[1682]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:18:19 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1682 duration=0(sec)
May 31 09:18:29 <Server Name>ndo2db: Trimming timedevents.
May 31 09:18:29 <Server Name>ndo2db: Trimming timedevents.
May 31 09:18:29 <Server Name>ndo2db: Trimming systemcommands.
May 31 09:18:29 <Server Name>ndo2db: Trimming systemcommands.
May 31 09:18:29 <Server Name>ndo2db: Trimming servicechecks.
May 31 09:18:29 <Server Name>ndo2db: Trimming servicechecks.
May 31 09:18:29 <Server Name>ndo2db: Trimming hostchecks.
May 31 09:18:29 <Server Name>ndo2db: Trimming hostchecks.
May 31 09:18:29 <Server Name>ndo2db: Trimming eventhandlers.
May 31 09:18:29 <Server Name>ndo2db: Trimming eventhandlers.
May 31 09:18:33 <Server Name>xinetd[1102]: START: nrpe pid=1757 from=::ffff:10.61.164.115
May 31 09:18:33 <Server Name>xinetd[1757]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:18:33 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1757 duration=0(sec)
The reinitiating of ndoutils causes us even a bigger problem because we are trying to configure master-slave replication. this issue generates an error on the slave database.
Also is there any special configuration parameters for ndo2db.cfg when doing database replication.
As requested in the Subject mentioned above I did a tail -100 /var/log/messages see output below:
May 31 09:17:11 <Server Name>dbus[806]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
May 31 09:17:11 <Server Name>dbus-daemon: dbus[806]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
May 31 09:17:11 <Server Name>dbus[806]: [system] Activated service 'org.freedesktop.problems' failed: Process /lib64/dbus-1/dbus-daemon-launch-helper received signal 9
May 31 09:17:11 <Server Name>dbus-daemon: dbus[806]: [system] Activated service 'org.freedesktop.problems' failed: Process /lib64/dbus-1/dbus-daemon-launch-helper received signal 9
May 31 09:17:11 <Server Name>xinetd[1102]: START: nrpe pid=1330 from=::ffff:10.61.164.115
May 31 09:17:11 <Server Name>xinetd[1330]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:17:11 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1330 duration=0(sec)
May 31 09:17:22 <Server Name>xinetd[1102]: START: nrpe pid=1368 from=::ffff:10.61.164.115
May 31 09:17:22 <Server Name>xinetd[1368]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:17:22 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1368 duration=0(sec)
May 31 09:17:26 <Server Name>ndo2db: Trimming timedevents.
May 31 09:17:26 <Server Name>ndo2db: Trimming timedevents.
May 31 09:17:26 <Server Name>ndo2db: Trimming systemcommands.
May 31 09:17:26 <Server Name>ndo2db: Trimming systemcommands.
May 31 09:17:26 <Server Name>ndo2db: Trimming servicechecks.
May 31 09:17:26 <Server Name>ndo2db: Trimming servicechecks.
May 31 09:17:26 <Server Name>ndo2db: Trimming hostchecks.
May 31 09:17:26 <Server Name>ndo2db: Trimming eventhandlers.
May 31 09:17:26 <Server Name>ndo2db: Trimming hostchecks.
May 31 09:17:26 <Server Name>ndo2db: Trimming eventhandlers.
May 31 09:17:36 <Server Name>xinetd[1102]: START: nrpe pid=1431 from=::ffff:10.61.164.115
May 31 09:17:36 <Server Name>xinetd[1431]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:17:36 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1431 duration=0(sec)
May 31 09:18:12 <Server Name>xinetd[1102]: START: nrpe pid=1672 from=::ffff:10.61.164.115
May 31 09:18:12 <Server Name>xinetd[1672]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:18:12 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1672 duration=0(sec)
May 31 09:18:19 <Server Name>xinetd[1102]: START: nrpe pid=1682 from=::ffff:10.61.164.115
May 31 09:18:19 <Server Name>xinetd[1682]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:18:19 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1682 duration=0(sec)
May 31 09:18:29 <Server Name>ndo2db: Trimming timedevents.
May 31 09:18:29 <Server Name>ndo2db: Trimming timedevents.
May 31 09:18:29 <Server Name>ndo2db: Trimming systemcommands.
May 31 09:18:29 <Server Name>ndo2db: Trimming systemcommands.
May 31 09:18:29 <Server Name>ndo2db: Trimming servicechecks.
May 31 09:18:29 <Server Name>ndo2db: Trimming servicechecks.
May 31 09:18:29 <Server Name>ndo2db: Trimming hostchecks.
May 31 09:18:29 <Server Name>ndo2db: Trimming hostchecks.
May 31 09:18:29 <Server Name>ndo2db: Trimming eventhandlers.
May 31 09:18:29 <Server Name>ndo2db: Trimming eventhandlers.
May 31 09:18:33 <Server Name>xinetd[1102]: START: nrpe pid=1757 from=::ffff:10.61.164.115
May 31 09:18:33 <Server Name>xinetd[1757]: FAIL: nrpe address from=::ffff:10.61.164.115
May 31 09:18:33 <Server Name>xinetd[1102]: EXIT: nrpe status=0 pid=1757 duration=0(sec)
The reinitiating of ndoutils causes us even a bigger problem because we are trying to configure master-slave replication. this issue generates an error on the slave database.
Also is there any special configuration parameters for ndo2db.cfg when doing database replication.