Doesnt Timeout?

[Seth Martin]

I think I found my problem
This was commented out:
MAX_ROUNDS=2; export MAX_ROUNDS

I set it to 2 rounds and now it fails after 3 minutes (180 seconds, 2
time out sessions)

If this is commented out (as is in the default config example) how many
times will it retry?  In the howto I also found it didn't make any
reference to this either.

Seth Martin
-Desk: 239-949-4450  x6705

-----Original Message-----
From: john heasley [mailto:heas at shrubbery.net] 
Sent: Thursday, February 23, 2006 4:35 PM
To: Seth Martin
Cc: rancid-discuss at shrubbery.net
Subject: Re: Doesnt Timeout?

Thu, Feb 23, 2006 at 04:03:29PM -0500, Seth Martin:
> I've Installed RANCID on a fresh install of Debian.  It runs just
fine,
> I setup a spare cisco 2600 router and I am able to log the config,
> changes to the router get reported just fine.  However if the device
> goes down (I turn itoff) and do a rancid-run it just hangs, and hangs,
> and after about 15 minutes I kill the process.  I am using the TCL
and
> expect packages from the rancid ftp server.  Any idea why this would
> happen?  Is it maybe because I have only 1 device?  When the device is
> down the clogin does timeout.

That is odd.  The connection should timeout (telnet or ssh) or expect
should timeout waiting for either of them.  Please send a transcript of
an interactive login attempt ("clogin device") while it is off or
disconnected.  eg:

% jlogin jnx
jnx
spawn telnet jnx
Trying 198.58.5.26...
telnet: Unable to connect to remote host: No route to host

Error: Couldn't login