Server crashed and RANCID somehow restored a two year old version

[john heasley]

Mon, Dec 29, 2003 at 11:18:30AM -0500, Elliott, Andrew:
> 
> > It could also be that someone has purposely done it.  You can 
> > check for
> > other revisions (ie: newer than the one you're seeing) with 
> > cvs log; eg:
> > 
> > 	cd /usr/local/rancid/groupfoo/configs
> > 	cvs log router.foo.net | less
> 
> 10:05am  rancid at bosshogg:/routers/Backbone/Cisco/configs> cvs log
> chr1.nyc-ny | less
> 
> RCS file: /tftpboot/routers/Backbone/CVS/Cisco/configs/chr1.nyc-ny,v
> Working file: chr1.nyc-ny
> head: 1.23
> branch:
> locks: strict
> access list:
> symbolic names:
> keyword substitution: o
> total revisions: 23;    selected revisions: 23
> description:
> ----------------------------
> revision 1.23
> date: 2003/12/29 06:14:16;  author: rancid;  state: Exp;  lines: +1377
> -566
> updates
> ----------------------------
> revision 1.22
> date: 2002/05/17 05:06:56;  author: rancid;  state: Exp;  lines: +117 -8
> updates
> ----------------------------

hmm.  Given the revs are serial, there are only 23, and the jump in dates;
I'd guess that either rancid had trouble committing updates (see the log
files) and the errors were ignored, the CVS file was damaged in the crash
(check the ",v" RCS file and compare to your backups), or someone mucked
with the cvs file.

Note: I do not recommend manually mucking with the respository (ie:
/tftpboot/routers/backbone/CVS in this case) in any fashion.