Nagios Support Forum

Hello,

I have been using Nagios 1.4.1 on Linux 4.7.

Nagios has not executed the update processing since the daily log rotation.
・We can refer to the Nagios management screen.
・The regular check processing is not executed on the schedule time.
・The reply doesn't return even if we change the schedule of the check processing.

After all,it returned normally by restart Nagios.
Does anyone else understand the cause of pertinent trouble?

Thanks in advance.

What does your Scheduling Queue look like?
Keep a close eye on Monitoring Performance.

Let me know if I'm way off base, I'm not certain I understand what you are trying to say.

Thank you for your response.

When we noticed the problem, we didn't check Scheduling Queue.
so, we don't understand the state of Scheduling Queue at that time.

But, we confirmed that /var/log/nagios/status.log had not been updated.
Such that we infer the scheduling Queue screen had not been updated.
※the Nagios management screen had not been updated from point to which status.log wasn't updated.

Though it might be unrelated to the above-mentioned problem,an external command wasn't accepted to Nagios．

Is the bug of Nagios a cause of the problem?

Thanks in advance.

I'm unaware of any bug that could cause this, however I have had similar issues. It sounds as though the Nagios server got hung up performing some task. I look forward to hearing more about the status of Nagios during these periods, perhaps some strace output would shed light on this. The process to strace is the Nagios one.

Thank you for your response.

Because We don't understand the cause that Nagios stop, we dot't know that when Nagios stop.
Therefore,we can't prepare to get strace output beforehand.

As information on the addition,
we execute the reload processing of the configuration file(timeperiods.cfg)
almost the same time as the daily log rotation.

We know the following fact as a result of the examination from the Nagios log.

■normal
1.finished the daily log rotation
2.caught sighup(restart)
3.finished restart

■abnormal
1.finished the daily log rotation
but 2 and 3 were not finished.

So,we are doubting that the cause is competition of process or failure of reload.

Do not you know the bug of failure of reload or the event that looks like?

Thanks in advance.

We understood the cause of the event.

The cause of this event is bug of Nagios.
Reference URL:http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416763

We plan to correct the reload processing of the configuration file.

We really appreciate your cooperation.