rancid hangs due to expect, ssh, or cisco?

[john heasley]

Mon, Dec 23, 2002 at 05:00:29PM -0600, Zhang, Anchi:
> I do get the shell prompt back right after the last line of the debug but it
> takes a long time to get there.

about 45 seconds?  that is the timeout period.  but, in the debug output
you sent, it should have immediately returned since it matched the prompt
and then EOF.

however, if the output hung prior to receiving the prompt (when we are
not expecting EOF), then it will wait for the timeout period.

>  Rancid over ssh does work with some of my routers but not all.  For
> example, it had worked with one router until I added a few more lines to
> its existing ACL.

can you share the lines that were added?

> The strange thing is that if I login using clogin <hostname> and issue
> "show run" at the router's command prompt, the display will be fine.
> However, if I do "term len 0" and then "show run" the display hangs when
> it gets close to the very end of the config.

when clogin <hostname> is used, clogin takes care of the login process
and then uses interact.  this should in essence (fingers crossed) connect
your terminal directly to the pty until EOF.  thus i suspect this is a
cisco bug.  try telnet (or ssh) without clogin.