Question

No Space Left on Device and MySQL crashes

  • Posted January 15, 2015

I’ve had periodic problems with MySQL crashes. It happens periodically and I can’t figure out why. I’ll restart the service and it works fine for a few days.

Now there’s a more immediate problem

I was copying the logs and I started getting errors that said “No space left on device.”

Same error happens when I attempt to create a directory using FTP “No Space Left On Device.” So I tried to re-log in FTP and I get this bit of luck: Status: Connection established, waiting for welcome message… Response: 220 ProFTPD 1.3.4a Server (Zpanel FTP Server) [::ffff:162.243.211.145] Command: AUTH TLS Response: 500 AUTH not understood Command: AUTH SSL Response: 500 AUTH not understood Status: Insecure server, it does not support FTP over TLS. Command: USER thelemur Response: 331 Password required for xxxxxxxx Command: PASS ********** Error: Could not connect to server

I restarted the droplet. I can use SSH to connect, but I still get the same No Space errors and ftp problems.

And now my sites look like SQL has crashed again. When I try to restart the service, I get “Job failed to start.”

If it matters, my droplet is Ubuntu 12.04, i’m using Apache and zpanel.

Anyone know what’s going on?

Subscribe
Share

Same problem :( have you find a solution?


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

do this:

du -hs /*

it will tell you which directories on / are using your space, if by example you get something like “50G /var” then do #du -hs /var/* and check what inside of /var is using your space, and gain and again till you find it.

If you are using MySQL InnoDB maybe is your binary logs that are fulling your HD as it creates a new one each time it crash, but also can be logs ie: /var/log/…

Do the #du -hs /* and all the procedure as I stated before and you will find out where and maybe why you are running out of space. Feel free to paste here the results and ask for more help.

Hi, I don’t think this may be a normal disk space issue, what happened on a server when I searched for this error is MariaDB strangely wrote a big file to /tmp and /tmp on that server is 4G, so I had that issue on a Plesk server, so why mariaDB may write a temp file which is so big like that, the life of this server is many years, and this is the first time it stops because no free space on /tmp partition.

Tks Dane and digital ocean team. Your suggestions were pertinent. I was in a state of pnic when nothing worked at 100% mem utlization and non even the commend to know which first 20 big files were. removing the useles tmp files and restarting my droplet brought me from 100->80%( after temp file removal) ->13%( after droplet restart), I am still working on root casue but not in a state of panic atleast :) Tks…:)

This comment has been deleted

What do you think “no space left on device” means?