Mailing List Archive

Rancid issues
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...

--

Regards,
Chris Knipe
Re: Rancid issues [ In reply to ]
rancid version would help in troubleshooting...

On Wed, 2019-08-21 at 12:10 +0200, Chris Knipe wrote:
> 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...
>
> --
>
> Regards,
> Chris Knipe
>
>
> _______________________________________________Rancid-discuss mailing
> listRancid-discuss@shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>
Re: Rancid issues [ In reply to ]
My apologies :)

bash-4.2$ ./bin/rancid -V
rancid 3.9



On Wed, Aug 21, 2019 at 12:13 PM Vacheslav <m_zouhairy@skno.by> wrote:

> rancid version would help in troubleshooting...
>
> On Wed, 2019-08-21 at 12:10 +0200, Chris Knipe wrote:
>
> 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...
>
> --
>
> Regards,
> Chris Knipe
>
> _______________________________________________
>
> Rancid-discuss mailing list
>
> Rancid-discuss@shrubbery.net
>
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>
>
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss@shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>


--

Regards,
Chris Knipe
Re: Rancid issues [ In reply to ]
Hi,

The issue seems to be the -c"" (no /export command)

Not sure why rancid isn't passing the command to mtlogin

On Wed, Aug 21, 2019 at 12:16 PM Chris Knipe <savage@savage.za.org> wrote:

> My apologies :)
>
> bash-4.2$ ./bin/rancid -V
> rancid 3.9
>
>
>
> On Wed, Aug 21, 2019 at 12:13 PM Vacheslav <m_zouhairy@skno.by> wrote:
>
>> rancid version would help in troubleshooting...
>>
>> On Wed, 2019-08-21 at 12:10 +0200, Chris Knipe wrote:
>>
>> 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...
>>
>> --
>>
>> Regards,
>> Chris Knipe
>>
>> _______________________________________________
>>
>> Rancid-discuss mailing list
>>
>> Rancid-discuss@shrubbery.net
>>
>> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>>
>>
>> _______________________________________________
>> Rancid-discuss mailing list
>> Rancid-discuss@shrubbery.net
>> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>>
>
>
> --
>
> Regards,
> Chris Knipe
>


--

Regards,
Chris Knipe
Re: Rancid issues [ In reply to ]
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

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss
Re: Rancid issues [ In reply to ]
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 <heas@shrubbery.net> 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
Re: Rancid issues [ In reply to ]
Wed, Aug 21, 2019 at 02:44:01PM +0000, john heasley:
> 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
>

I've fixed this here:
commit 4750bf3ee31cd11a299a1dfee2c8c36020f41479
rancid, rancid.pm: handle non-modulized rancid scripts in the rancid script
by exec()ing the real script

https://www.shrubbery.net/pipermail/rancid-discuss/2019-August/010820.html

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss