[rancid] Re: Rancid and end of run issues

[Gary Roberts]

Correct, but i have modified my version of rrancid so the only command its running is "show config".
So in essence, it is running the file, as i have it modified.
Nothing has been changed on the server, I've checked my yum logs, the only upgrade that has occured was back on 24Mar07, when it download the tzdata for the DST changes. But RANCID has been running flawlessly up until yesterday afternoon.
My version of expect is:
[root at Rancid ~]# rpm -q expect
expect-5.42.1-1

My next step was to do an strace, so i could see what was happening at the packet level, i was just hoping someone had ran into this before.

Thanks

GR




> ------------Original Message------------
> From: Ed Ravin <eravin at panix.com>
> To: "Gary Roberts" <groberts at hcis.net>
> Cc: "Lance" <rancid at gheek.net>, rancid-discuss at shrubbery.net
> Date: Fri, Apr-6-2007 5:14 PM
> Subject: Re: [rancid] Re: Rancid and end of run issues
>
> On Fri, Apr 06, 2007 at 05:05:04PM -0500, Gary Roberts wrote:
> > I gave that a shot,. with the same results.
> > If i run clogin from the command line, it does indeed pull the config 
> as it should.
> 
> But you aren't calling clogin the same way rrancid does - these 
> commands
> are invoked:
> 
>     "show version",
>     "dir /flash",
>     "dir /pcmcia0",
>     "dir /pcmcia1",
>     "show hardware",
>     "show chassis",
>     "show slot table",
>     "show config"
> 
> So you have to test with something like:
> 
>   clogin -c "show version;dir /flash;dir /pcmcia0; [...] ;show config"
> 
> > My first question when something stops working as it should is
> > "Whats Changed?", but in the case, i can honestly say, nothing has
> > changed as far as the router or access or the rancid server and
> > its .conf files. all is as it should be.
> 
> Have you changed anything on the server running RANCID, like upgraded
> its version of expect?
> 
> Another possible diagnostic would be running tcpdump (for telnet
> sessions) or strace/ktrace/truss (for ssh sessions) to see what
> was actually happening on the line.
> 
>