Hey,
I've had this issue since Last November now, and still has not been resolved. Occasionally, usually when the site gets alot of hits, a very minor number of users after being on the site for some time, surf back to this error:
Warning: session_start() [function.session-start]: open(/tmp/sess_f444de1eb721ec338c86f7903f10df8c, O_RDWR) failed: Permission denied (13) in /home/ccc/public_html/index.php on line 5
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/ccc/public_html/index.php:5) in /home/ccc/public_html/index.php on line 5
I own the server, based on Cpanel that uses /tmp/ for session storing, and have never faced these problems else where. The system admins who keep looking into the issue keep dismissing it because they don't see it (typical) and when it repairs itself, usually when the user opens and closes their browser or clears cookies (Obviously resetting the session ID so it doesn't use the same one) it works.
Now they have tried everything, and now have decided to blame my "poor scripting" which I am really peeved off at as I use the same script else where and never get these issues. They are saying all sessions I create should be closed when finnished! The only way we can do this surely is if we expect users to actually click "Log out" surely? 
Also, I do alot of session management and updates in the database and simply use the session ID to link users to them, so it shouldn't be storing too much info in these sessions! I do have a cron job automatically deleting sessions from the DB if they are so many minutes old with no activity, but its programmed to re-insert the session to the DB from scratch if they return, it seems the PHP side of things is somehow resetting permissions on the session data in tmp after so long! I can't even detect when the error comes up as session_start() always appears to return 1 even on error.
They've chmod'd tmp to all sorts, added stickys to it, played with settings, and still nothing. I am adament its a server issue, but they are adament its a scripting issue so would be nice if anyone else has had experiances with the error above?
I've tried searching it on google and on this site, and most people don't face the issue exactly the same except for a recent bug announced on php.net and curious if it is actually a bug, others must have made a temporary work around?
http://bugs.php.net/bug.php?id=43990&edit=1
Thanks in advance everyone!
James
The owner of the largest thread on here.. word association thread 