[rancid] Re: /tmp/.networking.run.lock exists

[john heasley]

Fri, Jan 12, 2007 at 02:05:27PM -0600, Justin Shore:
> It sounds like you're checking too many hosts in one single linear run
> and it's taking too long.  You may want to either increase PAR_COUNT in
> etc/rancid.conf or you may want to run each of the groups listed in
> LIST_OF_GROUPS from cron separately.  
> 
> 0 */1 * * * rancid-run abc
> 0 */1 * * * rancid-run def
> 0 */1 * * * rancid-run ghi
> 0 */1 * * * rancid-run jkl
> 0 */1 * * * rancid-run mno
> 
> I do both.  I set PAR_COUNT to 5 and I run each of our POPs (how I break
> up LIST_OF_GROUPS) separately from cron.  That way a slow speed link in
> one POP won't hold up the rancid on the other POPs.
> 
> That's my take on your problem.
> 
> Justin
> 
> -----Original Message-----
> From: rancid-discuss-bounces at shrubbery.net
> [mailto:rancid-discuss-bounces at shrubbery.net] On Behalf Of Pena, Antonio
> Sent: Friday, January 12, 2007 10:48 AM
> To: rancid-discuss at shrubbery.net
> Subject: [rancid] /tmp/.networking.run.lock exists
> 
> Hello
> 
> I started to get this message after Rancid runs:
> 
> more networking.20070112.110101
> starting: Fri Jan 12 11:01:01 EST 2007
> 
> hourly config diffs failed: /tmp/.networking.run.lock exists
> -rw-r-----  1 rancid netadm 0 Jan 12 10:01 /tmp/.networking.run.lock
> 
> ending: Fri Jan 12 11:01:01 EST 2007
> You have new mail in /var/spool/mail/root
> 
> I deleted the file, but next time breaks again.
> 
> Also found another file on /tmp/ called "rancid.networking.2447", if I
> cat this file comes with same message line....
> 
> cvs update: [16:46:32] waiting for rancid's lock in
> /usr/local/rancid//var/CVS/networking

more likely that (another) cvs is hanging, either due a buggered local
repository or a user is holding the lock on the respository.

cd /var/rancid/networking
cvs update -AdP

should not hang.