heas at shrubbery
Aug 16, 2012, 2:12 PM
Post #1 of 1
(784 views)
Permalink
|
|
Re: missed cmd(s): show full-configuration, get system status
|
|
Thu, May 31, 2012 at 12:20:30PM +0000, Gerhard Mourani:
> Thanks Gareth,
>
> That's worked for me too.
>
> Gerhard,
>
> From: Gareth Hopkins [mailto:gabbawp [at] gmail]
> Sent: May-31-12 4:30 AM
> To: Gerhard Mourani
> Cc: rancid-discuss [at] shrubbery
> Subject: Re: [rancid] missed cmd(s): show full-configuration,get system status
>
> Hi,
>
> If you run fnlogin instead of clogin, you'll see it complains about an ssh port not being specified. I ran into exactly the same problem and mailed the list a couple of weeks ago but heard nothing back unfortunately.
>
> A quick work around is to add the following to your cloginrc file
>
> add method device_name {ssh:22}
>
> I hope someone can take a look at this though.
Does this patch to fnlogin fix your problem:
Index: bin/fnlogin.in
===================================================================
--- bin/fnlogin.in (revision 2376)
+++ bin/fnlogin.in (revision 2435)
@@ -303,7 +303,7 @@
} elseif [string match "ssh*" $prog] {
regexp {ssh(:([^[:space:]]+))*} $prog methcmd suffix port
set cmd $sshcmd
- if {"$port" == ""} {
+ if {"$port" != ""} {
set cmd "$cmd -p $port"
}
set retval [ catch {eval spawn [split "$cmd -c $cyphertype -x -l $user $router" { }]} reason ]
>
> Cheers,
>
> Gareth
>
> On 30 May 2012, at 7:06 PM, Gerhard Mourani wrote:
>
>
> Helo list,
>
> After an update to Rancid version 2.3.8, the method used to login into FortiGate device no longer work and report the following error in the log file.
>
> Getting missed routers: round 4.
> 192.168.2.1 fnlogin error: Error: Couldn't login: 192.168.2.1
> 192.168.2.1: missed cmd(s): show full-configuration,get system status
> 0: found end
> 192.168.2.1: End of run not found
>
> With previous version of Rancid, everything worked correctly. According to the above error I've run the following commands to verify if the missed cmd is true or not.
>
> /usr/bin/clogin -f /usr/share/rancid/.cloginrc 192.168.2.1
> The above works and I can manually run the 'show full-configuration' or 'get system status' command without problem!
>
> Therefore no idea about why this error occur now and from which part it's really coming from!
>
> Gerhard,
_______________________________________________
Rancid-discuss mailing list
Rancid-discuss [at] shrubbery
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
|
