[rancid] clogin and rancid good, rancid-run fails

Alan McKinnon alan.mckinnon at gmail.com
Mon Oct 26 13:42:13 UTC 2015


On 26/10/2015 15:18, Ken Celenza wrote:
> I have been running rancid for a little over a year, and over the last month about 20 devices out of a few hundred stopped working. These are cisco devices, most of which have not been upgraded or rebooted in years. So I went through the normal debugging procedures that I know about. clogin works, rancid with debug "HIT"s all of the commands, but when I run it via "rancid-run -r <device>" it does not work. 
> 
> From the logs:
> 
> -------------------------------------------
> 
> Trying to get all of the configs.
> <device>: missed cmd(s): all commands
> <device> clogin error: Error: Connection closed (ssh): <device>
> <device>: End of run not found
> !
> =====================================
> Getting missed routers: round 1.
> <device>: missed cmd(s): all commands
> <device> clogin error: Error: Connection closed (ssh): <device>
> <device>: End of run not found
> !
> =====================================
> Getting missed routers: round 2.
> <device>: missed cmd(s): all commands
> <device> clogin error: Error: Connection closed (ssh): <device>
> <device>: End of run not found
> 
> 
> -------------------------------------------
> 
> 
> Is there any way to get the raw clogin output when running rancid-run sent to the log as well?
> 
> To recap, it works for most devices, but a few stopped working about a month ago and even though they work fine with clogin and rancid, cannot get it to work with rancid-run.


What version of rancid are you using?

The main point of departure in your results is that one uses router.db,
the other does not. I would start by verifying that router.db entries
for those problem devices are OK.


-- 
Alan McKinnon
alan.mckinnon at gmail.com



More information about the Rancid-discuss mailing list