[rancid] Re: Problems with getting configuration from a PIX 501.

[Steve Ousley]

Hi Ingabire

I have had a look, and when rancid runs, I also see a fair few instances of
expect running.  However looking at the times on these (840 hours for one),
that looks like a bit of a problem, it may just be that it has locked up,
and crashed.  Also stuff in [] I think is usually defunct stuff that has
died, but not properly.

I would suggest to ensure that tancid isnot running, and then killing these
processes manually.  Ensure that no processes exist, and that the lock files
(usually in /tmp) are not there, and then try rancid again.

This is all I can really offer from my limited experience.

Regards

Steve Ousley - SO620-RIPE
Nuco Technologies Ltd
steve at host-it.co.uk
www.nucotechnologies.com
Tel. 0870 165 1300

Nuco Technologies Ltd is a company registered in England and Wales
with company number 04470751


-----Original Message-----
From: Ingabire Grace [mailto:gingabire at rwandatel.rw] 
Sent: 15 July 2008 17:26
To: 'Steve Ousley'
Subject: RE: [rancid] Re: Problems with getting configuration from a PIX
501.

Hi Steve,

Congrats as your rancid is now working.
When trying to run rancid, I m seeing a lot of processes: is this normal? I
think no. I could not see what I made wrong...

rancid 74842 24.1  0.2  2756  2464  ??  R    11:30AM 135:08.47 [expect]
rancid 74924 24.1  0.2  2756  2464  ??  R    11:31AM 133:50.24 [expect]
rancid 76016 24.0  0.2  2756  2464  ??  R     6:01PM   4:40.78 [expect]
rancid 69761 23.9  0.2  2756  2464  ??  R    Mon11AM 840:14.06 [expect]
rancid 74837  0.0  0.1  1728  1236  ??  I    11:30AM   0:00.00 [sh]
rancid 75976  0.0  0.2  2856  2436  ??  I     6:01PM   0:00.02
/usr/bin/perl5 /usr/local/libexec/rancid//par -q -n 5 -c rancid-fe \\{}
/usr/local/var/rancid
rancid 76000  0.0  0.1  1724  1228  ??  I     6:01PM   0:00.00 sh -c
(rancid-fe \\196.xx.xx.xx:cisco)
rancid 76002  0.0  0.3  3596  3124  ??  I     6:01PM   0:00.04
/usr/bin/perl5 /usr/local/libexec/rancid//rancid 196.xx.xx.xx (perl5.8.8)
rancid 76012  0.0  0.1  1728  1236  ??  I     6:01PM   0:00.00 [sh]
rancid 69610  0.0  0.1  1732  1372  p0- I    Mon11AM   0:00.00 /bin/sh
/usr/local/libexec/rancid/rancid-run
rancid 69613  0.0  0.1  1740  1380  p0- I    Mon11AM   0:00.04 /bin/sh
/usr/local/libexec/rancid//control_rancid all

Can you please share your knowledge as you make yours working.

Thanks.


-----Original Message-----
From: rancid-discuss-bounces at shrubbery.net
[mailto:rancid-discuss-bounces at shrubbery.net] On Behalf Of Steve Ousley
Sent: Tuesday, July 15, 2008 5:56 PM
To: rancid-discuss at shrubbery.net
Subject: [rancid] Re: Problems with getting configuration from a PIX 501.

Oh, ok, I hadn't checked if it was still running,  but I do remember running
killall -9 rancid-run before I had done that anyway.  So I guess
inadvertently I had made sure it wasn't running, but not really consciously.
=/

Steve Ousley - SO620-RIPE
Nuco Technologies Ltd
steve at host-it.co.uk
www.nucotechnologies.com
Tel. 0870 165 1300

Nuco Technologies Ltd is a company registered in England and Wales
with company number 04470751


-----Original Message-----
From: john heasley [mailto:heas at shrubbery.net] 
Sent: 15 July 2008 16:54
To: Steve Ousley
Subject: Re: [rancid] Re: Problems with getting configuration from a PIX
501.

Tue, Jul 15, 2008 at 01:00:13PM +0100, Steve Ousley:
> Problem solved
> 
>  
> 
> I had a stunning idea to check the logs for the pix on rancid... lord only
> knows why I didn't think to do this sooner, but in there it stated that
> /tmp/.pix.run.lock existed.  Knowing that rancid was not running, I
removed
> this file, and ran rancid, and now we have updates on all the pix
firewalls.
> :)  

you should actually check that its really not running before removing that.
it could have been stuck or it could be a left-over from a system crash. 

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss at shrubbery.net
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss