Hey there all. I'm running Squirrelmail 1.4.22 under php5.3 under freeBSD. After I log in, some of my users are getting blank pages. I don't believe it's a PHP error -- everything is configured fine and works for most users. All squirrelmail configtests seem to indicate everything's hunky dory. While I think I've solved my problem at the moment, I wanted to document it here. The behavior is thus: Apache/2.2.22 (FreeBSD) PHP/5.3.13 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/0.9.8q IMAP is uw, uw-imapproxxy, and dovecot. 1) User is able to log in, ie they get a login form and are able to submit it. Someone tailing the mail server logs will see an imap login. 2) Dovecot loads a folder, and ostensibly sends it along to squirrelmail. TCPdump confirms this. 3) Squirrelmail never displays it -- and in fact never even closes the connection to the imap server. Browser continues to spin. 4) Any future access attempt seems to pick up the same session and hangs in a similar manner. You can't even bring up the login page again from that browser, unless you restart apache. So, here's what I discovered/tried in trying to solve this problem: * The problem went away for *some* users once I raised the memory limit, but the user I'm working with now about 300M in size. I've set php's memory limit WAY higher than that as a debug, but with no luck. * The debug plugin is not helpful -- it conflicted with multilogin. This is perhaps a bug. * I've tried moving user homedirs to different partitions (they're on NFS at the moment, just to rule out NFS overhead (although all other imap worked -- all other imaps)). * I've tried turning off the suhosin patch by setting suhosin.simulation = On in my php.ini, no help. * once apache was in this "stuck" state, I couldn't even load the squirrelmail config-test. (I could load a plain vanilla php phpinfo() page) * Finally, on a hunch, I disabled the "filters" plugin. Access came back to normal. I'm still not sure that this "solved the problem" but my user is happy, so I'm sticking with it. Questions: I recognize that there's not been a new release in a while, which is a shame, so the hope of fixing these items may be low, but I'll ask anyway: So, here's my big question -- why is this failure mode so obnoxious? If this problem is filters, why not send a redirect that says "still filtering, come back in a moment"? Or just output a status instead of a white, spinning page? Why not set a sane filtering timeout by default? Does filtering try to filter the *entire mailbox*, or just the N messages being displayed? If it's just the N messages, perhaps it should only filter those N, which means yeah, your main page may have <N (or even 0) messages on it. Why is debugger/multilogin broken? Why does a hit to login.php not expire the session? Why is there no logout.php -- just a page that does nothing but kill sessions and reset? Apologies for the rant, but I've poured about 12 hours of my time trying various debugs on this -- tweaking and even recompiling PHP, and I think there's got to be a better way. The fact that this is a "core" plugin, especially, would seem to imply it should be better behaved. -Dan -- --------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --------------------------- ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk ----- 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
