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

**URL:** <https://forums.percona.com/t/percona5-6-10-get-error-error-the-server-quit-without-updating-pid-file/2876>\
**Category:** Other MySQL® Questions\
**Created:** [August 13, 2013, 3:48am UTC](https://forums.percona.com/t/percona5-6-10-get-error-error-the-server-quit-without-updating-pid-file/2876 "2013-08-13T03:48:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hellogxp](https://avatars.discourse-cdn.com/v4/letter/h/cdc98d/32.png) [@hellogxp](https://forums.percona.com/u/hellogxp)\
**Post date:** [August 13, 2013, 3:48am UTC](https://forums.percona.com/t/percona5-6-10-get-error-error-the-server-quit-without-updating-pid-file/2876/1 "2013-08-13T03:48:15Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![niljoshi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/niljoshi/32/16889_2.png) [@niljoshi](https://forums.percona.com/u/niljoshi)\
**Post date:** [August 13, 2013, 8:58pm UTC](https://forums.percona.com/t/percona5-6-10-get-error-error-the-server-quit-without-updating-pid-file/2876/2 "2013-08-13T20:58:20Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![hellogxp](https://avatars.discourse-cdn.com/v4/letter/h/cdc98d/32.png) [@hellogxp](https://forums.percona.com/u/hellogxp)\
**Post date:** [August 15, 2013, 7:36am UTC](https://forums.percona.com/t/percona5-6-10-get-error-error-the-server-quit-without-updating-pid-file/2876/3 "2013-08-15T07:36:11Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![przemek](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/przemek/32/3_2.png) [@przemek](https://forums.percona.com/u/przemek)\
**Post date:** [August 16, 2013, 6:13am UTC](https://forums.percona.com/t/percona5-6-10-get-error-error-the-server-quit-without-updating-pid-file/2876/4 "2013-08-16T06:13:58Z")

</div>

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?
