>Here's the only error i see that could be generated by >the timeout errors. >[27-Aug-2003 19:11:35] PHP Fatal error: Maximum >execution time of 30 seconds exceeded in Unknown on >line 0 >just so you know mod_gzip and php-accelerator is >disabled. i restarted apache as well to make sure.
You might have to play with the logreporting stuff in the ini file to get more verbose messages. Let's regroup. We know some event occurs that causes apache to segfault and this is causing your browser to show the timeout message. This can be difficult to solve. And I have had this happen either after I hacked some PHP code after a long night overdosed on caffeine or after updating to some CVS code that isnt quite stable yet. You could probably post your SM config file(s) to me, or just shotgun SM as discussed below: Dont know if this is production server or not. If it is then you'll have to put your SM into a different tree. At anyrate, verify it is not some plugin causing it. Remove All plugin's, Or better yet, Install SM into a different tree. I assume this is not a production server. If it is then change the steps as necessary: Backup your current SM tree (mv squirrelmail squirrelmail.old) Backup any mysql databases and tables with mysqldump If you are positive the DB schemea is ok then just truncate the tables, else drop the whole DB , recreate it and the tables. Unmerge the SM ebuild and dont use it again. I seem to remember having some kind of difficulty with it, but its been a while and I've not looked at the SM ebuild in a while. Snag the 1.4.1 tarball from the SM site. Install it into /home/httpd/htdocs/squirrelmail Configure it. Please do not use anything from the old setup. Do _NOT_ install any plugins that are not already installed by default. Setup your mysql tables, dababases etc. Setup your DSN's in the SM config Then Chown -R apache:apache the entire squirrelmail tree when done Keep the default install simple. No esoteric plugins or other weirdness. The objective is to establish a stable base that is known to work without causing the segfault in Apache. Once you have an established working base, Anytime you do even something trivial, note it in your changelog. You _do_ keep a change log when you change something on your system right? Creating and maintaining a changelog will save your ass! You might make a change and not notice there is a problem until a week later. Then you'll be stuck out trying to figure out what happened. I use a simple mysql database and some php for this. Use vi, emacs, joe or whatever to document any changes you make to the system or to any software running on it. If the setup still segfaults Apache and you are positive you didnt make a configuration error, then we will have to pay more attention to your PHP and Apache setup, though I bet it's some plugin or some misconfig in SM causing your problem. Sometimes it's just easier to shotgun the problem and move on down the road than to waste time trying to figure out why. You can always figure out the why once you get things working and your users off your tail end. Good luck and keep me informed Ron ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
