[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Serious cvs tag/rtag issues Please help

From: Todd Denniston
Subject: Re: Serious cvs tag/rtag issues Please help
Date: Fri, 05 Oct 2007 09:19:25 -0500
User-agent: Thunderbird (X11/20070728)

Pranab Panda (pkpanda) wrote, On 10/05/2007 01:17 AM:
Hi All

In last couple of days our cvs server has gone done few times,

You mean like power outage/hardware fail???

Checkin and checkout work fine, but
since this afternoon I see errors with cvs tag and rtag commands.
They both fail with following error
cvs [rtag aborted]: could not open lock file
`/auto/cvsroot/repository/Files/,file12,': File exists

I am clueless how to fix this.
Please help if know whats the issue
this is very critical!

NOTE: cvs --version Concurrent Versions System (CVS) 1.11.2 (client/server)
On Linux 2.4.21-27.0.1.ELsmp #1 SMP Mon Dec 20 18:47:45 EST 2004 i686
i686 i386 GNU/Linux

Thanks in advance

1) make a backup[1] of what you have... immediately.
2) if it was power/hardware fail, A) you should get new UPS/hardware, B) probably fsck the drive with the repo on it. 3) `locate check_cvs; locate validate_repo` one of these should be on the system in a cvs/contrib directory (assuming a nice Linux distro), Otherwise you can beat the .in file[2] into shape.
4) `perldoc check_cvs || perldoc validate_repo`
5) use one of check_cvs || validate_repo on your repository to see what other problems you have.

6) with the ",filename," files, I _think_ you should see if there are usernames on them (if you are using pserver there might not be real ones) and if so ask those users to finish their broken commits.
7) if you think it appropriate, make a new backup.
8) ask the group again about help with the new problems if needed.
9) upgrade to a much newer CVS/verify RH has updated for all the security problems found since 1.11.2.

Good luck.


Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]