#25876 [Com]: session_start(): Failed to initialize storage module
ID: 25876 Comment by: mitch at webcob dot com Reported By: golden at riscom dot com Status: Bogus Bug Type: Session related Operating System: freebsd 4.8 PHP Version: 4.3.3 New Comment: I'm also running FreeBSD 4.8 - same problem. My /tmp is on a separate partition, and has plenty of space... a restart (even a graceful one) seems to fix the problem. As a temp fix, I heard someone say that the sites they had using custom session storage handlers did NOT exhibit the problem, so I think I may try an auto-prepend file containing such an override on a server-wide basis. Any comment on this idea? Please copy my email. Thanks. Previous Comments: [2004-02-18 11:18:59] bigrob at cox-internet dot com I'm having the same problems. FreeBSD 4.8, php 4.3.4. THIS IS GETTING VERY annoying. It quit doing it for a month, then almost to the exact day it just started up again this morning at 1AM and hasn't stoppd. Apache 2.0.47 as well. Restarting apache seems to do the trick for about a minute, then it starts popping up again. I've already had 20 customers call this morning saying they cannot place orders and they give me the error. I've check my apache access logs as well as the php log. I get this error several times: [18-Feb-2004 10:15:39] PHP Warning: Unknown(): A session is active. You cannot change the session module's ini settings at this time. in Unknown on line 0 Almost always following it is this srror: [18-Feb-2004 10:15:51] PHP Fatal error: session_start(): Failed to initialize storage module. in /mydir/myfile.php3 on line 2 All that is in myfile.php3 is session_start(); These errors started happening after moving to a new sever. NO PROBLEMS in the past, was using Apache 1.3.8 I believe and PHP 4.3.0. PHP People, WHAT ARE CAUSING THESE ERRORS [2004-02-18 07:35:32] c dot i dot morris at durham dot ac dot uk We're also getting this bug. Apache 1.3.27 PHP 4.3.2 Solaris 8 (rather than BSD) as the OS It happens intermittently, reloading the page _usually_ clears it. Different users report different things. I've never been able to duplicate it on my browsers (tested IE and Mozilla, no difference), a colleague gets it occasionally, users reporting the problem to us get it one time in three in the worst cases. /tmp is writeable and has a huge amount of free space. Multiple users have reported the problem to us, the minimal code sample already reported is the only common part. We are attempting to find if there is anything special about the requests that trigger it, but so far nothing - will update if we find anything. [2004-02-10 16:45:59] bernoico at netcabo dot pt A have this problem to, is very annoying... I made a search in google for "Fatal error: session_start(): Failed to initialize storage module" and I found millions of sites in this condition... Are there any work around? Thanks. [2004-02-07 22:58:14] [EMAIL PROTECTED] close [2004-02-05 04:08:22] golden at riscom dot com Open The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/25876 -- Edit this bug report at http://bugs.php.net/?id=25876&edit=1
#25876 [Com]: session_start(): Failed to initialize storage module
ID: 25876 Comment by: mitch at webcob dot com Reported By: golden at riscom dot com Status: Closed Bug Type: Session related Operating System: freebsd 4.8 PHP Version: 4.3.3 New Comment: Having this problem again too. I WAS having this problem with FreeBSD 4.4 / Apache 1.3.27 / PHP 4.3.2. The problem started happening again a couple days ago... Seems to be a Heisenbug - ever time I add code to output debug info and restart apache, the problem seems to have disappeared or moved to a different website / vhost. Problem does not seem to happen on all vhosts at the same time... Just upgraded to PHP 4.3.7 The problem still persists. I have done all the recommended "fixes" - checking disk space, permissions, changing storage location, etc. Am currently working on a db based storage moduel to include on all sites experiencing the problem as in interrum fix. Please CC me on any updates. thanks. Previous Comments: [2004-06-17 10:18:10] searchadm at goschorn dot de PHP Fatal error: session_start(): Failed to initialize storage module: user (path: /tmp) in ... PHP 4.3.7 (4.3.4 also) Apache 2.0.48 Suse Linux 8.2 after apachectl restart it works again for a while [2004-06-15 15:05:39] datacompboy at mail dot ru Currently runned workaround via auto_prepend_file = /etc/httpd/phpinc.php and in /etc/httpd/phpinc.php [2004-06-15 14:47:13] datacompboy at mail dot ru I have running Apache SERVER_SOFTWARE Apache/1.3.20 Sun Cobalt (Unix) mod_jk mod_ssl/2.8.4 OpenSSL/0.9.7d PHP/4.3.7 mod_auth_pam_external/0.1 FrontPage/5.0.2.2510 mod_perl/1.26 Small code to see: Producing session.save_handler files files and below: Fatal error: session_start(): Failed to initialize storage module: user (path: /tmp) in a.php on line 3 Can't say what to do to fix that _STRANGE_ error :/ [2004-06-14 01:43:26] sha3134 at njit dot edu I was having this problem intially with php-4.3.2 with squieralmail. After an upgrade of both SQ and PHP-4.3.7, the problem persists, though more random. Hitting refresh usually clears this error. As i discovered though the error happens with pages using start_session and session.save_path permissions for files are correct and i have tried clearing it out. I have not tried the: ini_set('session.save_handler', 'files'); as i its already defined in my php.ini file. Note this is a very random bug/feature. Could this be due to high load or high io on the server ? [2004-05-27 09:23:21] yertletheturtle82 at yahoo dot com I am running version 4.3.6 and receive this error consistently when attempting to run phprojekt. It was running with no problems previously. I am also running Drupal which uses php also, but seems to have no problems at all. Not sure why this started happening all of a sudden. Running RH9.0. It seemed to start when I was trying to re-compile PHP with IMAP support. Thanks The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/25876 -- Edit this bug report at http://bugs.php.net/?id=25876&edit=1