Mailing List Archive

rancid router hung on loghost?
Since a couple of hours I get:

rancid router hung on loghost? Old lockfile still exists:
-rw-r----- 1 rancid rancid 0 Jun 2 20:13 /tmp/.router.run.lock

As usual I didn't change anything (TM) :-)

I see some rancid processes

(loghost:nipper 2 ) ps -alef -opid,user,stime,args | grep rancid
17398 rancid 00:30:49 /usr/bin/perl /usr/local/bin/rancid gw.de-cix.net
17397 rancid 00:30:49 sh -c (rancid-fe \gw.de-cix.net:cisco)
4090 rancid 20:13:01 /bin/sh /usr/local/bin/control_rancid router
4083 rancid 20:13:01 sh -c /usr/local/bin/do-diffs
17411 rancid 00:30:49 /usr/local/bin/expect -- /usr/local/bin/clogin
-t 90 -c show version;show insta
17419 rancid 00:30:49 ssh -c 3des -x -l rancid gw.de-cix.net
4086 rancid 20:13:01 /bin/sh /usr/local/bin/do-diffs
17399 rancid 00:30:49 sh -c clogin -t 90 -c "show version;show install
active;show env all;show gsr c
4084 rancid 20:13:01 /bin/sh /usr/local/bin/do-diffs
17396 rancid 00:30:49 /usr/bin/perl /usr/local/bin/par -q -n 5 -c
rancid-fe \{} /var/rancid/router/ro

but have no idea why they got stuck. Looks like processes from 20:13 are
still active though all other processes started at 21:13, 22:13, ...
wnet thru. Removing /tmp/.router.run.lock does not really help as the
same problem reappears some hours later.

Any ideas? Thanks for your help!


Arnold
rancid router hung on loghost? [ In reply to ]
Thu, Jun 03, 2004 at 01:23:09AM +0200, Arnold Nipper:
> Since a couple of hours I get:
>
> rancid router hung on loghost? Old lockfile still exists:
> -rw-r----- 1 rancid rancid 0 Jun 2 20:13 /tmp/.router.run.lock
>
> As usual I didn't change anything (TM) :-)
>
> I see some rancid processes
>
> (loghost:nipper 2 ) ps -alef -opid,user,stime,args | grep rancid
> 17398 rancid 00:30:49 /usr/bin/perl /usr/local/bin/rancid gw.de-cix.net
> 17397 rancid 00:30:49 sh -c (rancid-fe \gw.de-cix.net:cisco)
> 4090 rancid 20:13:01 /bin/sh /usr/local/bin/control_rancid router
> 4083 rancid 20:13:01 sh -c /usr/local/bin/do-diffs
> 17411 rancid 00:30:49 /usr/local/bin/expect -- /usr/local/bin/clogin
> -t 90 -c show version;show insta
> 17419 rancid 00:30:49 ssh -c 3des -x -l rancid gw.de-cix.net
> 4086 rancid 20:13:01 /bin/sh /usr/local/bin/do-diffs
> 17399 rancid 00:30:49 sh -c clogin -t 90 -c "show version;show install
> active;show env all;show gsr c
> 4084 rancid 20:13:01 /bin/sh /usr/local/bin/do-diffs
> 17396 rancid 00:30:49 /usr/bin/perl /usr/local/bin/par -q -n 5 -c
> rancid-fe \{} /var/rancid/router/ro
>
> but have no idea why they got stuck. Looks like processes from 20:13 are
> still active though all other processes started at 21:13, 22:13, ...
> wnet thru. Removing /tmp/.router.run.lock does not really help as the
> same problem reappears some hours later.
>
> Any ideas? Thanks for your help!

dollars to donuts you're using a linux or solaris box and its nothing you've
done, your timing is just lucky. you need the expect patch on
www.shrubbery.net/rancid.

we've discovered that solaris 2.8 (possibly others) appears to have a bug
whereby that patch will affect the streams device (tty driver) and thus
leaves your terminal (or stdin) in non-blocking mode...which happens to
really irritate older versions of bash. i havent worked out a better
patch yet.
rancid router hung on loghost? [ In reply to ]
On 03.06.2004 09:57 john heasley wrote:

> dollars to donuts you're using a linux or solaris box and its nothing you've
> done, your timing is just lucky. you need the expect patch on
> www.shrubbery.net/rancid.
>

(loghost:nipper 1 ) uname -a
SunOS loghost 5.9 Generic_112233-04 sun4u sparc SUNW,UltraAX-i2

:-) Thanks for the hint. I will apply the patch.



Arnold