[Spread-users] why is the spread client being disconnected?

[Mark Blackman]

Hi,

I've got a mod_perl application using ultimately Spread.pm (3.17) on a
solaris 10 machine either disconnecting or being disconnected  
arbitrarily
after a few dozen messages.

In the spread (daemon) log, I see,

[Mon 02 Jul 2007 16:23:39] G_handle_kill: #1858ffxws0#ffxws02p1 is  
killed
[Mon 02 Jul 2007 16:23:39] G_handle_kill in GOP
[Mon 02 Jul 2007 16:23:39] G_handle_kill: Mask for group webapp set  
to 0 0 0 3

In the solaris truss output of the apache child (spread client), I see

13.2293 send(18, "A0\0\080 # 1 8 5 8 f f x".., 80, 0)   = 80
13.2302 send(18, " 2 0 0 7 - 0 7 - 0 2   1".., 194, 0)  Err#32 EPIPE
13.2303     Received signal #13, SIGPIPE [ignored]

EPIPE meaning the connection is closed for writing (where previous  
'send'
calls didn't get an EPIPE signal).

I *believe* this suggests the spread daemon is killing the handle for  
some
reason. I don't have any evidence that the spread client is closing  
the connection,
so perhaps someone can suggest why the spread daemon (or client)  
might arbitrarily
close the connection.

Cheers,
Mark