The server quit without updating PID file

The mysql of my server Centos with WHM/cPanel is down. When I try to restart it appear this message: ERROR! The server quit without updating PID file I see the .err file of var/lib/mysql and appear this:


190123  0:11:20 [Note] Plugin 'FEDERATED' is disabled.
190123  0:11:20 InnoDB: The InnoDB memory heap is disabled
190123  0:11:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190123  0:11:20 InnoDB: Compressed tables use zlib 1.2.3
190123  0:11:20 InnoDB: Using Linux native AIO
190123  0:11:20 InnoDB: Initializing buffer pool, size = 118.0M
190123  0:11:20 InnoDB: Completed initialization of buffer pool
190123  0:11:20 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 21179961
190123  0:11:20  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: trying to add tablespace 247828 of name './aulavirt_data2/mdl_config.ibd'
InnoDB: to the tablespace memory cache, but tablespace
InnoDB: 247828 of name './aulavirt_data/mdl_groups_members.ibd' already exists in the tablespace
InnoDB: memory cache!
InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery
InnoDB: even though the tablespace creation of this table failed.
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 21266846
190123  0:11:20  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: InnoDB: Error: trying to access page number 0 in space 248519,
InnoDB: space name ./novagas_novagaspe/#sql-58ae_5f.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
190123  0:11:20  InnoDB: Assertion failure in thread 139842894915328 in file fil0fil.c line 4578
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to MySQL Bugs.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 14.23.2 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
05:11:20 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338551 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7aeab5]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6892e4]
/lib64/libpthread.so.0(+0xf7e0)[0x7f2fb5d197e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f2fb50e1495]
/lib64/libc.so.6(abort+0x175)[0x7f2fb50e2c75]
/usr/sbin/mysqld[0x8cd31c]
/usr/sbin/mysqld[0x8a69a8]
/usr/sbin/mysqld[0x8a707c]
/usr/sbin/mysqld[0x8fcb74]
/usr/sbin/mysqld[0x8f8554]
/usr/sbin/mysqld[0x8f8e1f]
/usr/sbin/mysqld[0x8cf618]
/usr/sbin/mysqld[0x855ad6]
/usr/sbin/mysqld[0x8241be]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x68bc68]
/usr/sbin/mysqld[0x5957fa]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa8c)[0x59a0dc]
/usr/sbin/mysqld[0x51866a]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x44d)[0x51c15d]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7f2fb50cdd1d]
/usr/sbin/mysqld[0x510eb9]
The manual page at MySQL :: MySQL 8.0 Reference Manual :: B.6.3.3 What to Do If MySQL Keeps Crashing contains
information that should help you find out what is causing the crash.

balitas

January 23, 2019 06:55

I solved it ERROR! The server quit without updating PID file | Web Hosting Talk using the last solution :D

cPanelLauren

January 23, 2019 20:03

Hi @balitas I'm glad to see setting Force Recovery to 4 resolved the issue. I would suggest reading over the tutorial here though: Tutorial - InnoDB Corruption Repair Guide Really you shouldn't continue to run InnoDB in recovery this should only be used until you're able to implement a resolution. Thanks!

The server quit without updating PID file

Comments

Didn't find what you were looking for?