ID: 25876
Comment by: dan at nitro dot com
Reported By: golden at riscom dot com
Status: No Feedback
Bug Type: Session related
Operating System: freebsd 4.8
PHP Version: 4.3.9-4.3.10
Assigned To: sniper
New Comment:
I was experiencing this problem on my server, and have managed to make
it go away after reading comments in this post and experimenting a bit.
details:
original setup:
/var/lib/php/session
owner root:apache
permissions: 770
test script from gul_murjani at yahoo dot com would fail after between
1 and 30 or so counts
modified permissions on directory to:
owner apache:apache
permissions 700
test script ran on five client computers to over 10,000 cycles without
failing.
this fix is strange though as I have since changed the permissions back
to the origial setup:
owner root:apache
permissions: 770
and the script has run without failing - no more errors - even after
another thousands of cycles.
strange but true!
Previous Comments:
------------------------------------------------------------------------
[2005-09-08 01:42:04] info at ruudgoedhart dot nl
I'm experiencing the same problem, strange enough NOTHING i tried so
far has solved it. I tried:
Recompiling PHP
Downgrading PHP
Reinstalling Zend
Upgrading Zend
At a certain moment a harddrive of the server with this error went bad,
and i had to do a complete reinstall on a different drive.. Strange
enough.. the SAME error occured, while I have different servers with
identical hardware and settings which run just fine.. without errors.
Is it possible this error has somehow got anything to do with hardware?
bad memory or something? I simply find it too strange that i'm only
experiencing this error on 1 of the 8 machines, and that even a
COMPLETE re-install didn't work.
I'm using FC3 with Cpanel
PHP 4.4.0 with Zend Optimizer 2.5.10a
------------------------------------------------------------------------
[2005-08-26 07:11:32] smbukas at gmail dot com
I have this problem too and adding the the code with setting
"session.save_handler", "session.save_path", "session.use_cookies" does
not solve this problem.
I use PHP Version 4.4.0
------------------------------------------------------------------------
[2005-08-18 10:15:44] frank dot altpeter at gmail dot com
Used the workaround mentioned two comments below, but experiencing
still the same sporadic errors.
Any further hints are very appreciated.
------------------------------------------------------------------------
[2005-08-15 11:04:30] frank dot altpeter at gmail dot com
I experience the same (sporadic) errors on my FreeBSD 4.11-RELEASE-p11
using php4-4.4.0 and apache-1.3.33.
The mentioned workaround (putting ini_set in an auto_prepend_file) is
now in place and to be tested.
Additionally, i would be glad if the PHP crew would do something about
this - it's really a shame to see that this bug still happens with
4.4.0.
------------------------------------------------------------------------
[2005-06-27 10:37:51] ftownes at w3-hosting dot net
On our ES 3 machines, we worked around this bug by pre-pending and
appending the following code to all scripts executed (via the php.ini)
file:
[EMAIL PROTECTED] root]# cat /tmp/auto_append_file.php
<?php
if (ini_get("session.save_handler") == "user") {
@ini_set("session.save_handler","files");
@ini_set("session.save_path","/tmp");
@ini_set("session.use_cookies","1");
}
?>
Since the error is never exhibited on a freshly spawned instance of
apache, reducing the number of requests handled by apache (in Worker
MPM mode) made sure that new children were spawned before old age
increased probability of the bug; this seemed to be vital to make a 99%
effective solution.
[EMAIL PROTECTED] root]# httpd -l
Compiled in modules:
core.c
prefork.c
http_core.c
mod_so.c
On our machine we also noticed that after testing this for workaround
for 3 weeks we haven't used any swap on the machine as opposed to
~100MB previously, another desireable side effect.
------------------------------------------------------------------------
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
