[Top][All Lists]

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

RE: are there any log files for cvs client/server connection information

From: Teala Spitzbarth
Subject: RE: are there any log files for cvs client/server connection information?
Date: Tue, 14 May 2002 12:35:15 -0700

Thanks for your reply David,

- we are using pserver access
- the checkout proceeded through about 1/3 of the files in the module,
the hang happened after pulling over (successfully) a 15Mb file, and
(presumably) during pulling over the next file in that directory (6Mb).
- The checkout was recorded in the history file

I think you are right that the origin of the problem was a network
issue, probably slowness caused a time-out on the server side process?
However the client side was still hanging there waiting for more info
from the server side (which was long gone 15 hours at least). I was just
wondering if there was any way (either client side or server side) to
get more information about why the cvs connection had died. Like anyway
to enable debugging in the cvs binary so when pserver connection die the
server and the client write information to a log file about what the
heck is going on?  The cvs process on the client (Solaris) side was just
in sleep mode when we looked at it with a debugger.  

You are right I need to upgrade and I've been wanting to upgrade since
last Oct when Larry got some fixes to log in that I really need -
however I'm in a commercial environment and need to time the upgrade
with our release schedule and also need to have standard packages issued
by Red Hat and Sun Freeware before I can do it (i.e hand built versions
of cvs aren't considered acceptable on a production system).  I hope to
go to cvs 1.11.2 as soon as those packages become available.  

I am also blocked from setting up a new repository to prototype a new
version of CVS, due to another pserver problem. This is the other reason
I am asking this question about cvs pserver debugging log files - I am
having other access problems with pserver connections over *any*
repositories, other than my main source repository.  E.g. access to my
main repository works fine - but I have two other cvspserver ports set
up for alternate test repositories.  Access to these other repositories
used to work fine - but in the last several months they suddenly stopped
working.  I can't get pserver access to any new repositories (on any
linux systems) to work, and I am using all the exact same inetd
configuration as used to work on these systems. Permissions on secondary
repository directories are open and aren't blocking access, we are using
the server system password access (ie. not using CVSROOT/passwd).

This is the error message I get:
address@hidden teala]$
address@hidden teala]$ cvs login
(Logging in to address@hidden)
CVS password:
cvs [login aborted]: authorization failed: server
rejected access   

However if I just change the CVSROOT variable to our main repository...
it all works fine!

address@hidden teala]$
address@hidden teala]$ cvs login
(Logging in to address@hidden)
CVS password: 
address@hidden teala]$ cvs co build
cvs server: Updating build
U build/athena_nightly.rc
U build/
U build/beta_nightly.rc
U build/
U build/
U build/cpship.rsh
U build/
U build/
U build/
U build/
U build/  


cvspserver      stream  tcp     nowait.600      root    /usr/bin/cvs cvs
-f --allow-root=/raid/cvsroot pserver

cvspserver2     stream  tcp     nowait.600      root    /usr/bin/cvs cvs
-f --allow-root=/raid/home/teala/cvsroot pserver

cvspserver3     stream  tcp     nowait.600      root    /usr/bin/cvs cvs
-f --allow-root=/raid/cvsroot-old pserver 


cvspserver      2401/tcp                        # CVS client/server
cvspserver      2401/udp                        # CVS client/server
cvspserver2     2402/tcp                        # CVS client/server
cvspserver2     2402/udp                        # CVS client/server
cvspserver3     2403/tcp                        # CVS client/server
cvspserver3     2403/udp                        # CVS client/server

Any help or illumination you could shed on how to debug either the
pserver checkout 'hang' or, more importantly, this pserver access
problem, would be greatly appreciated!


reply via email to

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