MySQL Boot error error! MySQL server PID file could not being found solution

Source: Internet
Author: User

/etc/init.d/mysql Start Unable to start the MySQL error message is as follows:

error! MySQL server PID file could not being found!

Starting MySQL. error! The server quit without updating PID file (/usr/local/mysql/var/ayxxxxxxxxxxx.pid).


The full log information is as follows:


140902 18:11:33 Mysqld_safe starting mysqld daemon with databases from/usr/local/mysql/var140902 18:11:33 innodb:the Inn ODB memory Heap is disabled140902 18:11:33 innodb:mutexes and rw_locks use GCC atomic builtins140902 18:11:33 innodb:com Pressed tables use zlib 1.2.3140902 18:11:33 innodb:initializing buffer pool, size = 16.0m140902 18:11:33 innodb:complet Ed initialization of buffer pool140902 18:11:33 innodb:highest supported file format is barracuda.140902 18:11:33 InnoDB : Waiting for the background threads to start140902 18:11:34 innodb:5.5.37 started; Log sequence number 18321078305/usr/local/mysql/bin/mysqld:file './mysql-bin.000035 ' not Found (errcode:2) 140902 18:11 : [ERROR] Failed to open log (file './mysql-bin.000035 ', errno 2) 140902 18:11:34 [ERROR] Could not open log file140902 1 8:11:34 [ERROR] Can ' t init tc log140902 18:11:34 [ERROR] Aborting140902 18:11:34 innodb:starting shutdown ... 140902 18:11:35 Innodb:shutdown completed; Log sequence Number 18321078305140902 18:11:35 [Note]/usr/local/mysql/bin/mysqld:shutdown complete140902 18:11:35 mysqld_safe mysqld from PID file/us R/local/mysql/var/ay140429171715z.pid ended140902 18:12:55 Mysqld_safe starting mysqld daemon with databases from/usr/ local/mysql/var140902 18:12:56 innodb:the InnoDB memory heap is disabled140902 18:12:56 innodb:mutexes and Rw_locks use GCC Atomic builtins140902 18:12:56 innodb:compressed tables use zlib 1.2.3140902 18:12:56 innodb:initializing buffer poo L, size = 16.0m140902 18:12:56 innodb:completed initialization of buffer pool140902 18:12:56 Innodb:highest supported fi Le format is barracuda.140902 18:12:57 innodb:waiting for the background threads to start140902 18:12:58 innodb:5.5.37 Started Log sequence number 18321078305/usr/local/mysql/bin/mysqld:file './mysql-bin.000035 ' not Found (errcode:2) 140902 18:12 : [ERROR] Failed to open log (file './mysql-bin.000035 ', errno 2) 140902 18:12:58 [ERROR] Could not open log file140902 1 8:12:58 [ERROR] Can 'T init tc log140902 18:12:58 [ERROR] Aborting140902 18:12:58 innodb:starting shutdown ... 140902 18:12:58 Innodb:shutdown completed; Log sequence number 18321078305140902 18:12:58 [Note]/usr/local/mysql/bin/mysqld:shutdown complete140902 18:12:58 Mysqld_safe mysqld from PID file/usr/local/mysql/var/ay140429171715z.pid ended140902 18:30:59 Mysqld_safe starting Mysqld daemon with databases from/usr/local/mysql/var140902 18:30:59 innodb:the InnoDB memory Heap is disabled140902 18: 30:59 innodb:mutexes and Rw_locks use GCC atomic builtins140902 18:30:59 innodb:compressed tables use zlib 1.2.3140902 1 8:30:59 innodb:initializing buffer pool, size = 16.0m140902 18:30:59 innodb:completed initialization of buffer pool14090 2 18:30:59 innodb:highest supported file format is barracuda.140902 18:31:00 innodb:waiting for the background threads To start140902 18:31:01 innodb:5.5.37 started; Log sequence number 18321078305/usr/local/mysql/bin/mysqld:file './mysql-bin.000035 ' not Found (Errcode:2) 140902 18:31:01 [ERROR] Failed to open log (file './mysql-bin.000035 ', errno 2) 140902 18:31:01 [ERROR] Could No T open log file140902 18:31:01 [ERROR] Can ' t init tc log140902 18:31:01 [ERROR] Aborting140902 18:31:01 innodb:starting Shutdown ... 140902 18:31:01 Innodb:shutdown completed; Log sequence number 18321078305140902 18:31:01 [Note]/usr/local/mysql/bin/mysqld:shutdown complete140902 18:31:01 Mysqld_safe mysqld from PID file/usr/local/mysql/var/ay140429171715z.pid ended140902 18:32:10 Mysqld_safe starting Mysqld daemon with databases from/usr/local/mysql/var140902 18:32:10 innodb:the InnoDB memory Heap is disabled140902 18: 32:10 innodb:mutexes and Rw_locks use GCC atomic builtins140902 18:32:10 innodb:compressed tables use zlib 1.2.3140902 1 8:32:10 innodb:initializing buffer pool, size = 16.0m140902 18:32:10 innodb:completed initialization of buffer pool14090 2 18:32:10 innodb:highest supported file format is barracuda.140902 18:32:10 innodb:waiting for the Background threads to start140902 18:32:11 innodb:5.5.37 started; Log sequence number 18321078305/usr/local/mysql/bin/mysqld:file './mysql-bin.000035 ' not Found (errcode:2) 140902 18:32 : one [ERROR] Failed to open log (file "./mysql-bin.000035 ', errno 2) 140902 18:32:11 [ERROR] Could not open log file140902 1 8:32:11 [ERROR] Can ' t init tc log140902 18:32:11 [ERROR] Aborting140902 18:32:11 innodb:starting shutdown ... 140902 18:32:11 Innodb:shutdown completed; Log sequence number 18321078305140902 18:32:11 [Note]/usr/local/mysql/bin/mysqld:shutdown complete140902 18:32:11 Mysqld_safe mysqld from PID file/usr/local/mysql/var/ay140429171715z.pid ended140902 18:32:14 Mysqld_safe starting Mysqld daemon with databases from/usr/local/mysql/var140902 18:32:14 innodb:the InnoDB memory Heap is disabled140902 18: 32:14 innodb:mutexes and Rw_locks use GCC atomic builtins140902 18:32:14 innodb:compressed tables use zlib 1.2.3140902 1 8:32:14 innodb:initializing buffer pool, size = 16.0m140902 18:32:14 innodb:completed Initialization of buffer pool140902 18:32:14 innodb:highest supported file format is Barracu da.140902 18:32:14 innodb:waiting for the background threads to start140902 18:32:15 innodb:5.5.37 started; Log sequence number 18321078305/usr/local/mysql/bin/mysqld:file './mysql-bin.000035 ' not Found (errcode:2) 140902 18:32 : [ERROR] Failed to open log (file './mysql-bin.000035 ', errno 2) 140902 18:32:15 [ERROR] Could not open log file140902 1 8:32:15 [ERROR] Can ' t init tc log140902 18:32:15 [ERROR] Aborting140902 18:32:15 innodb:starting shutdown ... 140902 18:32:15 Innodb:shutdown completed; Log sequence number 18321078305140902 18:32:15 [Note]/usr/local/mysql/bin/mysqld:shutdown complete140902 18:32:15 Mysqld_safe mysqld from PID file/usr/local/mysql/var/ay140429171715z.pid ended140902 18:33:15 Mysqld_safe starting Mysqld daemon with databases from/usr/local/mysql/var140902 18:33:15 innodb:the InnoDB memory Heap is disabled140902 18: 33:15 Innodb:muTExES and Rw_locks use GCC atomic builtins140902 18:33:15 innodb:compressed tables use zlib 1.2.3140902 18:33:15 InnoDB: Initializing buffer pool, size = 16.0m140902 18:33:15 innodb:completed initialization of buffer pool140902 18:33:15 Innod B:highest supported file format is barracuda.140902 18:33:15 innodb:waiting for the background threads to start140902 1 8:33:16 innodb:5.5.37 started; Log sequence number 18321078305/usr/local/mysql/bin/mysqld:file './mysql-bin.000035 ' not Found (errcode:2) 140902 18:33 : [ERROR] Failed to open log (file './mysql-bin.000035 ', errno 2) 140902 18:33:16 [ERROR] Could not open log file140902 1 8:33:16 [ERROR] Can ' t init tc log140902 18:33:16 [ERROR] Aborting140902 18:33:16 innodb:starting shutdown ... 140902 18:33:17 Innodb:shutdown completed; Log sequence number 18321078305140902 18:33:17 [Note]/usr/local/mysql/bin/mysqld:shutdown complete140902 18:33:17 Mysqld_safe mysqld from PID file/usr/local/mysql/var/ay140429171715z.pid ended140902 18:34:05 Mysqld_safe starting mysqld daemon with databases from/usr/local/mysql/var140902 18:34:05 [Warning] your need to use --log-bin to make--binlog-format work.140902 18:34:05 innodb:the InnoDB memory heap is disabled140902 18:34:05 InnoDB: Mutexes and Rw_locks use GCC atomic builtins140902 18:34:05 innodb:compressed tables use zlib 1.2.3140902 18:34:05 InnoDB : Initializing buffer pool, size = 16.0m140902 18:34:05 innodb:completed initialization of buffer pool140902 18:34:05 Inn  Odb:highest supported file format is barracuda.140902 18:34:05 innodb:waiting for the background threads to start140902 18:34:06 innodb:5.5.37 started; Log sequence number 18321078305140902 18:34:06 [Note] Server hostname (bind-address): ' 0.0.0.0 '; port:3306140902 18:34:06 [note]-' 0.0.0.0 ' resolves to ' 0.0.0.0 '; 140902 18:34:06 [note] Server sockets created on IP: '  0.0.0.0 '. 140902 18:34:07 [note] Event scheduler:loaded 0 events140902 18:34:07 [note]/usr/local/mysql/bin/mysqld:ready For connections. Version: ' 5.5.37 ' socket: '/tmp/mysql.sock ' port:3306 Source distribution140902 18:34:30 [Note]/usr/local/mysql/bin/m Ysqld:normal shutdown140902 18:34:30 [Note] Event scheduler:purging the queue. 0 events140902 18:34:30 innodb:starting shutdown ... 140902 18:34:30 Innodb:shutdown completed; Log sequence number 18321078305140902 18:34:30 [Note]/usr/local/mysql/bin/mysqld:shutdown complete140902 18:34:30 Mysqld_safe mysqld from PID file/usr/local/mysql/var/ay140429171715z.pid ended140902 18:34:31 Mysqld_safe starting Mysqld daemon with Databases from/usr/local/mysql/var140902 18:34:31 [Warning] Your need to use--log-bin to make--binlog -format work.140902 18:34:31 innodb:the InnoDB memory heap is disabled140902 18:34:31 innodb:mutexes and Rw_locks use GC  C Atomic builtins140902 18:34:31 innodb:compressed tables use zlib 1.2.3140902 18:34:31 innodb:initializing buffer pool, Size = 16.0m140902 18:34:31 innodb:completed initialization of buffer pool140902 18:34:31 InnoDB:Highest supported file format is barracuda.140902 18:34:31 innodb:waiting for the background threads to start140902 18:3 4:32 innodb:5.5.37 started; Log sequence number 18321078305140902 18:34:32 [Note] Server hostname (bind-address): ' 0.0.0.0 '; port:3306140902 18:34:32 [note]-' 0.0.0.0 ' resolves to ' 0.0.0.0 '; 140902 18:34:32 [note] Server sockets created on IP: '  0.0.0.0 '. 140902 18:34:32 [note] Event scheduler:loaded 0 events140902 18:34:32 [note]/usr/local/mysql/bin/mysqld:ready for connections. Version: ' 5.5.37 ' socket: '/tmp/mysql.sock ' port:3306 Source distribution


boot will error starting MySQL. error! The server quit without updating PID file (/var/local/mysql/var/ayxxxxxxx.pid) because the mysql-bin.0000* file fills the system disk, Insufficient disk space is causing the write to fail.


Workaround:

1: Delete all mysql-bin.0000* log files all RM off

2: Modify in the my.cnf file, find Log-bin=mysql-bin to comment out the start, will not produce 2 binary mysql-bin.0000* log file

MySQL Startup error error! MySQL server PID file could not being found workaround

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.