R
R
ratuy2018-09-03 11:28:27
Nginx
ratuy, 2018-09-03 11:28:27

Error "mysqld: Disk is full writing '/var/tmp/#sql_3946_0.MAD' (Errcode: 28). Waiting for someone to free space...”, how to solve?

The log is:(/var/log/mariadb/mariadb.log)

180831 18:50:50 [Warning] mysqld: Disk is full writing '/var/tmp/#sql_3946_0.MAD' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
180831 18:50:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 18:50:50 [Warning] mysqld: Disk is full writing './mysql-bin.001289' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
180831 18:50:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:00:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:00:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:10:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:10:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:20:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:20:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:30:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:30:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:40:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:40:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:50:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 19:50:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:00:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:00:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:09:58 [Warning] IP address '*' could not be resolved: Name or service not known
180831 20:10:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:10:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:20:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:20:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:30:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:30:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:40:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:40:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:43:58 [Warning] IP address '*' could not be resolved: Name or service not known
180831 20:50:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 20:50:50 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
180831 21:00:50 [Warning] mysqld: Retry in 60 secs. Mess180903  8:38:24  InnoDB: Starting shutdown...
180903  8:38:27  InnoDB: Shutdown completed; log sequence number 3369227524552
180903  8:38:27 [Note] /usr/libexec/mysqld: Shutdown complete

How to fix this error, I understand that the disk is full ... And what is usually done in these cases? Thanks for the answer!

Answer the question

In order to leave comments, you need to log in

4 answer(s)
R
Ruslan Fedoseev, 2018-09-03
@martin74ua

clear disk space.
increase disk space.

T
TyzhSysAdmin, 2018-09-03
@POS_troi

The data you provided refers to the moment "after" and does not mean at all that at some point your 40 free gigs did not turn into a pumpkin.
1. Attempt to backup
2. Compromise of the server and attempt to merge the database
And another 100,500 scenarios.
Well, at this point, you have already been pointed out to stackoverflow a couple of times.

C
CityCat4, 2018-09-03
@CityCat4

1. Stop muscle - yes, data loss is possible!
2. Add places
3. Analyze the situation - why the place is over.

V
Viktor Taran, 2019-04-10
@shambler81

1. ran out of space
2. run the muscle check all databases especially innodb, check all databases and tables
if there are errors dump all databases.
and just do something after that.
further autorepair, again, of all databases
Well, then it’s already fun if something pokotsalsya.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question