Hi, this can occur when you fetch the current development stuff via svn, because we sometimes also commit unfinished things. Please wait some time - we're about to commit an update procedure (http://server/idoit/updates) for the nagios stuff today. You can then just update to the "virtual" version 0.9.4 for preventing these exceptions. Regards, Dennis

Hello, Can you tell me how can I do to automatically feed the servers logbooks with Nagios events?  Is it working if Nagios is installed on another server? Here's an history of what I did: -> I entered the parameters in the NDO MySql Server section in Nagios module (on i-doit server).  The communication between i-doit and Nagios is working fine. -> I scheduled a task with cron to launch the command "php /path/controller.php -v -m nagios >> /var/log/idoit".     Here's an extract of what I can find in this log file (same every 10min): * Loading module: nagios    * Logging in..    * Connected to mandator: 1 (xxxx)    * Logged in as: nagsync    * Setting up system environment    * Nagios-Handler initialized (2010-10-12 18:30:02).    * Processing xxxxx..    * Processing xxxxx..    * Logging out -> Through i-doit web interface, I can see that my servers are UP or DOWN, so the communication with Nagios is working well but I cannot get the other monitoring information like CPU use or Memory use… Do you have any idea on what can I do ? Thank you in advance for your answer !