I am running a very popular service... on free.fr (ya, that was smart) and am now starting to get this error below.

Warning: Unknown(): write failed: No space left on device (28) 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 (/var/www/free.fr/1/c/customsigs/sessions) in Unknown on line 0

Happens every now and again, but especially when I am writing config files, even though the error is to do with sessions...

The session data that I am storing is username and password, not even a kilobyte. (times that by 1000 and you still have very small amount of space used by the sessions)

A bit of info about the space used on the server, 7 meg out of 1 gigabyte (does that sound full to you? I'm not an expert, but I'd say that 7mb < 1gb haha)

Anyone got any ideas.

People are getting pissed off at me. Isn't that fun.

    The "session.save_path" php.ini file setting shows where the sessions are saved. This is usually at something like "/tmp". This directory is usually shared for ALL subscribers of the web host provider (for at least that particular server). So, you might not be saving a lot of info, but the combined subscriber population is and that's enough to make it full.

    Notify the web host provider that they are running out of disk space on that server!

    .

      Its actually individual for each of the users on this host, because we had to create a folder called sessions to get sessions to work.

        Unless you're code is in a loop or just writing a lot of data unintentionally, I'd say it still is the problem with the web host provider.

        On a shared host you can get this problem. It doesn't matter that the session directory is particular to you. The fact is that other subscribers get to save data to that same disk (for their stuff), and they're causing your script to bomb out. That's also why it's intermittent, it depends what others are doing at the same time you are. The 1GB is just a number to show the max you can use, but doesn't necessarily mean that is available on disk now!

        I would certainly bring up this problem to your web host provider if you haven't already done so.

          I think he has already contacted them...

          Anyhoo, I have actually been working with webservers the past week anyway, so I know how it all works. This sucks tho...

            Write a Reply...