ID: 32330
Comment by: todd dot trann at palidar dot com
Reported By: [EMAIL PROTECTED]
Status: Assigned
Bug Type: Session related
Operating System: *
PHP Version: 4CVS, 5CVS (2005-03-17)
Assigned To: sniper
New Comment:
RedHat 9
PHP 4.3.9 from RPM (php-4.3.9-11.rh90.art)
Zend Engine 1.3.0, Optimizer 2.5.5
I am experiencing the same problem: the error indicates storage module
"user", yet php.ini has it set to "files", and nowhere in my code do I
change it to "user".
The problem comes and goes as the page is reloaded. A PHP page with no
session code does not exhibit the problem.
Todd
Previous Comments:
------------------------------------------------------------------------
[2005-03-24 22:27:36] scliburn at trtinfo dot com
mfischer,
I'm positive about the session.save_handler and the session_module_name
not being set anywhere.
I'm emailing direct my link to my php info page.
no sessions nothing on the page expect for phpinfo();
the save_handler is set to files. No joke.
another test i've done was to have a copy of a website running on 2
servers (same code, same db)
Server 1: Redhat php 4.3.9 Zend engine 1.3.0 - no problems
Server 2: php 4.3.10 Zend Zend engine 1.3.0 Optimizer 2+ - problems
------------------------------------------------------------------------
[2005-03-24 21:43:44] [EMAIL PROTECTED]
Do you use session_destroy in your code? Are you sure you aren't
calling session_module_name somewhere? Does a clean page, with no
session_start but only phpinfo in it, also tell you that the session
module in use is 'user' rather then files?
------------------------------------------------------------------------
[2005-03-24 18:43:34] scott at trtinfo dot com
scott => scliburn are one in the same :).
We have not been using any custom session handlers. We have been
utilizing the PHP built in session handlers. My session.save_handler
all have been set to "files".
I have noticed the error message still states:
Fatal error: session_start(): Failed to initialize storage module: user
(path: /tmp)
Take notice to the module "user", however this is my php.ini (i've
located and updated all instances of the php.ini);
session.save_handler = files
I was also unable to produce this error on another machine
(win2003-webedition) which has thread saftey on. Not sure if that is
helpful. This error has only produced itself after upgrading Zend 2+ on
php 4.3.9, 4.3.10, & 5.03 (I cannot produce this error on 5.02 with Zend
2+) yet.
I'm taking a wild non-technical quess in that the save_handler setting
is obviously getting reset during a php request, but have no clue as to
where. I know it's not the code calling to this. I wrote it. Zend?
Heres another twist. I do have another site that is running osCommerce
with custom session handlers and that site doesnot produce this error
(once again, yet). odly enough
------------------------------------------------------------------------
[2005-03-24 07:22:24] [EMAIL PROTECTED]
scott, scliburn: are you both using session_set_save_handler() ? Are
you operating in the same environment (custom save handlers are getting
lost after session_destroy) or are you just having the same error
message?
Most bugs I've seen refering to 'Failed to initialize...' are because
session module in php.ini is set to user instead of files when there
are no custom session handlers, which has nothing to do with this
issue.
------------------------------------------------------------------------
[2005-03-23 20:40:49] scliburn at trtinfo dot com
I would like to also add that I'm running and experiencing this issue
in both api versions CGI/ISAPI. not sure if that mattered
------------------------------------------------------------------------
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/32330
--
Edit this bug report at http://bugs.php.net/?id=32330&edit=1
