> Fyodor was unresponsive for a while today. This morning around 7:00 EST I > found load averages upwards of 30, and just now the system was totally > unresponsive. I seem to have caught it at the worst time when ssh and > http were totally unavailable for a while. > > [EMAIL PROTECTED]:~$ uptime > 14:57:48 up 3 days, 12:51, 11 users, load average: 101.25, 144.79, 92.69 > > spamd seems to be working pretty hard still but the load average is > dropping down to 13 now. Whatever was causing the system to become > unresponsive must have finished or gotten killed. > > > I'd like to hear if anyone has ideas about why this happened to see if we > can prevent it on the new server configuration.
Argh, did you run ps or top? It would seem unlikely that spamd alone could bring fyodor to its knees, but perhaps we got a particularly bad barrage? I don't know. I personally enabled spamassassin on my account recently and have added my extensive spam traffic to Spamassassin's load, but the extra work that Spamassassin does is offset by the reduced imap work. I set up my .forward file to send all spam > 9.0 to /dev/null, as a result a large proportion of my email is never even delivered to a mailbox. However, this may indicate that in the further future we will probably want to have mail and web on separate servers. Mail is a batch process whereas web transactions should be highly responsive. But immediately speaking performance should be substantially better at Peer1, and from the last couple emails I received things are pretty much ready to go. -ntk _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
