SESSION_WRITE_DIRECTORY error...

I have a live site, that suddenl crashed. Nothing was done on it. The following is on the main page, any clue? You can see it at www.OnlineShop.com.sg

Warning: session_start() [function.session-start]: open(SESSION_WRITE_DIRECTORY/sess_3bb0b89cddbb864724e1879c38df16b4, O_RDWR) failed: No such file or directory (2) in /home/onlinesh/public_html/includes/functions/sessions.php on line 102

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/onlinesh/public_html/includes/functions/sessions.php:102) in /home/onlinesh/public_html/includes/functions/sessions.php on line 102

Warning: Cannot modify header information - headers already sent by (output started at /home/onlinesh/public_html/includes/functions/sessions.php:102) in /home/onlinesh/public_html/includes/init_includes/init_templates.php on line 78

http://www.onlineshop.com.sg/include...ns/warning.gif Warning: The sessions directory does not exist: SESSION_WRITE_DIRECTORY. Sessions will not work until this directory is created.


Warning: Unknown(): open(SESSION_WRITE_DIRECTORY/sess_3bb0b89cddbb864724e1879c38df16b4, O_RDWR) failed: No such file or directory (2) 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 (SESSION_WRITE_DIRECTORY) in Unknown on line 0

Sounds like you are missing a configuration_key in your configuration table ...

Peek in the Configuration ... Sessions ...

Do you see a setting for:

Quote:

---

Session Directory
If sessions are file based, store them in this directory.

---

same problem for me but it's not clear how to fix it...

Can you go to phpMyAdmin and search the configuration table for the configuration_key called:
SESSION_WRITE_DIRECTORY

in the configuration table there isn't any configuration_key called: SESSION_WRITE_DIRECTORY in fact phpmyadmin after the query:

UPDATE configuration SET configuration_value = '/accounts/bla/bla/bla/cache' WHERE configuration_key = 'SESSION_WRITE_DIRECTORY'

returns:

Rows modified: 0

Add this via phpMyAdmin:

Code:

---

INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added) VALUES ('Session Directory', 'SESSION_WRITE_DIRECTORY', '/tmp', 'If sessions are file based, store them in this directory.', '15', '1', now());

---

yes I fixed! :clap:

i get also:

Warning Your database appears to need patching to a higher level. See Admin->Tools->Server Information to review patch levels.

...but my version is 1.3.8b!
I just dropped all the tables and created all again but nothing changed...where have i to look at?

Where did you get your Zen Cart download?

Was this a clean install or an upgrade of an existing install?

It sounds like an upgrade that has not been completed ...

i've installed the italian version 1.3.8b following the wizard and I got immediately the SESSION_WRITE_DIRECTORY problem, I tried to fix it reinstalling and upgrading through wizard but something went wrong...

Zen Cart has not released a "v1.3.8b" version. The latest official release is "v1.3.8a". Maybe you need to contact whoever made your "italian version 1.3.8b" for personal support.

:shocking: at this point i'll follow the official release and patch manually the italian stuff..

yes, it seems the official version of ZC works perfectly! :yes:

Thanks for the update that the problems were with the italian version that you were using and that you have the current version of Zen Cart working ... :smile:

thanks for the great support! ;)

This is great to know as I just encountered this error when moving my store to a new server!

I've moved a few stores and I thought as long as I edit both config.php files that all should be well. I will have to double check the value in the config table of the DB now also during any future "moves". Since I learned something new, is there anything else I should watch out for? Specifically any other DB values/files that would need to be tweaked with the new full path, during a site move?

just got the same error on a customers website and it turned out the web host company was doing maintenance and it was not possible to write to the server creating the problem

once the maintenance was completed then the error disappeared