[SOLVED] CVS/Pserver issues

Q122 · 11-23-2011, 10:10 AM

This was working - but suddenly stopped...

I've got some cvs projects set up and all of my client users connect to the linux server via Eclipse. The server is configured to use pserver in xinetd.

My xinetd config is:

service cvspserver
{
disable = no
port = 2401
socket_type = stream
protocol = tcp
wait = no
user = root
passenv = PATH
server = /usr/bin/cvs
env = HOME=/var/cvs
server_args = -f --allow-root=/cvsroot pserver
# bind = 127.0.0.1
}

All of the users are in the cvs group and the projects under cvsroot are configured as follows:

total 48
drwsrwsr-x. 9 root cvs 4096 Nov 23 10:28 .
dr-xr-xr-x. 30 root root 4096 Nov 23 09:03 ..
drwsrwsr-x. 3 root cvs 4096 Nov 23 10:28 CVSROOT
drwxrwsrwx. 4 nobody cvs 4096 Nov 23 10:32 .lock
drwx-wS---. 2 root cvs 16384 Aug 14 09:10 lost+found
drwxrwsr-x. 5 u1 cvs 4096 Nov 14 10:10 P1
drwxrwsr-x. 14 u2 cvs 4096 Nov 23 09:52 P2
drwxrwsr-x. 5 root cvs 4096 Oct 17 12:20 P3
drwxrwsr-x. 10 root cvs 4096 Nov 16 09:21 p4

When I connect via eclipse and try to pull the P3 project (or any project, I get the following errors:

Error: P3: cvs log: failed to create lock directory for `/cvsroot/P3' (/cvsroot/.lock/P3/#cvs.lock): Permission denied
Error: P3: cvs log: failed to obtain dir lock in repository `/cvsroot/P3'

If I'm directly logged into the server with the same account and do a cvs checkout P3, it works fine.

Q122 · 11-23-2011, 02:02 PM

OK, on a whim, I created a cvs user added it to the cvs group, chown'ed everything in /cvsroot to cvs:cvs and updated the pserver to run as cvs instead of root.

No change. It really looks like xinetd is causing me a headache somehow.

Q122 · 11-25-2011, 08:18 AM

Got the answer - SELINUX getting me again.

Change /etc/selinux/config:

SELINUX=permissive

reboot.

deep27ak · 11-26-2011, 03:11 AM

Good to find the thread was solved but it might also happen due to permission issues inside P3 directory

As i was also having the same problem so made some changes in permission according to users and groups and my user was able to checkout the repository

I don't think xinetd plays much role in errors part at the time of checkout or import.

Q122 · 11-26-2011, 06:31 AM

Thanks Deep,

In my case, the users could checkout/import/commit just fine if they were logged into the linux system - they only had problems when they tried to use an over the network cvs connection like Eclipse.

That's what led me to xinet & SELinux.

--Will

deep27ak · 11-26-2011, 07:07 AM

Quote:

Originally Posted by Q122

Thanks Deep,

In my case, the users could checkout/import/commit just fine if they were logged into the linux system - they only had problems when they tried to use an over the network cvs connection like Eclipse.

That's what led me to xinet & SELinux.

--Will

I thought you were facing issues while checkout as I got the same error while doing checkout after logging in successfully
Any way I am replying so that anyone in future if face such problem they can look for both the options

While checkout if any such error comes

Code:

cvs checkout: cwd=E:\cvstest ,current=E:\cvstest
cvs checkout: failed to create lock directory for `/usr/local/cvsroot/CVSROOT' (/usr/local/cvsroot/CVSROOT/#cvs.history.lock): Permission denied
cvs checkout: failed to obtain history lock in repository `/usr/local/cvsroot'
cvs checkout: Updating test
cvs checkout: failed to create lock directory for `/usr/local/cvsroot/test' (/usr/local/cvsroot/test/#cvs.lock): Permission denied
cvs checkout: failed to obtain dir lock in repository `/usr/local/cvsroot/test'
cvs [checkout aborted]: read lock failed - giving up

Then manually lookout for those files and give required permission as per the user or group