ID: 25876
Comment by: mbi at euro-ip dot net
Reported By: golden at riscom dot com
Status: Feedback
Bug Type: Session related
Operating System: freebsd 4.8
PHP Version: 4.3.3
New Comment:
I agree with mak123. We updated to PHP 4.3.10 on dec. 17, after the
news spread about the security issues in the serialize function.
Everything went without a problem, after about a week things started to
get itchy. Every now and then this damn error comes up. There has been
no notable change to the configuration of the affected machines in the
meantime.
At first, everything looked allright again, but after about an hour the
same damn error returned on all sites using file based sessions.
Looking at the changelog of 4.3.10 the following line comes to mind:
- Crash when using unknown/unsupported session.save_handler and/or
session.serialize_handler.
So, instead of figuring out what all the code in session.c is supposed
to do, I replaced this one with a 4.3.9 version and recompiled the
4.3.10 package.
This is running now for about 20 minutes on a heavily loaded machine,
until now, no problems (knock on wood).
If this fixes the problem, it seems clear to me that the alterations of
session.c caused it.
I will keep you informed.
Previous Comments:
------------------------------------------------------------------------
[2004-12-27 16:47:04] mak123 at poczta dot onet dot pl
strange - I face this problem about week after upgrading to php.4.3.10
(apache 1.3.33, rh.es.3). first few days without any error ...
meanwhile no updates, tripwire shows no changes in any system files...
------------------------------------------------------------------------
[2004-12-27 16:39:49] onno at triptic dot nl
Didn't look at this thread well enough the first time
also:
ini_set('session.save_handler', 'files');
seemed to have solved all of my problems.
it's still a major bug though.
thanks
------------------------------------------------------------------------
[2004-12-27 16:09:31] onno at triptic dot nl
I should probably mention that more sites use this machine, and I don't
know in which way they are using sessions that might give conflicts or
something.
------------------------------------------------------------------------
[2004-12-27 16:03:04] onno at triptic dot nl
Yeah I know, error didn't appear for more than half an hout, not so
long ago. I quitely hoped it wasn't there anymore until it popped up
again. I assure you it has produced the following error several times:
Fatal error: session_start(): Failed to initialize storage module: user
(path: /tmp) in /usr/www/users/jtag/test.php on line 2
It usually happens a lot of times in a row and in the complete website
as well, so I guess it's a server-state which triggers it. Probably
when more users browse the site, unfortenately I can't tell you when
this happens.
------------------------------------------------------------------------
[2004-12-27 15:51:21] [EMAIL PROTECTED]
Tried many times: no errors/warnings etc.
Works just fine.
------------------------------------------------------------------------
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
