Logout " Error "

Warning: session_start() [function.session-start]: open(/tmp/sess_880e94e3ca2a8024425c148343cc3a39, O_RDWR) failed: Permission denied (13) in /home/msite/public_html/modules/boonex/facebook_connect/inc/facebook.php on line 49

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/msite/public_html/modules/boonex/facebook_connect/inc/facebook.php:49) in /home/msite/public_html/modules/boonex/facebook_connect/inc/facebook.php on line 49

Warning: Cannot modify header information - headers already sent by (output started at /home/msite/public_html/modules/boonex/facebook_connect/inc/facebook.php:49) in /home/msite/public_html/inc/profiles.inc.php on line 574

Warning: Cannot modify header information - headers already sent by (output started at /home/msite/public_html/modules/boonex/facebook_connect/inc/facebook.php:49) in /home/msite/public_html/inc/profiles.inc.php on line 575

Warning: Cannot modify header information - headers already sent by (output started at /home/msite/public_html/modules/boonex/facebook_connect/inc/facebook.php:49) in /home/msite/public_html/inc/design.inc.php on line 116

Warning: Cannot modify header information - headers already sent by (output started at /home/msite/public_html/modules/boonex/facebook_connect/inc/facebook.php:49) in /home/msite/public_html/inc/design.inc.php on line 117

Warning: Cannot modify header information - headers already sent by (output started at /home/msite/public_html/modules/boonex/facebook_connect/inc/facebook.php:49) in /home/msite/public_html/inc/design.inc.php on line 118

Warning: Cannot modify header information - headers already sent by (output started at /home/msite/public_html/modules/boonex/facebook_connect/inc/facebook.php:49) in /home/msite/public_html/inc/design.inc.php on line 119

Warning: Cannot modify header information - headers already sent by (output started at /home/msite/public_html/modules/boonex/facebook_connect/inc/facebook.php:49) in /home/msite/public_html/inc/design.inc.php on line 101
Please Wait

Warning: Unknown: open(/tmp/sess_880e94e3ca2a8024425c148343cc3a39, O_RDWR) failed: Permission denied (13) in Unknown on line 0

Warning: Unknown: 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 too had this same issue - in which I just went and reinstalled the whole site (thank goodness the majority of my pages were in blocks so all i had to do was backup my database and restore it on new install). The only thing I can think of in my issue, and hoping this helps you resolve yours, is that I was creating a session, in a separate php page for the mobile app. In doing this, I got a session error that the save location could not be found, so i changed this in my php.ini file of my server. Now, Inormally do not logout as I am constantly on the site and always tweaking things,but I do have others test things, and I make them make sure that they are logged out, so I know at some point the logout worked.

But, if you look at the last line of your error statement, that will give you the base of your errors:

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0 - Iwould check the session.save.path in your php.ini and make sure that this location exists and is properly permissioned.

 and then the error above it next:

Warning: Unknown: open(/tmp/sess_880e94e3ca2a8024425c148343cc3a39, O_RDWR) failed: Permission denied (13) in Unknown on line 0 - again, goes with the above error of checking to make sure the path exists and that the permissions are set properly.

Another thing - and I could be totally wrong, but it is how it works on my server - for some reason. Ihave noticed that when I have errors, that the first error is always the last error, and the first error is actually the last one.So,Ialways look at the last error, and it is usually the one that I fix and all others go away. So, asareference, if you have errors like this again, check the very last one, and that should give you the reason for all of the other errors, or at least fixing that one should fix any other related errors.

I really hope this helps

EDIT: that the first error is always the last error, and the first error is actually the last one -actually means, that the first error the site runs across will be at the bottom of the list of errors, being the last one shown. and that the first error shown is actually the last error that the site ran across.