My servers problem was due to it occasionally going into read only state due to a SCSI bios issue I have yet to fix. A new server is being built to replace it, slowly. I just haven't been checking on it for a while and found the locked file state when I noticed the router.db file for one group wasn't updated after I added some devices and did a rancid-run. It was a DOH moment for me because I forgot the darn file is hidden and I didn't see it to delete it. All is working fine for me. I like the Fedora Core server version that I run, other than the hardware issue, it has performed flawlessly.
Nothing ever goes as planned, Its a hell of a notion,
Even pharaohs turn to sand, Like a drop in the ocean
-----Original Message-----
From: rancid-discuss-***@shrubbery.net [mailto:rancid-discuss-***@shrubbery.net] On Behalf Of Alan Evans
Sent: Tuesday, August 07, 2007 3:36 PM
To: rancid-***@shrubbery.net
Subject: [rancid] Re: File lock help
This maybe a coincidence but I started to get the same problem a couple of days ago.
Rancid would hang after a while and I had to "kill -9" a number of rancid processes and then remove the lock file. It would work for about 12 hours and then hang again.
I knew about the expect patch but hadn't applied it because I didn't have any problems. I applied the expect patch to see if this would fix my problem but it made things worse. After applying the patch I did not get any output in the .new files.
I fixed my problem (hopefully) by installing the ActiveState's ActiveTcl distribution (http://www.activestate.com/Products/activetcl/).
This distribution includes expect as a package to tclsh rather than a separate executable therefore if you want to use ActiveTcl's expect you need to change the first line in the rancid login scripts:
From:
# /usr/bin/expect --
To something like this:
#! /usr/local/ActiveTcl-8.4/bin/tclsh8.4
package require Expect
cheers
AlanE
________________________________________
From: rancid-discuss-***@shrubbery.net [mailto:rancid-discuss-***@shrubbery.net] On Behalf Of Chris Stave
Sent: Monday, August 06, 2007 10:41 AM
To: Todd Heide
Cc: rancid-***@shrubbery.net
Subject: [rancid] Re: File lock help
To unlock, you just delete the file in question, /tmp/.Customer_Routers.run.lock
This file gets created during the hourly run, and sometimes doesn't get properly removed.
Chris Stave
Computing and Network Services
Drew University
On 8/6/07, Todd Heide <***@equivoice.com > wrote:
I know I asked this before, but cant find the reply from a year ago.
hourly config diffs failed: /tmp/.Customer_Routers.run.lock exists
-rw-r----- 1 rancid netadm 0 Aug 2 14:10 /tmp/.Customer_Routers.run.lock
How do I unlock the files? Also what would have locked them in the first place?