ID: 19022
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Session related
Operating System: linux (rh7.3), apache 1.3.26
PHP Version: 4.2.2
New Comment:
I have a basic installation of OpenBSD 3.2, Qmail 1.03, Courier-IMAP
1.6.2, Apache 1.3.26, PHP 4.2.3. I have configured PHP and all seems
run. But, when I installed SquirrelMail 1.2.10 for webmail service, I
received the same error
Warning: open(/tmp/sess_7538b7739bdd44e2fb0e747f65af858d, O_RDWR)
failed: No such file or directory (2) in /htdocs/webmail/src/global.php
on line 134
and then
Warning: Failed to write session data (files). Please verify that the
current setting of session.save_path is correct (/tmp) in Unknown on
line 0
I think it is your same problem. I have also tried to write a simple
php file with only the row
<? session_open(); ?>
It returns the usual error! I hope there will be a solution as soon as
possible, I'm very sad to see all run but I can't install my Squirrel
WebMail...
Previous Comments:
------------------------------------------------------------------------
[2003-01-27 08:15:51] [EMAIL PROTECTED]
my apache is running as "nobody,nogroup" with an assigned homedir of
"/" or "/tmp" or "/dev/null" or "/var".
the error still spams my logfiles, but alot less cause i have migrated
over to java/jsp. seems like the only way to fix this is to redruce
traffic.
------------------------------------------------------------------------
[2003-01-24 23:12:17] [EMAIL PROTECTED]
ALL READ THIS PLEASE !!! SOLUTION TO
Failed to write session data
(files). Please verify that the current setting of session.save_path
is
correct (/tmp) in Unknown on line 0
In this case an many other, working with Linux or FreeBSD, remember
that applications are users too. I am not an expert on this OS, but I
know something. When a user does not have a home directory, he can not
do a lot of things, among them is to execute many commands (why? do not
ask) you may check, create a user with no home dir and test. So that is
the problem with mysql and www, (PHP is working as www because apache),
SO, assign a home dir to www and you will see the error no more. The
same may happen with some mysql change settings. Thanks.
------------------------------------------------------------------------
[2003-01-23 14:28:50] [EMAIL PROTECTED]
Hello, had the same error on a low-traffice development server (one
processor) with pretty standart php (4.2.3) + apache (1.3.26) set-up. I
noticed that I forgot the SID on one page and that somehow messed up
the session and created the error on all pages that tried to access
this same session. After I put the missing SID in, everything worked
fine...
------------------------------------------------------------------------
[2002-12-12 18:25:45] [EMAIL PROTECTED]
You can work around this bug by changing the session saver to "mm"
(without the quotes).
There are no known solutions to this problem that I can see out there.
The only people with solutions are the windows people who didn't change
the php.ini file to have a windows path in it. FOr the Linux people,
this may well be a library compatibility problem, which is the best
guess so far but is probably wrong!
------------------------------------------------------------------------
[2002-12-07 20:32:26] [EMAIL PROTECTED]
Okay, I think I solved this bug for me at least.
I would receive this error:
Failed to write session data (files). Please verify that the current
setting of session.save_path is correct (c:\windows\temp) in Unknown on
line 0
and I finally tracked it down to being I was sometimes setting the
session_id(""); to blank, aka, to nothing. That would cause it to fail.
I still think this is a bug, because you shouldn't be able to break it
by setting it to nothing.
The reason I was unable to track this down quicker was because I had no
idea I was passing a blank variable to the session_id. So I looked into
that, and it turns out PHP fails to delete cookies.
I think their is a bug with the delete cookie functions...you might
want to check into that. To solve this, instead of deleting the
cookies, I just set them to -1, and then checked if they were -1, and
if so, treated them as if they weren't there.
I hope this helps,
Nate
------------------------------------------------------------------------
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/19022
--
Edit this bug report at http://bugs.php.net/?id=19022&edit=1
