Nagios is freezing a lot of time

[Adrian Chapela]

Hello,

I have been using Nagios from a long time ago (6 years...). From 2 weeks 
ago I am experiencing some problems with nagios, it is stopping getting 
information and checking services and hosts. Also the graphs are 
stopping. It was version 3.0.6 and I am getting this messages:

Oct 18 09:03:54 correo1 nagios: Warning: A system time change of 1d 7h 
49m 0s (forwards in time) has been detected.  Compensating...
Oct 18 09:07:56 correo1 nagios: Auto-save of retention data completed 
successfully.
Oct 18 09:12:56 correo1 nagios: Auto-save of retention data completed 
successfully.
Oct 18 09:15:23 correo1 nagios: Warning: The check of host 'APN' looks 
like it was orphaned (results never came back).  I'm scheduling an 
immediate check of the host...

Now I have installed Nagios 3.2.0 to try to avoid this problem but it 
has appear again but without any message in log:
Oct 26 06:43:35 correo1 nagios: Auto-save of retention data completed 
successfully.
Oct 26 06:48:35 correo1 nagios: Auto-save of retention data completed 
successfully.
Oct 26 06:53:35 correo1 nagios: Auto-save of retention data completed 
successfully.
Oct 26 06:58:35 correo1 nagios: Auto-save of retention data completed 
successfully.

nagios only write the above messages  in log. But I have lost the graphs 
and  6 hours later all of checks. Why could be the reason ?

Thank you!



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null