1&1 Internet: Disk quota exceeded (122) error on MYSQL Database apps
I just started receiving the the following errors on all my websites hosted on 1&1 internet that have MYSQL databases.
Warning: session_start() [function.session-start]: open(/tmp/sess_x, O_RDWR) failed: Disk quota exceeded (122) in /path/page.php on line 20
The result is that no session is created, so things that require a session don’t work too well.
Since I am nowhere near my allocated storage capacity, I’m not sure why this is occuring, and feel pretty confident that 1&1 support won’t tell me, even if they know. The support people that I’ve talked to so far don’t even have root access to the server, so I hope they fix it sometime soon. The temporary workaround is just to point the session.save_path somewhere else.
Luckily I use 1&1 for development only, as they are not reliable enough to host client websites, so no customers are effected.
Just letting you know, 1&1 database servers kicked the proverbial bucket today at 1.03pm GMT.
It’s not a one off as the three different servers I using are all (bless them) RIP.
Just an update for you all, and it’s amazing at how apologetic front line tech support can be.
This is over a year after the original post, but a friend of mine had the same issue yesterday and also uses 1&1 for hosting.
This issue was caused by his site being on a shared server and the server’s global php session folder was set to “/tmp”, which he did not have access to. His access started in a client folder like “/homepages//htdocs”. So his app didn’t have permissions to the global session folder and was reporting a lack of disk space because it couldn’t write files there.
The fix was one line of code that changed the php session folder to somewhere within his reach in the file system, given his file permissions:
ini_set(“session.save_path”, “/homepages//tmp”);
This needs to be placed in the php code at a point before any sessions are being created. Change the above path to match your path on the server and create a tmp folder there to serve as the new location for sessions. Make sure the file permissions allow php full read/write/modify/delete access to the new location. That immediately fixed our problem.
it still helped me a year later! tnx!!
Thanks for visiting. Glad I could help!