[rancid] mtlogin error: Error TIMEOUT reached (2.3.8 deb)
Lukasz Sokol
el.es.cr at gmail.com
Thu Mar 26 15:13:22 UTC 2015
On 26/03/15 12:58, Lukasz Sokol wrote:
> On 26/03/15 11:19, Tim Warnock wrote:
>>> I googled and found one occurrence on this m/l when someone asked, is the
>>> router having a lot or routes,
>>> but that, as far as I could follow, wasn't answered; in my case, the answer is
>>> YES, and NO I can't put any less on it.
>>>
>>> Hope this can still be helped ;)
>>>
>>> el es
>>
>> Ok simple test.
>>
>> How long does an /export take if you run it from ssh/winbox?
>
> rancid at george:~$ time ~/bin/mtlogin -c "export" myrouter > /dev/null
>
> real 0m48.548s
> user 0m0.060s
> sys 0m0.024s
>
> and in test with a stopwatch,
>
> (doing ssh -i my_ident myuser at myrouter, then issuing export by hand)
>
> give or take 36s lag has been encountered
> after first 8s of running. Give or take because there were a few of them
> and not exactly sure how to catch...
>
Looking at run_commands,
it strikes me, that sending the command, it is allowed to timeout, just like that -
but unfortunately :
- trying to catch the timeout at first and making it go exp_continue instead, doesn't work
- trying to insert another expect clause in front of the main one, just to catch the timeout, doesn't work
Looks like this calls for a 'for' loop and checking whether the cause of expect breakout was timeout...
> hope this helps,
>
> el es
>
More information about the Rancid-discuss
mailing list