#19022 [Fbk]: PHP Warning: Failed to write session data (files)

From: Date: Wed, 04 Sep 2002 05:29:59 +0000
Subject: #19022 [Fbk]: PHP Warning: Failed to write session data (files)
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-18384@lists.php.net to get a copy of this message
 ID:               19022
 Updated by:       rasmus@php.net
 Reported By:      phpbugs@mx4k.com
 Status:           Feedback
 Bug Type:         Session related
 Operating System: linux (rh7.3), apache 1.3.26
 PHP Version:      4.2.2
 New Comment:

Your production server wouldn't happen to have multiple cpus?


Previous Comments:
------------------------------------------------------------------------

[2002-09-04 00:06:04] rossr@reactive.com

Hi there,

We didn't run into this problem until the site that we were working on
went live and we have been unable to replicate the problem on our dev
server in our office. 

So I'm guessing that the bug only appears on a loaded system.

Cheers, Ross

------------------------------------------------------------------------

[2002-09-03 23:46:17] kalowsky@php.net

Unfortunately I cannot reproduce this locally here, and looking the
code I don't see anything particularly/glaringly wrong.

The piece of code in question (I believe) is the
php_session_save_state() function, most specifically the PS(mod)->write
pieces of code.  

Does this happen on a non-loaded system as well?  Would any of you be
willing to apply some patches to see if things do and do not work?

------------------------------------------------------------------------

[2002-09-03 23:35:55] ShaneO@alldigitalservices.com.au

Further to this I have since discovered that the server generated
PHPSESSID=713540145172t2t0 addon to links genereated on these pages
where the Warning occurs are generated as follows...

https://www.aussiepharmacy.com.au/index3.php?pid=46&cart_action=Add&PHPSESSID=<?php
session_id(); ?>

which is not much use either.

------------------------------------------------------------------------

[2002-09-03 23:08:25] ShaneO@alldigitalservices.com.au

Rather than have it in the log file which it probably registers in as
well, I have the message displaying on my ecommerce site just after the
session crashes into oblivion losing all cart items and user log-in
data.

This is EXTREMELY URGENT as My clients are pissed at me.

How the hell do i workround this ????
What the hells causing it???

I suspect that it has something to do with the level of depth that is
utilised in a require_once stack... eg if a require once calls a page
that issues a require once or include which calls a page that issues
another require once... etc...  At some point the server gets lost as
to where the session cache is being written to and goes belly up

------------------------------------------------------------------------

[2002-08-27 06:08:13] phpbugs@mx4k.com

hi,

the problem returned. it doesnt seem to be affected by
register_shutdown_function. the day i thought the problem was gone was
related to a problem at our ISP (which caused very low traffic (5k
instead of 70k users))

maybe its just a problem under high load or something like that. im
back at the old problem (tried apache+php rpm (with dso), same
problem).

------------------------------------------------------------------------

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



Thread (75 messages)

« previous php.bugs (#18384) next »