Broken Pipe error

The solution to this problem has not yet been found. The client writer (Server_Writer_Client) can delete a client from the server list using the socket but then the client could still be processed. Processing does not quit when a client was deleted outside the loop.

Goedzo
Daan Sprenkels

<email address hidden>
https://launchpad.net/~dsprenkels

On Fri, Sep 18, 2009 at 23:18, Wouter Bulten <email address hidden>wrote:

> The solution to this problem has not yet been found. The client writer
> (Server_Writer_Client) can delete a client from the server list using
> the socket but then the client could still be processed. Processing does
> not quit when a client was deleted outside the loop.
>
> ** Branch linked: lp:mai-server
>
> ** Branch linked: lp:mai-server/0.1
>
> ** Tags added: server-writer-client
>
> --
> Broken Pipe error
> https://bugs.launchpad.net/bugs/432112
> You received this bug notification because you are a member of Mai Bug
> Team, which is subscribed to Mai Project.
>
> Status in Mai Server: Confirmed
>
> Bug description:
> While having the server running and quitting the client without
> disconnecting, the server will give Broken Pipe errors. This keeps looping
> and then server will never reinitialize.
>
> Warning: socket_write(): unable to write to socket [32]: Broken pipe in
> /home/sprenkels/Dropbox/Infostuff/mai-server/application/Server/Writer/Client.php
> on line 69
>

There is some progress with this bug. Users are now removed from the client list when the connection is lost. The server will also not send a disconnect message to client.

There are still some broken pipe errors caused by unknown input send to the server.

If a user sent a command before he disconnected no errors occur. In this case the server will show a message that the client is disconnected.

If a user disconnect without having sent any commands the server still returns broken pipe errors.

Fix commited. See commit 20.