Hi,

at squid-cache.org we have a problem with "cvs server" processes 
getting stuck att 100% CPU and needing to get killed by "kill -9" to 
go away. A nice kill -TERM or kill -HUP does not help.


We are currently running

  Concurrent Versions System (CVS) 1.11.2-FreeBSD (client/server)

And as it only seems to be me who triggers the problem: via normal ssh 
server connections using cvs 1.11.1, 1.11.2 or 1.10.7 clients (RedHat 
Linux packages).

It seems the problems started after the last upgrade of the server (14 
Nov). I do not know which version of CVS we were running before.


A truss of the hung processes show nothing. Unfortunately the binary 
is stripped so I can't get much of a stack trace at this time.

Before digging into the problem too deaply I wonder if there is 
anything known about such issues with 1.11.2 or the FreeBSD port 
thereof. Did not find anything immediately striking in the bug-cvs 
archives however..

It does not seem these processes keeps any locks in the CVS tree, and 
I am not yet sure what/when this problem is triggered as I have 
several more or less automated CVS jobs running plus doing a fair 
share of interactive usage, but a gut feeling is that the problem 
might be caused if the cvs job is aborted by the client. However, 
this is not by any means a strong feeling and the little data I have 
on the hung processes is not entirely consistent with this feeling.


Regards
Henrik Nordström
Squid HTTP Proxy cache project


_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs

Reply via email to