Percona5.6.10 get error ERROR! The server quit without updating PID file

MySQL & MariaDB Other MySQL® Questions
#1

hey i have meet the same problem,and i install percona5.6.10 via compile(i download Percona-Server-5.6.10-alpha60.2.tar.gz),when i finished install, all is well,but after a short time when i use /etc/init.d/mysqld restart i get error like "The server quit without updating PID file "
so i reinstall the percona,and when i complete ,the mysql service is normal and is running,but sfter about 1 0r 2 hours, when i check,the service status is not running and get error like “mysql is not running and lock file………”,even if i remove /etc/my.cnf,the service is not starting,and weather my percona package is correct?and below is the parameter of compile for percona
tar -zxv -f mysql-5.6.13.tar.gz
cd mysql-5.6.13/
cmake -DCMAKE_INSTALL_PREFIX=/usr/local/mysql
-DMYSQL_UNIX_ADDR=/tmp/mysql.sock
-DDEFAULT_CHARSET=utf8
-DDEFAULT_COLLATION=utf8_general_ci
-DWITH_EXTRA_CHARSETS:STRING=all
-DWITH_INNOBASE_STORAGE_ENGINE=1
-DWITH_MYISAM_STORAGE_ENGINE=1
-DWITH_READLINE=1
-DENABLED_LOCAL_INFILE=1
-DMYSQL_DATADIR=/var/mysql/data
make
male install
/usr/local/mysql/scripts/mysql_install_db
–basedir=/usr/local/mysql
–datadir=/var/mysql/data
–user=mysql

and below if my /etc/my.cnf
[mysqld]

Remove leading # and set to the amount of RAM for the most important data

cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.

innodb_buffer_pool_size = 128M

Remove leading # to turn on a very important data integrity option: logging

changes to the binary log between backups.

log_bin

These are commonly set, remove the # and set as required.

basedir = /usr/local/mysql
datadir = /var/mysql/data
port = 3306
server_id = 1
socket = /tmp/mysql.sock
sort_buffer_size = 1M
join_buffer_size = 1M
query_cache_size = 50M
query_cache_limit = 2M
query_cache_min_res_unit = 2k
thread_stack = 192K
tmp_table_size = 246M
max_heap_table_size = 50M
key_buffer_size = 256M
read_buffer_size = 1M
read_rnd_buffer_size = 10M
bulk_insert_buffer_size = 10M
slow_query_log = 1
log-error = /var/mysql/mysql_error.log
slow_query_log_file = /var/mysq/query_slow.log
long_query_time = 2
log-queries-not-using-indexes = ON

Remove leading # to set options mainly useful for reporting servers.

The server defaults are faster for transactions and fast SELECTs.

Adjust sizes as needed, experiment to find the optimal values.

join_buffer_size = 128M

sort_buffer_size = 2M

read_rnd_buffer_size = 2M

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLE S

#2

Hi,

I’m bit confused. In subject you said about 5.6.10 version and you are giving example of 5.6.13 (Native MySQL not Percona Server) so exactly on which version you are getting this problem? Can you also provide the full mysql error log of the server? Thanks.

#3

sorry,i have make a mistake,and i use Percona-Server-5.6.10-alpha60.2.tar.gz, now i can run mysql server,but when i prees f5 to refresh my website without stopping about 10seconds,i get error :“mysqld_safe mysqld from pid file /var/mysql/data//server.hzxsrc.com.pid ended”,my website run in a vps with nginx+php+percona mysql5.6.10,and before i run website in apache+php+native mysql5.5.1,and if i press f5 without stopping about 10seconds or longer, the website is normal,and below is the error_log

2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘partition’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_CHANGED_PAGES’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_SYS_DATAFILES’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_SYS_TABLESPACES’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN_COLS’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_SYS_FIELDS’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_SYS_COLUMNS’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_SYS_INDEXES’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_SYS_TABLESTATS’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_SYS_TABLES’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_FT_INDEX_TABLE’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_FT_INDEX_CACHE’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_FT_CONFIG’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_FT_BEING_DELETED’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_FT_DELETED’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_FT_DEFAULT_STOPWORD’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_METRICS’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_BUFFER_POOL_STATS’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE_LRU’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX_RESET’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_CMPMEM_RESET’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_CMPMEM’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_CMP_RESET’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_CMP’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_LOCK_WAITS’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_LOCKS’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘INNODB_TRX’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘XTRADB_RSEG’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘XTRADB_INTERNAL_HASH_TABLES’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘XTRADB_READ_VIEW’
2013-08-15 05:51:24 3217 [Note] Shutting down plugin ‘InnoDB’
2013-08-15 05:51:24 3217 [Note] InnoDB: FTS optimize thread exiting.
2013-08-15 05:51:24 3217 [Note] InnoDB: Starting shutdown…
2013-08-15 05:51:26 3217 [Note] InnoDB: Shutdown completed; log sequence number 1626900
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘BLACKHOLE’
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘ARCHIVE’
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘PERFORMANCE_SCHEMA’
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘MRG_MYISAM’
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘MyISAM’
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘MEMORY’
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘CSV’
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘sha256_password’
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘mysql_old_password’
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘mysql_native_password’
2013-08-15 05:51:26 3217 [Note] Shutting down plugin ‘binlog’
2013-08-15 05:51:26 3217 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

130815 05:51:26 mysqld_safe mysqld from pid file /var/mysql/data//server.hzxsrc.com.pid ended

#4

This error log part shows only normal shutdown process. The question is why the service was stopped if not intentionally? Anything interesting earlier in this log? Maybe system log (/var/log/syslog /var/log/messages etc) will tell something?
What happened after you started mysql back, did it stop again later?

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright © 2006 - 2021 Percona LLC. All rights reserved.