[rancid] rancid finding changes that do not exist

[heasley]

Thu, Mar 12, 2015 at 10:36:26PM +0200, Alan McKinnon:
> On 12/03/2015 22:05, Jason Humes wrote:
> > Hi
> > We've got some devices that rancid thinks have changed but have not, for example;
> > 
> > 
> > Index: configs/acs_internetmonitoringfirewall
> > ===================================================================
> > - -- configs/acs_internetmonitoringfirewall	(revision 3422)
> > @@ -344,13 +344,13 @@
> >   ip http secure-server
> >   ip http secure-port 4444
> >   !
> > + ip nat inside source static tcp 142.46.14.24 21 interface 
> > + FastEthernet0/0 21 ip nat inside source static tcp 142.46.14.172 443 
> > + interface FastEthernet0/0 443 ip nat inside source static tcp 
> > + 142.46.14.172 80 interface FastEthernet0/0 80
> >   ip nat inside source static udp 142.46.14.167 162 interface FastEthernet0/0 162
> >   ip nat inside source static udp 142.46.14.163 69 interface FastEthernet0/0 69
> >   ip nat inside source static udp 142.46.14.19 514 interface FastEthernet0/0 514
> >   ip nat inside source static udp 142.46.14.169 9996 interface FastEthernet0/0 9996
> > - ip nat inside source static tcp 142.46.14.24 21 interface FastEthernet0/0 21
> > - ip nat inside source static tcp 142.46.14.172 443 interface FastEthernet0/0 443
> > - ip nat inside source static tcp 142.46.14.172 80 interface FastEthernet0/0 80
> >   ip nat inside source route-map nat interface FastEthernet0/0 overload
> >   ip route 10.1.0.0 255.255.0.0 172.31.230.225
> > =================================================================
> > 
> > The line;
> > 
> > + ip nat inside source static tcp 142.46.14.24 21 interface 
> > + FastEthernet0/0 21
> > 
> > Is actually;
> > ip nat inside source static tcp 142.46.14.24 21 interface FastEthernet0/0 21
> > 
> > Which rancid says was remvoed (-ip nat inside source static tcp 142.46.14.24 21 interface FastEthernet0/0 21)
> > 
> > Any idea why it is parsing the text like this?
> 
> 
> You seem to have a bunch of newlines removed. Considering how rancid
> works, it's hard to imagine that the bug is happening inside rancid
> itself, so maybe the device itself is doing it? But, the previous time
> rancid ran, it parsed the input correctly. Interesting....
> 
> 
> What kind of device is this, what rancid version are you using, and what
> device type have you configured the firewall as?

and is the login script able to disable the pager on this device?