<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br>Am 25.09.2014 um 10:07 schrieb Dan Anderson <<a href="mailto:dan.w.anderson@gmail.com">dan.w.anderson@gmail.com</a>>:</div><div><br></div><blockquote type="cite"><div><div dir="ltr">It's a Raspberry Pi running Raspian. I can get you access to the box if you'd like it.</div></div></blockquote><div><br></div>Iirc, thats what that user had, so yes please. <div><br><blockquote type="cite"><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 25, 2014 at 10:12 AM, John Heasley <span dir="ltr"><<a href="mailto:heas@shrubbery.net" target="_blank">heas@shrubbery.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Am Sep 24, 2014 um 4:09 PM schrieb Dan Anderson <<a href="mailto:dan.w.anderson@gmail.com" target="_blank">dan.w.anderson@gmail.com</a>>:</div><div><div class="h5"><div><br></div><blockquote type="cite"><div><div dir="ltr">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:<div><br></div><div>
<p>Trying to get all of the configs.</p>
<p>usage: par [-dfiqx] [-n #] [-p n] [-l logfile] [-c command] [<command file>]</p>
<p>=====================================</p>
<p>Getting missed routers: round 1.</p>
<p>usage: par [-dfiqx] [-n #] [-p n] [-l logfile] [-c command] [<command file>]</p>
<p>=====================================</p>
<p>Getting missed routers: round 2.</p>
<p>usage: par [-dfiqx] [-n #] [-p n] [-l logfile] [-c command] [<command file>]</p>
<p>=====================================</p>
<p>Getting missed routers: round 3.</p>
<p>usage: par [-dfiqx] [-n #] [-p n] [-l logfile] [-c command] [<command file>]</p>
<p>=====================================</p>
<p>Getting missed routers: round 4.</p>
<p>usage: par [-dfiqx] [-n #] [-p n] [-l logfile] [-c command] [<command file>]</p>
<p><br></p><p><br></p><p>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. </p><p>I chucked an "echo" after the call to par in control_rancid and got this:</p><p>
</p><p>par -q -n 5 -c 'rancid-fe "{}"' /usr/local/rancid/var/home/routers.up</p><p><br></p><p>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.</p></div></div></div></blockquote><div><br></div></div></div>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?<span class="HOEnZb"><font color="#888888"><div><br><blockquote type="cite"><div><div dir="ltr"><div>-- <br>Dan
</div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Rancid-discuss mailing list</span><br><span><a href="mailto:Rancid-discuss@shrubbery.net" target="_blank">Rancid-discuss@shrubbery.net</a></span><br><span><a href="http://www.shrubbery.net/mailman/listinfo/rancid-discuss" target="_blank">http://www.shrubbery.net/mailman/listinfo/rancid-discuss</a></span></div></blockquote></div></font></span></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Dan
</div>
</div></blockquote></div></body></html>