ladykaren Posted August 5, 2010 Posted August 5, 2010 Hi all; I have a problem I hope someone can help with. Last night I created a new Category in my Admin section. Well I changed my mind about how I was going to set up the new Category and decided to delete it. Click Delete. Are you sure you want to delete? Yes. Then I received this : Warning: session_write_close() [function.session-write-close]: write failed: No space left on device (28) in /home/content/l/a/d/ladykdelights/html/catalog/includes/functions/sessions.php on line 136 Warning: session_write_close() [function.session-write-close]: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in /home/content/l/a/d/ladykdelights/html/catalog/includes/functions/sessions.php on line 136 And guess what? My entire database was dumped. Images and all. So I've spent the day doing restores on both the database and all 9000 + images. The Warning also now appears at the bottom of my website ladykbridalplus.com Can anyone help? Now I'm terrified to try and delete anything from Admin Thanks in advance :)
chadcloman Posted August 5, 2010 Posted August 5, 2010 In your catalog/includes/configure.php file, what value do you have for the STORE_SESSIONS define? Check out Chad's News.
ladykaren Posted August 5, 2010 Author Posted August 5, 2010 Hi Chad; I have this : define('STORE_SESSIONS', ''); // leave empty '' for default handler or set to 'mysql'
chadcloman Posted August 5, 2010 Posted August 5, 2010 Change it to "mysql" and your problem will most likely go away: define('STORE_SESSIONS', 'mysql'); Make the change in these two files: catalog/include/configure.php catalog/admin/include/configure.php Note that it's most likely that your store is incapable of processing orders (or even the shopping cart) until this is fixed. And if you're on a shared hosting system, you may want to notify your hosting company that there are disk space problems with "/tmp" and that your PHP code can't save session information. . Check out Chad's News.
ladykaren Posted August 5, 2010 Author Posted August 5, 2010 Hi Chad; Thanks for your help. I'll change those files. I have GoDaddy for hosting. What exactly should I tell them is the problem? Thanks so much again :)
chadcloman Posted August 5, 2010 Posted August 5, 2010 Thanks for your help. I'll change those files. I have GoDaddy for hosting. What exactly should I tell them is the problem? I suggest you tell them that your PHP program was trying to save the session data to /tmp and you got a "disk full" message. And provide the error messages that you had in your original post. I also suggest letting them know that you've solved the problem by saving the session data to the MySQL database. They may well respond and say that you shouldn't be using /tmp anyway... Check out Chad's News.
ladykaren Posted August 6, 2010 Author Posted August 6, 2010 Hi Chad; Thank you so much for your help. I contacted GoDaddy and they responded with "Sending the problem to a higher tech person". I'm still waiting to hear back. I changed the define to mysql the other night and I ran a dumby order today, and good news, the cart is working. Now for a really dumb question. Forgive me but this is pretty much a non-knowledge area for me when it comes to the database. LOL Is there a way to tell if the database is saving to the /tmp place? I'm not even sure where that is :blush:
chadcloman Posted August 6, 2010 Posted August 6, 2010 Is there a way to tell if the database is saving to the /tmp place? I'm not even sure where that is Hi Karen, By changing the configuration, the session data is stored in the database -instead- of /tmp. The default method to store session data is to put it somewhere on the server's hard disk, and /tmp is a directory name. By specifying 'mysql', you are telling osCommerce to store the session data in the MySQL database instead of on the hard drive. That's why the problem went away when you made the change. . Check out Chad's News.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.