Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hi all! I want to move our cvsserver / repository to a new machine. The old one was RedHat, the new one is Debian 2.6.18-4-amd64. CVSNT version on both machines is: (CVSNT) 2.5.03 (On new machine the build is 2382.) I copied the complete repository to the new machine (file system structure is identical) and checked the owner/group and access rights. Following the README.Debian for cvsnt, I changed /etc/cvsnt/PServer: Repository0=/mnt/raid/cvs Repository0Name=/mnt/raid/cvs #Repository0Description=My Repository Repository0Default=1 #Repository0Publish=1 #Repository0Online=1 # # Encryption 0=Don't force encryption, EncryptionLevel=0 # # Compression 0=Don't force compression CompressionLevel=0 # # LockServer Default lock server location. Can be overridden by # LockServer directive in individual repositories. LockServer=NewServer:2402 # # ResponderType Set Zeroconf publication type. Default dependent on platform. # 0 - No publication #ResponderType=0 (the rest is comment with #) In /etc/service there are entries cvspserver 2401/tcp cvspserver 2401/udp In /etc/inetd.conf there is an entry cvspserver stream tcp nowait root /usr/bin/cvsnt cvsnt -f authserver Logging in succeeds: cvs -d:pserver:MyUser at NewServer:/mnt/raid/cvs login (from Windows console and directly on Debian) Checkout doesn't succeed: cvs -d:pserver:MyUser at NewServer:/mnt/raid/cvs checkout MyModule Error message: cvs [checkout aborted]: cvsnt server: connect to NewServer(NewServer):2402 failed: Connection refused OK, lockserver seems to be not running. Starting it in debug mode shows: NewServer:# cvslockd -d Initialising socket... Starting lock server on port 2402/tcp... Using default mdns Responder Loading miniMdns Publishing mdns records for server7._cvspserver._tcp Segmentation fault Here http://www.cvsnt.org/pipermail/cvsnt-dev/2006-January/000335.html I found a similar message. They detected that there was no configuration at all, but I HAVE a configuration, I think (see above). Then I found an "outstanding bug" for Debian: "cvsnt: cvslockd crashes at startup": http://bugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=441236 As proposed, I set ResponderType=0 in /etc/cvsnt/PServer. Now starting the lockserver seems to succeed, there is a process cvslockd. But cvs [...] checkout MyModule still doesn't work! The cvs init command also doesn't work: cvs -d :local:/mnt/raid/cvs init cvs init: connect to NewServer(NewServer):2402 failed: Connection refused cvs [init aborted]: Couldn't connect to lock server Any idea what to do? Thanks in advance, Melanie