[p4] Anyone experienced these perforce problems?
karish at well.com
Wed Jun 27 12:16:21 PDT 2001
At 02:02 PM 6/27/2001 -0400, Rajesh Vaidheeswarran wrote:
> > >We have been encountering *very long* delays from the client side
> > >for many p4 commands .. a p4 edit which typically returns in under a
> > >second returns at times after 10 minutes! Most often it times out..
> > What times out? My experience is that neither the Perforce server
> > nor the client time out on their own. Are attempts to open connections
> > timing out after four minutes?
>The client side errors out with something like this. But its not always the
>same error. I'm collecting the various types of errors that we are seeing.
>Perforce client error:
> Connection with partner closed unexpectedly.
> TCP receive failed.
> read: socket: WSAECONNRESET
That's the message you'd see if the user were to terminate the connection
from the client side. Are you sure that they're not doing that?
> > The messages you showed us all look like reports of client/server
> > not server/fileserver problems. Many of them are the usual messages I
> > expect to see when a user interrupts a long-running client process or when
> > a bad client spec is used (non-existent local Root).
>How do you say so? It looks like they are client-server problems, but I am
>sure if they are (or are not) server/fileserver problems too.
The messages about access denied refer to files in the client workspace,
not in the depot.
Chuck Karish karish at well.com (415) 317-0182
More information about the perforce-user