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. :) -- Paulo Ribeiro On 13.Jan.09 14:16, Jordi Sanfeliu wrote: > Hello Paulo, > > Those error messages in the log file are of course unexpected. > > As you might know your old Monitorix version (probably 1.x branch) used > the crond to collect data on every minute while the new 2.x branch (as > you might already know) acts as a daemon. > > So, you better check in your /etc/cron.d/ directory to make sure if > there is a residual 'monitorix' file from the 1.x branch that crond is > still executing on every minute. > > Please, let me know if that solved your problem. > Best regards. > > > > On 01/09/2013 02:37 PM, Paulo Ribeiro wrote: >> Hello, >> >> I've been using an older version of Monitorix for a couple of years, but >> yesterday I decided to update to version 2.6.0. >> >> I'm running Ubuntu Server 10.04.4, so I decided to completely remove the >> old version and install the new one using the IzzySoft repository. >> >> Apparently all went well, and Monitorix is up and running. However, in >> the log file I see many errors complaining that Monitorix cannot lock >> some of the .rrd files. For example: >> >> Wed Jan 9 13:23:00 2013 - ERROR: while updating >> /var/lib/monitorix/net.rrd: could not lock RRD >> Wed Jan 9 13:23:00 2013 - ERROR: while updating >> /var/lib/monitorix/int.rrd: could not lock RRD >> Wed Jan 9 13:24:00 2013 - ERROR: while updating >> /var/lib/monitorix/int.rrd: could not lock RRD >> Wed Jan 9 13:27:00 2013 - ERROR: while updating >> /var/lib/monitorix/system.rrd: could not lock RRD >> Wed Jan 9 13:27:00 2013 - ERROR: while updating >> /var/lib/monitorix/int.rrd: could not lock RRD >> Wed Jan 9 13:28:00 2013 - ERROR: while updating >> /var/lib/monitorix/proc.rrd: could not lock RRD >> >> I searched for this type of error, but all the references I found had to >> do with using the NFS filesystem, which I am not using. >> >> I already tried stopping Monitorix, deleting the files, and starting >> Monitorix again. Monitorix detected that the files were missing, so it >> created the files again, but the errors continue. When I load the Web >> page, most of the graphs already display values (the ones that are empty >> may still need to be configured). >> >> Is there anything that I can do to understand why Monitorix cannot lock >> these files? Or are these errors to be expected? >> >> Thank you, >> > ------------------------------------------------------------------------------ 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
