Reboot of server, now having issues with NagVis and other

[brian.gamble]

Rebooted server and when I now go into my NagVis maps, all I get is:

ERROR: Problem (Backend:ndomy_1): NDO Claims that nagios did no status update for more than "180" seconds. Make sure that nagios and NDO daemons are running. (Backend-ID: ndomy_1)

Also,

Several of my server's services are showing up as only "(service name) critical. No route to host.

How do I resolve these issues and why is it so sensitive to reboots. Seems everytime I reboot I'm holding my breathe only to have issues once booted back up?

[jsmurphy]

If you run a 'ps -ef | grep ndo2db' does it return any results? If not then the backend database hasn't started. So do the following:

/etc/init.d/nagios stop
/usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg
/etc/init.d/nagios start

The service restart may take up to 45 mins depending on how much data it needs to synch with the database. Ndo2db must start before Nagios. To prevent this problem in the future create an entry for ndo2db in xinetd. Do you use the provided Nagios CentOS image? I've that to be highly resilient.

[brian.gamble]

When I run the 'ps -ef | grep ndo2db' command, the following is returned:

root 10276 7241 1 15:00 tty1 00:00:00 grep ndo2db

I'm running the Nagios XI VMWare Image

[yancy]

Brian,

it looks like the only results returned that match the grep is the grep command itself you passed.

Here is what the output should look like if ndo2db is running:

nagios 3376 1 0 Nov23 ? 00:00:00 /usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg
nagios 26709 3376 0 09:20 ? 00:00:00 /usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg
root 29318 29121 0 09:28 pts/1 00:00:00 grep ndo2db

try starting ndo2db as jsmurphy suggested above.

[brian.gamble]

After running the /usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg command, I get the following response:

Could not bind socket: Address already in use

[mguthrie]

This looks like it's an issue that's specific to NagVis. Try the following and see what happens.

Code: Select all

yum install ntp
ntpdate pool.ntp.org  #this will makes your system time is up to date

service mysqld restart
service ndo2db restart
service nagios restart

[brian.gamble]

After the install completed, I ran the ntpdate pool.ntp.org command and it came back with:

ntpdate[26898]: no server suitable for synchronization found

I assumet that's not normal? I can ping pool.ntp.org

[brian.gamble]

Back in business. Thanks guys!

[agriffin]

Glad to hear everything's working okay!