localhost/Service Status - ndo2db is UNKNOWN [Solved]

[abiswas]

We started having an error with one of ndo2db service for couple days now.

Nagios has detected a problem with this service.

Notification Type: PROBLEM

Service: Service Status - ndo2db
Host: localhost
Address: 127.0.0.1
State: UNKNOWN
Info:
● ndo2db.service - Nagios Data Out Daemon

I have narrowed it down to the binary /usr/local/nagios/bin/ndomod.o

When I execute it, I get
# /usr/local/nagios/bin/ndomod.o
Segmentation fault

I have tried compiling it myself with the result.

And here is the service status:

● ndo2db.service - Nagios Data Out Daemon
Loaded: loaded (/usr/lib/systemd/system/ndo2db.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2018-08-10 15:40:28 EDT; 4 days ago
Docs: http://www.nagios.org/documentation
Process: 30102 ExecStopPost=/bin/rm -f /usr/local/nagios/var/ndo2db.pid (code=exited, status=0/SUCCESS)
Process: 30099 ExecStart=/usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg -f (code=exited, status=1/FAILURE)
Main PID: 30099 (code=exited, status=1/FAILURE)

Aug 10 15:40:28 sentry systemd[1]: Started Nagios Data Out Daemon.
Aug 10 15:40:28 sentry systemd[1]: Starting Nagios Data Out Daemon...
Aug 10 15:40:28 sentry systemd[1]: ndo2db.service: main process exited, code=exited, status=1/FAILURE
Aug 10 15:40:28 sentry systemd[1]: Unit ndo2db.service entered failed state.
Aug 10 15:40:28 sentry systemd[1]: ndo2db.service failed.

Any help is appreciated! Thanks!

[tgriep]

The ndomod.o binary is not meant to be ran from the command line so that is why it is erring out when you do.

I would guess that the ndo2db service is not starting because of a left over lock or sock file so lets remove them and start the daemon.
Run this as root.

Code: Select all

rm -rf /usr/local/nagios/var/ndo.sock
rm -rf /usr/local/nagios/var/ndo2db.lock
service ndo2db start

Then check it to see if it started by running

Code: Select all

service ndo2db status

Let us know if it started for you.

[abiswas]

The ndomod.o binary is not meant to be ran from the command line so that is why it is erring out when you do.

I would guess that the ndo2db service is not starting because of a left over lock or sock file so lets remove them and start the daemon.
Run this as root.

Code: Select all

rm -rf /usr/local/nagios/var/ndo.sock
rm -rf /usr/local/nagios/var/ndo2db.lock
service ndo2db start

Then check it to see if it started by running

Code: Select all

service ndo2db status

Let us know if it started for you.

Thanks!! That worked out perfectly

[scottwilkerson]

The ndomod.o binary is not meant to be ran from the command line so that is why it is erring out when you do.

I would guess that the ndo2db service is not starting because of a left over lock or sock file so lets remove them and start the daemon.
Run this as root.

Code: Select all

rm -rf /usr/local/nagios/var/ndo.sock
rm -rf /usr/local/nagios/var/ndo2db.lock
service ndo2db start

Then check it to see if it started by running

Code: Select all

service ndo2db status

Let us know if it started for you.

Thanks!! That worked out perfectly

Great Closing thread