On 8/5/10 9:51 PM Paul Lesniewski wrote: >> The only time that I have seen this problem with SquirrelMail was >> when our webmail service was under a brute force password attack and >> the /var/lib/ partition filled up with php session identifiers. >> Check your file system free space with df. > > Note that the Lockout plugin could probably have prevented that situation. strange: this morning, SM works, as i should. Lockout plugin will be installed as soon as possible. FYI: filesystems (special: /var/lib) are OK and was always OK (monitoring by nagios) SELinux is and was disabled. No bruteforce attack or something similar yesterday. login via telnet also failed. onesmore: no changes where done in SM. PHP sessions where maybe deleted by rebooting the hole server. many thanks Richard ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
