[rancid] "upgrade" to 3.1 breaks par?
Heasley
heas at shrubbery.net
Thu Sep 25 19:02:10 UTC 2014
Am 25.09.2014 um 10:07 schrieb Dan Anderson <dan.w.anderson at gmail.com>:
>
> It's a Raspberry Pi running Raspian. I can get you access to the box if you'd like it.
Iirc, thats what that user had, so yes please.
>
>> On Thu, Sep 25, 2014 at 10:12 AM, John Heasley <heas at shrubbery.net> wrote:
>>> Am Sep 24, 2014 um 4:09 PM schrieb Dan Anderson <dan.w.anderson at gmail.com>:
>>>
>>> I "upgraded" by installation from 2.3.8 to 3.1 this morning. By upgrade, I mean "back up, rm -rf etc bin var share lib, make install" and I keep getting par syntax errors in the logs:
>>>
>>> Trying to get all of the configs.
>>>
>>> usage: par [-dfiqx] [-n #] [-p n] [-l logfile] [-c command] [<command file>]
>>>
>>> =====================================
>>>
>>> Getting missed routers: round 1.
>>>
>>> usage: par [-dfiqx] [-n #] [-p n] [-l logfile] [-c command] [<command file>]
>>>
>>> =====================================
>>>
>>> Getting missed routers: round 2.
>>>
>>> usage: par [-dfiqx] [-n #] [-p n] [-l logfile] [-c command] [<command file>]
>>>
>>> =====================================
>>>
>>> Getting missed routers: round 3.
>>>
>>> usage: par [-dfiqx] [-n #] [-p n] [-l logfile] [-c command] [<command file>]
>>>
>>> =====================================
>>>
>>> Getting missed routers: round 4.
>>>
>>> usage: par [-dfiqx] [-n #] [-p n] [-l logfile] [-c command] [<command file>]
>>>
>>>
>>>
>>>
>>>
>>> I ended up moving the par binary out of the way and restoring the perl version from 2.3.8 and it seems to have resolved my issue for now, but it's not really an ideal fix.
>>>
>>> I chucked an "echo" after the call to par in control_rancid and got this:
>>>
>>> par -q -n 5 -c 'rancid-fe "{}"' /usr/local/rancid/var/home/routers.up
>>>
>>>
>>>
>>> I haven't spent a lot of time on this at the moment, but I thought I would see if anyone else has run across this (I didn't see anything in the archives for the last few months) and might have an easy fix.
>>>
>>
>> Another user had a problem like this; they were on some embedded platform version of linux. I had no manner of helping them. What are you using?
>>
>>> --
>>> Dan
>>> _______________________________________________
>>> Rancid-discuss mailing list
>>> Rancid-discuss at shrubbery.net
>>> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>
>
>
> --
> Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20140925/7168b2cd/attachment.html>
More information about the Rancid-discuss
mailing list