ID: 32330
Comment by: colossuswv at hotmail dot com
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Session related
Operating System: *
PHP Version: 6CVS, 5CVS, 4CVS (2005-03-17)
New Comment:
The ini_set workaround doesn't seem to work when using a db to store
sessions. Using session_set_save_handler() again after session destroy
does work however, albeit an undesirable solution.
Previous Comments:
------------------------------------------------------------------------
[2006-12-14 17:24:03] faithfulsoft at tiscali dot it
I've experienced this problem today, and it was driving me crazy.
I was able to resolve it thanks to the last post on this page.
I've put this two lines of code
ini_set("session.save_handler", "files");
session_start();
in a separate file, and I include them where I need.
The strange thing is that I borrowed the piece of code I am using from
a GPL portal system, which is working like a charm on my local server
with this line
ini_set('session.save_handler', 'files');
This is really strange.
Anyhow, thank you all guys.
------------------------------------------------------------------------
[2006-06-07 04:26:18] sean at oteams dot com
I struggled for several days with the "Failed to initialize storage
module: user" problem. I read everything I could find on php.net and
in this bug database. Finally, what solved the problem for me was
this:
Whenever I made a call in my code to session_start(), I used an include
statement to include the following from an include file:
<?php
ini_set("session.save_handler", "files");
session_start();
?>
And that did it.
------------------------------------------------------------------------
[2006-01-16 16:41:52] ajithts at gmail dot com
Hi folks,
I have also had the same problem. My /tmp was not a separate partition
and it had full permissions.
I have then changed session.save_handler to "files" in php.ini.
Initially it was "user". Everything worked perfectly after I have
restarted httpd saving the changes.
Thanks and regards,
Ajith
------------------------------------------------------------------------
[2005-06-04 00:25:54] [EMAIL PROTECTED]
PS(mod_data) gets set to NULL with these:
session_write_close(),
session_module_name('foo'),
session_destroy()
------------------------------------------------------------------------
[2005-05-21 19:19:42] [EMAIL PROTECTED]
I think you are on the right track mfischer. It looks like PS(mod) and
PS(mod_data) can get out of synch which would cause this. And I think
all the others with seemingly unrelated issues are actually related.
If PS(mod_data) leaks out of the per-request sandbox and infects
subsequent requests all it takes is one application on a server to use
its own session handler and it could affect other seemingly trivial
standalone session apps on that server.
------------------------------------------------------------------------
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
