session warnings

leandra

Hi All,

I've got session problems. I've looked over my code a million times and I've got
<?
session_start();
?>
at the start of every page, with no spaces or blank linkes, these are the warnings I get:

Warning: session_start(): read returned less bytes than requested in /var/www/specgen/news.php on line 2

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /var/www/specgen/news.php:2) in /var/www/specgen/news.php on line 2

Warning session_start(): Cannot send session cache limiter - headers already sent (output started at /var/www/specgen/news.php:2) in /var/www/specgen/news.php on line 2

I don't get why the line of code that's opening the session is complaining about the session already being open!

Any hints?

leandra

also, i should note that news.php works okay when included by my login script...
(users of my system are taken to the news page after loging in) but not when I try and go to news.php after being logged in. All my other pages behave the same way too all of a sudden, (after they working fine for several months)

Is there something in php.ini that I should look out for?

leandra

I've narrowed it down to the the fact that i had session.save_path, and it wasn't helping and that possibly session.auto_start=1 might not have been helping. how i have the same session id coming on consecutive pages, but my $_SESSION array seems to be being reset on every page.

Any ideas? Please? (My brain is slowing turning to fudge because of this problem)

Leandra

leandra

Now it seems as though my

$_SESSION['blah']="blah blah";

lines are causeing the errors... and "the client did not send the appropriate cookie. SID" according to http://aspn.activestate.com/ASPN/docs/PHP/ref.session.html

Any ideas? Clues? Please?

rpanning

Humm...sounds like you've got something going out already, like a space right before <? Just for fun try putting [man]ob_start/man just after session_start();

Weedpacket

Originally posted by rpanning
Humm...sounds like you've got something going out already, like a space right before <? Just for fun try putting [man]ob_start/man just after session_start();

I'm not so sure... I've never seen that first error message (the one with the bad grammar) before. What I am sure about is that the other error messages are being thrown because the first one was displayed. Something looks broken with the session-handling. What was changed on the system immediately before things went wonky? Did the permissions on the session directory change? (Like I said, I've never seen that message before, so I'm just guessing, here).

tsinka

Hi,

did you check if the partition where the sesion data gets stored is running out of space (or full already) ?
I'm not sure if you get that first error message in those cases but who knows ?

Which OS, PHP version ... do you use ?

leandra

Hey guys,

Thanks for your replies.

I managed to fix the problem, by reconfiguring php. It was something in my ini file after all. sigh of relief

The offending line seems to have been either:

short_open_tag
allow_call_time_pass_reference

safe_mode also came up in my diff results, but it probabley wasn't that right?

Oh well... alls well that ends well. Only wish I'd reconfigured php a lot eariler, instead of wasting 3ish days trying to work out what was wrong! ...Such is life. 😉

Thanks again,
Leandra

Weedpacket

Originally posted by leandra
safe_mode also came up in my diff results, but it probabley wasn't that right?

Personally, it sounds like the most likely option to me 🙂 - the writers of the session-handling code didn't anticipate permission problems writing session data? (Maybe, since the session-handling code has to work with session storage mechanisms other than just "files in a temp directory", the error message has to be a bit more generic.)