A clarification: I meant that multiple sa-learn processes caused DOS. And: this occurred because somehow over 517 messages were dumped into SiteSpam. sa-learn couldn't gobble it up in time before cron spawned another sa-learn process. iirc, 4 processes total were spawned, and at one point, 1.3gb of swap was filled.
This lasted over an hour. I'd say 1.5 hours. That's significant. Best, Ryan > Hey, > there happened to be multiple DOS causing sa-learns spawned tonight. The > swap was thrashing, things were at a standstill except for basic shell > operations. I suggest we avoid this by modifying the script called by > cron to check if a pid exists for sa-learn, and to die if it does. I > haven't tested this, but it might look something like: > #!/bin/bash > pid=`pidof -s sa-learn` > if [ $pid ]; then > echo "sa-learn already spawned" > else > echo "sa-learn can be spawned" > fi > > Any other input to prevent this from occuring again? Something like this > should definitely be on the new servers. > > Cheers! > Ryan > > _______________________________________________ > HCoop-SysAdmin mailing list > [email protected] > http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin > _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
