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

[Alan McKinnon]

On 26/10/2015 18:44, Ken Celenza wrote:
> 
>> Sent: Monday, October 26, 2015 at 9:42 AM
>> From: "Alan McKinnon" <alan.mckinnon at gmail.com>
>> To: rancid-discuss at shrubbery.net
>> Subject: Re: [rancid] clogin and rancid good, rancid-run fails
>>
>> 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
>>
>> _______________________________________________
>> Rancid-discuss mailing list
>> Rancid-discuss at shrubbery.net
>> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>>
> 
> 
> Version "
> 
> $Id: rancid.in 2820 2014-04-25 19:03:59Z heas $
> rancid 3.1
> "

You should probably update top latest version if possible


> 
> Good call, but verified the router.db, and it's using ";". I actually think I have more of a hint. It is a suse server and was upgraded to suse 11 SP4, so I suspect one of those packages caused as issue. 
> 
> Any other suggestions?


I've had to debug an issue in this area only once; what I did was the
classic method: edit the rancid-run script and scatter print calls
throughout; and find the call to the actual rancid parser and launch
that with -d.

Then investigate further depending on what you find.

-- 
Alan McKinnon
alan.mckinnon at gmail.com