ndoutils constantly deinitializes

[Johnsmit]

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.

[scottwilkerson]

Which line of the log output are you referring to? All of this is normal every time the nagios service restarts.

[Johnsmit]

this is the data entry into nagios logentry table
"logentry_id","instance_id","logentry_time","entry_time","entry_time_usec","logentry_type","logentry_data","realtime_data","inferred_data_extracted"
7379,1,"2018-05-30 11:09:44","2018-05-30 11:09:44",941250,262144,"ndomod registered for adaptive contact data'",1,1
7380,1,"2018-05-30 11:09:44","2018-05-30 11:09:44",941258,262144,"Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.",1,1
7381,1,"2018-05-30 11:09:48","2018-05-30 11:09:48",31120,64,"Caught SIGTERM, shutting down...",1,1
7382,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",0,262144,"Successfully launched command file worker with pid 2767",1,1
7383,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",0,64,"Successfully shutdown... (PID=2731)",1,1
7384,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203445,262144,"ndomod registered for log data'",1,1
7385,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203459,262144,"ndomod registered for system command data'",1,1
7386,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203467,262144,"ndomod registered for event handler data'",1,1
7387,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203480,262144,"ndomod registered for notification data'",1,1
7388,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203488,262144,"ndomod registered for comment data'",1,1
7389,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203495,262144,"ndomod registered for downtime data'",1,1
7390,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203502,262144,"ndomod registered for flapping data'",1,1
7391,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203508,262144,"ndomod registered for program status data'",1,1
7392,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203515,262144,"ndomod registered for host status data'",1,1
7393,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203522,262144,"ndomod registered for service status data'",1,1
7394,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203528,262144,"ndomod registered for adaptive program data'",1,1
7395,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203535,262144,"ndomod registered for adaptive host data'",1,1
7396,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203542,262144,"ndomod registered for adaptive service data'",1,1
7397,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203549,262144,"ndomod registered for external command data'",1,1
7398,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203556,262144,"ndomod registered for aggregated status data'",1,1
7399,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203563,262144,"ndomod registered for retention data'",1,1
7400,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203570,262144,"ndomod registered for contact data'",1,1
7401,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203577,262144,"ndomod registered for contact notification data'",1,1
7402,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203585,262144,"ndomod registered for acknowledgement data'",1,1
7403,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203591,262144,"ndomod registered for state change data'",1,1
7404,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203598,262144,"ndomod registered for contact status data'",1,1
7405,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203605,262144,"ndomod registered for adaptive contact data'",1,1
7406,1,"2018-05-30 11:09:50","2018-05-30 11:09:50",203624,262144,"Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.",1,1
7407,1,"2018-05-30 11:09:56","2018-05-30 11:09:56",234333,262144,"Successfully launched command file worker with pid 2821",1,1

[scottwilkerson]

That entry should be in that table, it is also logged right from the nagios.log.

[Johnsmit]

why it is restarting everytime while inserting data to database? how can generating sigterm be normal ?

[scottwilkerson]

why it is restarting everytime while inserting data to database? how can generating sigterm be normal ?

It doesn't every time you do an insert. The SIGTERM is only logged when the nagios process restarts.

If you look at your example of data you showed from the table, you will see that there is a lot more data there than just the SIGTERM lines

Instead of telling us the software isn't working right because it is generating something you do not understand in the log, how about asking a question that is relevant to your experience using the software?

Does Nagios XI stop working? Does the UI stop updating? Is it not producing reports or notifications?

Are any of those the problem? Or is it just a log line that you do not understand?

[Johnsmit]

It doesn't complete replication to a remote database so are you saying it is impossible to use the Nagios MariamdB capabilities to do application replication without buying LINBIT which is not replication but HA Failover. So Correct me you can not do db replication with Nagios ONLY.

[scottwilkerson]

How are you performing your replication? Your replication should have nothing to do with the nagios process.

Quite frankly you should be able to replicate your database even if the nagios process isn't running, one has no bearing on the other.

[mcapra]

I'm still of the opinion that an incorrect replication strategy is to blame:
https://support.nagios.com/forum/viewto ... 84#p251584

[scottwilkerson]

I tend to agree with @mcapra

and @Johnsmit please keep all these under 1 thread, you have all kinds of different forum threads open on the same topic and keep bouncing back and forth so each only has a small amount of the whole picture...

Please, please, please just use one forum thread for everyone's sanity so we can assist you.