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 <h...@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
_______________________________________________ Rancid-discuss mailing list Rancid-discuss@shrubbery.net http://www.shrubbery.net/mailman/listinfo/rancid-discuss
