Mysql:can ' t start server:can ' t create PID file:no space left on Device_mysql

Solve case One:

Today, all the Web sites on the company's servers have problems, some open no data, and some are directly blank.

My first reaction was that the database was dead. Open remote, into the system, service mysqld stop failed. Service mysqld start and so a good freshman meeting, prompted timeout error occurred trying to start MySQL Daemon

First thought is a MySQL user problem, query system users completely no problem.

Open log Log a look, the problem arises can ' t start server:can ' t create PID file:no space left on device;

Df-h looked at the disk, 500G of hard disk has been used 100%, usable for 0;

One bite to erase the Var/log folder. Unexpectedly, log logs have accumulated up to 32G.

Khan!!! And then start MySQL. Everything's fine.

Solve case Two:

Recently in the maintenance of Linux server found that the site is not open, after the check found that the MySQL database has been down, anyway, is not start up.

Then look at the MySQL log file

Show can ' t start server:can ' t create PID file:no space left on device

This error.

Prompt for insufficient disk space

Then use the df-h command to view

I found out that all the disk capacity ran out, so I wanted to see who was taking the
With the command:
Find/tmp-size +100000000c
Find files that are larger than 100M in the following disk
Unexpectedly appears:

Tomcat's log file takes up 443G, that's disgusting.

Erase this log file
RM-RF Catalina.out
Restart MySQL.
It is best to reboot the Linux OS.

Solve the case three:

MySQL failed to start and the log appears as follows:

Copy Code code as follows:

120321 14:23:54 innodb:1.1.8 started; Log sequence Number 1595695
120321 14:23:54 [ERROR]/usr/libexec/mysqld:error writing file '/var/run/mysqld/mysqld.pid ' (errcode:28)
120321 14:23:54 [ERROR] Can ' t start server:can ' t create PID file:no space left on device
120321 14:23:54 mysqld_safe Number of processes running now:0
120321 14:23:54 Mysqld_safe mysqld restarted
120321 14:23:54 [note] Plugin ' federated ' is disabled.
120321 14:23:54 innodb:the InnoDB memory heap is disabled
120321 14:23:54 innodb:mutexes and rw_locks use InnoDB ' s own implementation
120321 14:23:54 innodb:compressed tables use zlib 1.2.3
120321 14:23:54 innodb:using Linux native AIO
120321 14:23:54 innodb:initializing buffer pool, size = 128.0M
120321 14:23:54 innodb:completed initialization of buffer pool
120321 14:23:54 innodb:highest Supported file format is barracuda.
120321 14:23:55 innodb:waiting for the background threads to start

In fact, the answer is very simple,
There is no disk space in the no spaces left on device. Clean up the/var/log space!