The /var/run/shinken directory is actually deleted every time the server reboots (every night at 3AM or manual shutdown) without being created afterwards. 

So, I followed the advice and I created the directory manually with the shinken user ownership and everything worked fine again (shinken started and restarted correctly by using /var/run/shinken directory for pid files location). Nevertheless, the directory is still deleted without being re-created at system reboot (maybe an issue with user rights preventing this directory of being re-created at startup ?).

Best regards,


Le 27 oct. 2011 à 10:12, nap a écrit :

On Wed, Oct 26, 2011 at 9:49 AM, Simon SCHERRER <simon.scherrer@insa-strasbourg.fr> wrote:

I did a fresh install of Shinken 0.8.1/Thruk 1.1.1 on an Ubuntu Server 10.04 LTS based on the nicolargo's script (great job, by the way). For now, I just added some services on localhost (the server itself). Everything works fine until the server reboot (daily task). Then the daemons are just unable to restart with this kind of error in the "/tmp/bad_start_for_" log files :

Maybe, I just miss something in the main configuration of Shinken (the default configuration has been kept since the setup).

Thanks for your help,



Is the /var/run/shinken directory really deleted? Can you try to mkdir it, with shinken ownership, and restart Shinken. If it wok (and it should :) ) can you restart it and see if this directory still exists?


The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
Shinken-devel mailing list