fatal error lock already exists /var/run/munin/munin-update.lock. dying Junior West Virginia

We provide Wildblue high-speed internet via satellite for rural areas without access to DSL or broadband. No phone line is required, only a clear view of the southern sky. We also provide supporting computer services, such as installation of wireless routers to provide wireless internet throughout the house. Computer repair and service is provided at our shop in Belington. Free estimates are given for our services at the store. Mt. Liberty Connections, Inc. has a full-time graphic designer on staff. She provides services such as computer graphic design, business cards, brochures, web page design along with video editing and vinyl signs.

Address 19 S Main St, Philippi, WV 26416
Phone (304) 457-6800
Website Link http://mtlibertyinc.com
Hours

fatal error lock already exists /var/run/munin/munin-update.lock. dying Junior, West Virginia

After a bit of investigations, it seems that munin processes (graph, update, etc...) don't remove their lock files when they end. Would you please write a bug report in the trac attaching one of the images. The only major difference is that the problem set is running > Debian Squeeze, whereas the no-problem setup has munin on Debian Lenny. > It runs fine, with no occurrences of Well...

Copy sent to Munin Debian Maintainers . Yes, but is that a cause or a symptom? Dying.log/munin/munin-graph.log:2012/08/06 10:41:29 [FATAL ERROR] Lock already exists: /opt/munin/var/run/munin/munin-graph.lock. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________munin-users mailing [email protected]://lists.sourceforge.net/lists/listinfo/munin-users reply | permalink Nicolai Langfeldt If it's not ignoring it that's a bug yes.

Re: [munin-users] Runaway munin processes From: Nicolai Langfeldt - 2011-08-12 05:17:00 On 08/12/2011 01:15 AM, Martin N Brampton wrote: > On 11/08/2011 23:11, Nicolai Langfeldt wrote: >> On 08/11/2011 03:38 It stores all the polled data into the spooldir. How many nodes do you have configured. Are you really surprised?

Should never happen. Nicolai Re: [munin-users] Runaway munin processes From: Martin Brampton - 2011-08-12 08:24:50 On 12/08/11 06:16, Nicolai Langfeldt wrote: > Would you be able to test a (ported) lenny kernel on Do you read the email to root on this vps? Then I discovered that I have /usr/bin/munin-cron added also to munin's crontab (crontab -e -u munin).

Many possibilities: the final cause is too long execution of munin-update (longer then 5 minutes). Is there something that could have been duplicated when I upgraded from Munin 2.0.3 to 2.0.4? Thank you for reporting the bug, which will now be closed. I *really* have to write a doc on it....

I checked all of the /etc cron folders and don't see anythingin there. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________munin-users mailing [email protected]://lists.sourceforge.net/lists/listinfo/munin-users reply | permalink Nicolai Langfeldt Munin 1.4 does batch graphing by default, and cgi graphing has some serious bugs so it might not work. Dying.log/munin/munin-graph.log:2012/08/06 10:56:30 [FATAL ERROR] Lock already exists: /opt/munin/var/run/munin/munin-graph.lock. Message #58 received at [email protected] (full text, mbox, reply): From: Holger Levsen To: [email protected] Subject: Bug#310915: fixed in munin 1.2.6-1 Date: Mon, 16 Jun 2008 13:17:36 +0000 Source: munin Source-Version:

Any help would be appreciated. ...[FATAL ERROR] Lock already exists:/opt/munin/var/run/munin/munin-graph.lock. Locking failed.
2013/03/25 23:11:02 [FATAL ERROR] Lock already exists: /var/run/munin/munin-update.lock. OR because the node process > or server is down at the time. The munin-updates seem to finish within a minute or two at most.NickFrom: [email protected]: [email protected]: Mon, 6 Aug 2012 12:36:48 -0400CC: [email protected]: Re: [munin-users] Lock already exists error after upgrading to Munin

They are all >> firewalled with iptables, but nothing dynamic is happening with the >> iptables configuration. >> >> There are a lot of "[WARNING] Call to accept timed out." but The munin-updates seem to finish within a minute or two at most. I'vealso tried running /usr/bin/munin-cron under the user munin and get noerror. Please referto http://munin-monitoring.org/wiki/FAQ_no_graphs at /usr/share/munin/munin-html line 38I understand this may not be Munin's fault but I am at a loss on howto debug this further.

Full text and rfc822 format available. Please study your logs and figure out if any nodes are slow or even totaly unresponsive. Since this is a VPS, is any other virtual machines using up the > CPU, the memory or the disk bandwidth in connection with this? > > Nicolai It is a If this doesn't help solve your problem, have a look inside the various munin log files in /var/log/munin/ to see if one of them contains more details as to why munin

Nick From: [email protected] To: [email protected] Date: Mon, 6 Aug 2012 12:36:48 -0400 CC: [email protected] Subject: Re: [munin-users] Lock already exists error after upgrading to Munin 2.0.4 Here are There are some failures to connect, and they include failures to connect to the node on which munin is running. I understand that I can withdraw my consent at any time. Request was from Brian May to [email protected]

By overwhelm, I can not ssh >> into the box, if a ssh is connected, terminal becomes non >> responsive, etc. Dying.
2013/03/25 23:11:02 at /usr/lib/perl5/vendor_perl/5.8.8/Munin/Master/Update.pm line 128 Munin hadn't been updating for a couple weeks, so I finally deleted the existing munin-update.lock file, and munin started running again. There are various warnings and information messages. Is there something that could have been duplicated when I upgraded from Munin 2.0.3 to 2.0.4?Date: Mon, 6 Aug 2012 08:41:07 +0200From: [email protected]: [email protected]: [email protected]: Re: [munin-users] Lock already exists error

I'm at the point where I'mdesperately looking for just about any workaround or hack that mightgive me a greater degree of confidence that a munin-update run isn'tgoing to get skipped or It seems I have to edit the comment to make my intend crystal-clear, sorry. -- Steve Schnepp http://blog.pwkf.org/ Re: [munin-users] Stable version 2.0 From: Gaƫtan Slongo - 2011-08-10 11:17:52 Attachments: Do you know where to get that ? The reports of CPU load are the CPU load in this VPS instance that is running munin.

Package version 2.0.2-1ubuntu2.2 to be specific. Dying.log/munin/munin-graph.log:2012/08/06 12:26:33 [FATAL ERROR] Error deleting lock /opt/munin/var/run/munin/munin-graph.lock: No such file or directorylog/munin/munin-graph.log:2012/08/06 12:31:33 [FATAL ERROR] Lock already exists: /opt/munin/var/run/munin/munin-graph.lock. I don't know any reason for them. > The nodes are all local - in the same data centre. Remove it from the cron file and file a bug on the site please.

So it is certainly not because the process is taking more than 5 minutes to run. After removing the update process there is nothing to do for others... No single node should ever preventmonitoring of the other nodes.On Thu, Nov 10, 2011 at 1:21 PM, Svensk Ljud & Ljus Produktionwrote:Im running munin 1.4.5 and have a munin plugin witch You said it: > There are some failures to connect, and they include failures to > connect > to the node on which munin is running.

Dying.at /usr/local/lib/perl5/site_perl/5.8.8/Munin/Master/Update.pm line 128Your munin-update has not finished before the next call.A running process sets a semaphor: /var/run/munin/munin-update.lockIf the file exists new processes will not start generating the message.I understand that On 11/08/11 12:01, Nicolai Langfeldt wrote: > Please stay on the list. Copy sent to Munin Debian Maintainers .