[p4] Has anyone seen these p4d errors before?
Robert McKenna
robertm at bioware.com
Tue Dec 11 07:57:47 PST 2007
I've seen them when users cancel commands. In our case it was an
indication of an overloaded server as users often thought their clients
were hanging.
-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Stephen Vance
Sent: Monday, December 10, 2007 7:04 PM
To: Ivey, William
Cc: Perforce User
Subject: Re: [p4] Has anyone seen these p4d errors before?
Could be network, but I think you can also get these with a canceled
command.
Steve
Ivey, William wrote:
> Perforce server error:
>
> Date 2007/12/10 09:14:50:
>
> Connection from [xx.xx.xx.xx] broken.
>
> TCP send failed.
>
> write: socket: No child processes
>
>
>
> Perforce server error:
>
> Date 2007/12/10 07:15:40:
>
> Connection from [xx.xx.xx.xx] broken.
>
> TCP send failed.
>
> write: socket: Bad file descriptor
>
>
>
> The [xx.xx.xx.xx] are various ip addresses, not always the same one.
>
> Anyone know what the likely causes are? (I'm guessing network,
>
> and IT is being informed, but...)
>
>
>
> Thanks.
>
>
>
> -Wm
>
> _______________________________________________
> perforce-user mailing list - perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>
--
Stephen Vance
www.vance.com
_______________________________________________
perforce-user mailing list - perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
More information about the perforce-user
mailing list