Re: Need help please: "writing to server socket" error

[Dennis Jones]

The server has been working so well for so long, I have had no reason to
mess with anything, other than to set up some new repositories a few months
ago, which of course does not affect the existing clients.  And that's what
makes this problem so weird -- nothing has changed anywhere -- neither on
the server nor the client.

The client has always been authorized to use the server, and continues to be
(apparently) since he can checkout new sandboxes, and still do updates (most
of the time).  It seems to be a sporatic problem.  He can do an update once
and have it work, then again a minute later and have a problem.  Sometimes
he will get the "writing to server socket" error, sometimes it will just
seem to hang during the update, and sometimes it will work fine.

I had him do one more fresh checkout of the tree, and haven't had any more
complaints since.  At this point, I can only hope it will continue to work
as before.  Maybe it was just some momentary interuptions in his Internet
connection?

- Dennis

----- Original Message -----
From: "Larry Jones" <address@hidden>
To: "Dennis Jones" <address@hidden>
Cc: <address@hidden>
Sent: Thursday, February 14, 2002 5:12 PM
Subject: Re: Need help please: "writing to server socket" error

> How about security settings -- tcpd, perhaps?  A connection reset means
> that the server machine accepted the connection, but then closed it.
> CVS doesn't do that unless some kind of very serious error occurs
> (typically a crash), but inetd will do it if it can't run the server
> (which doesn't seem likely since others can run it successfully) and
> things like tcpd will do it if the client isn't authorized to use the
> server.