Pending status after reload/restart

[David Manchado]

Hi all,

I'm running Nagios on a Debian box but I can't configure it in order to read 
the previous state of hosts and services so everytime I perform a reload o 
restart all checks go to 'pending' status.
I've been using Nagios for long without any problem but just after an update 
it began to behave this way with no configuration change.

Version:
nagios-plugins 1.3.1.0-9     
nagios-text    1.2-3.5        

Has anyone had this problem before?

Some util config info:
~ nagios.cfg
resource_file=/etc/nagios/resource.cfg
status_file=/var/log/nagios/status.log
retain_state_information=1
state_retention_file=/var/log/nagios/status.sav
retention_update_interval=60
use_retained_program_state=1
interval_length=60
use_agressive_host_checking=0
execute_service_checks=1
accept_passive_service_checks=1
enable_notifications=1

~ hosts.cfg
retain_status_information       1
retain_nonstatus_information    1

~ services.cfg
retain_status_information       1
retain_nonstatus_information    1

/var/log/nagios/status.sav did not exist so I created it
-rw-rw-r--  1 nagios nagios  status.log
-rw-rw-r--  1 nagios nagios  status.sav

But it seems nagios does not write in it anyway, even copying status.log into 
status.sav and stop/start, reload or restart fails...

Maybe I'm missing some parameter but I can't figure where the mistake lies, so 
any help with be pleased.

Thanks in advance,
-- 
David Manchado


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
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