[rancid] rancid-run returning no output

[Alan McKinnon]

On 14/02/2015 19:44, Ryan Milton wrote:
> That is what I thought would debug, however, this is the output I get:
> 
> rancid at FP-RANCID:~$ rancid -d 10.50.1.1
> loadtype(): device_type is empty
> Couldn't load device type spec for
> rancid at FP-RANCID:~$*jrancid -d 10.50.1.1*
> jrancid: command not found
> rancid at FP-RANCID:~$*/usr/local/rancid/bin/jrancid -d 10.50.1.1*
> -bash: /usr/local/rancid/bin/jrancid: No such file or directory
> rancid at FP-RANCID:~$ cd /usr/local/rancid/bin
> rancid at FP-RANCID:/usr/local/rancid/bin$ jrancid -d 10.50.1.2
> jrancid: command not found
> rancid at FP-RANCID:/usr/local/rancid/bin$ jrancid -d 10.50.1.1



Those are Unix errors, you are not giving the correct path to the
jrancid executable. You need to find it and provide that directory path






> 
> 
> 
> Ryan Douglass Milton
> 
> 
> On Sat, Feb 14, 2015 at 3:23 AM, Alan McKinnon <alan.mckinnon at gmail.com
> <mailto:alan.mckinnon at gmail.com>> wrote:
> 
>     On 14/02/2015 02:32, Ryan Milton wrote:
>     > Hi all,
>     >
>     > I'm getting slowly closer to my goal...
>     >
>     > Rancid IS running...however, it seems that it may NOT be capturing
>     any configs.
>     > My original problem had been that I couldn't get the rancid-cvs to
>     function. That did work.
>     > running rancid v 3.1
>     > now, when I run the command:
>     >
>     > /usr/local/rancid/bin/rancid-run   or
>     > /usr/local/rancid/bin/rancid-run -r 10.50.1.1
>     >
>     > I get the following empty message :
>     >
>     > starting: Fri Feb 13 19:16:47 EST 2015
>     >
>     >
>     >
>     > ending: Fri Feb 13 19:16:47 EST 2015
>     > ~
>     > This  works:
>     > rancid at FP-RANCID:/usr/local/rancid/var/logs$ jlogin 10.50.1.3
>     > 10.50.1.3
>     > spawn ssh -c 3des -x -l rancid 10.50.1.3
>     > rancid at 10.50.1.3 <mailto:rancid at 10.50.1.3>'s password:
>     > --- JUNOS 12.3R8.7 built 2014-09-19 15:47:21 UTC
>     > {master:0}
>     > rancid at Distribution_North>
> 
> 
>     rancid -d <hostname>
> 
>     will give debug output so you can see what's going on.
> 
>     Looks like you have Junipers, so use
> 
>     jrancid for those instead. In either event, it's usually quite obvious
>     where the problem lies once you get proper debug output
> 
> 
> 
>     --
>     Alan McKinnon
>     alan.mckinnon at gmail.com <mailto:alan.mckinnon at gmail.com>
> 
>     _______________________________________________
>     Rancid-discuss mailing list
>     Rancid-discuss at shrubbery.net <mailto:Rancid-discuss at shrubbery.net>
>     http://www.shrubbery.net/mailman/listinfo/rancid-discuss
> 
> 


-- 
Alan McKinnon
alan.mckinnon at gmail.com