[Spread-users] unix domain socket in /tmp and diskfull

[Yair Amir]

Hi,

You should move to 3.17.0 which solved these problems.

    :) Yair.
    
On Thursday, April 10, 2003 3:47 PM
Aditya Aditya aditya at grot.org wrote:

Aditya> I just had a cascading failure of several webservers that all use spread to
Aditya> log. The webservers became sluggish and unresponsive and I noticed that
Aditya> nothing was being logged via spread. I use spread 3.16.2 on FreeBSD 4-STABLE.
Aditya> This cluster of spread-enabled servers has been up and running for around 7
Aditya> months without any spread problems...it's possible that in the last 3 weeks we
Aditya> have been seeing a lot more traffic and consequently many more spread
Aditya> messages...

Aditya> Typically, running spmonitor yields something like:

Aditya>   Status at server1 V 3.16. 2 (state 1, gstate 1) after 2673 seconds :

Aditya> for each spread daemon (== servers in my case).

Aditya> however, when this problem occurred, all the spread daemons were in gstate 3,
Aditya> ie:

Aditya>   Status at server1 V 3.16. 2 (state 1, gstate 3) after 12321 seconds :

Aditya> Since stopping/starting individual spread daemons did not seem to change that,
Aditya> I stopped all the spread clients, spread daemons and restarted them all and it
Aditya> seems "okay" now. The only thing I can think of is that *after* I noticed all
Aditya> the daemons in gstate 3, /tmp on one of the servers started complaining it was
Aditya> full. The default spread socket is put in /tmp/4803 and that makes me
Aditya> suspicious...

Aditya> Any clues to what I should be looking for?

Aditya> Thanks,
Aditya> Adi

Aditya> _______________________________________________
Aditya> Spread-users mailing list
Aditya> Spread-users at lists.spread.org
Aditya> http://lists.spread.org/mailman/listinfo/spread-users