Paulo, Glad to know you managed to solve the problem. Thank you very much for your kind words on Monitorix.
Best regards. On 01/09/2013 04:17 PM, Paulo Ribeiro wrote: > Hello Jordi, thank you for your reply! > > I had already deleted the old cron scripts, as I noticed that the new > version now uses a daemon. > > However, your reply gave me an idea: > > ~$ ps aux | grep 'monitorix' > root 11665 0.0 0.6 115136 12644 ? Ss Jan08 1:01 > /usr/bin/monitorix -c /etc/monitorix.conf > root 11767 0.0 0.6 115136 13020 ? Ss Jan08 1:01 > /usr/bin/monitorix -c /etc/monitorix.conf > root 12482 0.1 0.9 132588 19560 ? Ss 11:23 0:25 > /usr/bin/monitorix -c /etc/monitorix.conf -p /var/run/monitorix.pid > > For some reason, I had two "rogue" monitorix processes, running without > the -p switch. I manually killed those and the file lock errors are gone! > > Thank you, and congratulations for such a simple and elegant application. :) > -- Jordi Sanfeliu FIBRANET Network Services Provider http://www.fibranet.cat ------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 _______________________________________________ Monitorix-general mailing list Monitorix-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monitorix-general
