Nagios did not exit in timely manner

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
pradeepanan
Posts: 41
Joined: Wed Sep 30, 2015 1:58 pm

Nagios did not exit in timely manner

Post by pradeepanan »

Folks,

My previous post was regarding "Thruk" which i though was the issue. But when I do export in nagios its showing "Warning : Nagios did not exit in timely manner" error. I have checked if there is any duplicate instance running which is not. I have also checked the timput in init script which till 1...30. Is there any other thing I am missing to check?
pradeepanan
Posts: 41
Joined: Wed Sep 30, 2015 1:58 pm

Re: Nagios did not exit in timely manner

Post by pradeepanan »

I am also seeing next schedule check is in past. So whenever I stop and start nagios process , its working again. Will the be related to above issue?
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:

Re: Nagios did not exit in timely manner

Post by Box293 »

Is your system time and php time correctly set to your timezone?

Even though the following KB article is for Nagios XI, the same systems should work for Nagios Core:

https://assets.nagios.com/downloads/nag ... m_Time.pdf

Does this help?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
pradeepanan
Posts: 41
Joined: Wed Sep 30, 2015 1:58 pm

Re: Nagios did not exit in timely manner

Post by pradeepanan »

Yes, it is set to my time zone.

also when I restart nagios am seeing process running like,

ps awx | grep nagios.cfg | grep -v grep
7140 ? Ssl 1:41 /usr/sbin/nagios -d /etc/nagios/nagios.cfg
15504 ? S 0:00 /usr/sbin/nagios -d /etc/nagios/nagios.cfg
15506 ? S 0:00 /usr/sbin/nagios -d /etc/nagios/nagios.cfg

I was expecting process stst to be "R+". How ever not sure what the above means. Is this something abnormal?
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Nagios did not exit in timely manner

Post by rkennedy »

It's hard to say because Thruk will still make changes on how everything runs. We aren't able to support forks.

On a stock XI system though, it's running with Ss:

Code: Select all

[root@localhost etc]# ps awx | grep nagios.cfg | grep -v grep
 2027 ?        Ss     0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
 2048 ?        S      0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
Former Nagios Employee
pradeepanan
Posts: 41
Joined: Wed Sep 30, 2015 1:58 pm

Re: Nagios did not exit in timely manner

Post by pradeepanan »

I think I am kind of stuck in figuring out the issues. Anyway thanks for the help folks
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Nagios did not exit in timely manner

Post by tgriep »

The only other suggestion is to update to the latest version of Nagios or if you have a lot of warnings in the nagios configs, try and resolve those as that will speed up nagios restarting.
Be sure to check out our Knowledgebase for helpful articles and solutions!
pradeepanan
Posts: 41
Joined: Wed Sep 30, 2015 1:58 pm

Re: Nagios did not exit in timely manner

Post by pradeepanan »

I am doing some clean up and see if that fixes the issue. Thanks
User avatar
lmiltchev
Former Nagios Staff
Posts: 13587
Joined: Mon May 23, 2011 12:15 pm

Re: Nagios did not exit in timely manner

Post by lmiltchev »

Let us know if you have any more questions. Is it OK if we lock this thread?
Be sure to check out our Knowledgebase for helpful articles and solutions!
pradeepanan
Posts: 41
Joined: Wed Sep 30, 2015 1:58 pm

Re: Nagios did not exit in timely manner

Post by pradeepanan »

I have cleaned up the nagios config and did export. This time I dont see any error and everything was running smooth and fine. After several hours I am seeing the time for "next schedule check" goes 5 minutes behind. I was expecting it to be same as my system time but its not.

For example
Next Scheduled Check: 19:46:16 This service is currently executing its servicecheck
system time :
[root@nms ~]# date
Tue Aug 23 19:54:04 GMT 2016
Locked