Re: [rancid] Rancid issues

--===============3834693529708093126==
Content-Type: multipart/alternative; boundary="0000000000003315d20590a1b8cd"

--0000000000003315d20590a1b8cd
Content-Type: text/plain; charset="UTF-8"

Hi all,

We used an AWS Linux image to run rancid on - expect there is an issue with
either TCL and/or expect.

Trashed the box and went to an ubuntu image instead, and everything is
working fine.

Thanks.


On Wed, Aug 21, 2019 at 4:44 PM john heasley <[email protected]> wrote:

> Wed, Aug 21, 2019 at 12:10:35PM +0200, Chris Knipe:
> > Hi All,
> >
> > Rancid setup and everything's fine form what I can tell.  I'm getting a
> > strange error I haven't seen before:
> >
> > router.db:
> > za-ctn-pe01;mikrotik;up
> >
> > bash-4.2$ ./bin/rancid -d -t mikrotik za-ctn-pe01
> > loadtype: device type mikrotik
> > loadtype: found device type mikrotik in /srv/rancid/etc/rancid.types.base
> > executing mtlogin -t 90 -c"" za-ctn-pe01
> > inloop is not configured for device type mikrotik at ./bin/rancid line
> 130.
> >
> > Not quite sure what is happening at this stage...
>
> bin/rancid does not work this way with scripts that have not been converted
> to modules.  It could be made to work, I just had not anticipated it.  you
> must run the script itself.
>
> mtrancid [opts] hostname
>


-- 

Regards,
Chris Knipe

--0000000000003315d20590a1b8cd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>We used an AWS Linux image to r=
un rancid on - expect there is an issue with either TCL and/or expect.</div=
><div><br></div><div>Trashed the box and went to an ubuntu image instead, a=
nd everything is working fine.</div><div><br></div><div>Thanks.</div><div><=
br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gma=
il_attr">On Wed, Aug 21, 2019 at 4:44 PM john heasley &lt;<a href=3D"mailto=
:[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">Wed, Aug 21, 2019 at 12:10:35PM +020=
0, Chris Knipe:<br>
&gt; Hi All,<br>
&gt; <br>
&gt; Rancid setup and everything&#39;s fine form what I can tell.=C2=A0 I&#=
39;m getting a<br>
&gt; strange error I haven&#39;t seen before:<br>
&gt; <br>
&gt; router.db:<br>
&gt; za-ctn-pe01;mikrotik;up<br>
&gt; <br>
&gt; bash-4.2$ ./bin/rancid -d -t mikrotik za-ctn-pe01<br>
&gt; loadtype: device type mikrotik<br>
&gt; loadtype: found device type mikrotik in /srv/rancid/etc/rancid.types.b=
ase<br>
&gt; executing mtlogin -t 90 -c&quot;&quot; za-ctn-pe01<br>
&gt; inloop is not configured for device type mikrotik at ./bin/rancid line=
 130.<br>
&gt; <br>
&gt; Not quite sure what is happening at this stage...<br>
<br>
bin/rancid does not work this way with scripts that have not been converted=
<br>
to modules.=C2=A0 It could be made to work, I just had not anticipated it.=
=C2=A0 you<br>
must run the script itself.<br>
<br>
mtrancid [opts] hostname<br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><br>Regards,<br>Chris Knipe<br></div>

--0000000000003315d20590a1b8cd--


--===============3834693529708093126==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Rancid-discuss mailing list
[email protected]
http://www.shrubbery.net/mailman/listinfo/rancid-discuss

--===============3834693529708093126==--