The server quit without updating PID file
please help me ,this is my first jobe,my boss ask me must be solve it,but my tech is poor.
thanks in advance
and the log is
----------------------------
root@localhost [/var/lib/mysql]# service mysql start
Starting MySQL................ ERROR! The server quit without updating PID file
(/var/lib/mysql/localhost.localdomain.ltd.pid).
and the log is
160422 05:11:20 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160422 5:11:20 [Note] /usr/sbin/mysqld (mysqld 5.5.48-cll) starting as process 6326 ...
160422 5:11:20 [Note] Plugin 'FEDERATED' is disabled.
160422 5:11:20 InnoDB: The InnoDB memory heap is disabled
160422 5:11:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160422 5:11:20 InnoDB: Compressed tables use zlib 1.2.3
160422 5:11:20 InnoDB: Using Linux native AIO
160422 5:11:20 InnoDB: Initializing buffer pool, size = 128.0M
160422 5:11:20 InnoDB: Completed initialization of buffer pool
160422 5:11:20 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 23490815472
160422 5:11:20 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 23491101887
160422 5:11:20 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Error: tried to read 16384 bytes at offset 0 23576576.
InnoDB: Was only able to read 12288.
InnoDB: Fatal error: cannot read from file. OS error number 17.
160422 5:11:35 InnoDB: Assertion failure in thread 140656762644224 in file os0file.c line 2549
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.21.2 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
09:11:35 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)[0x7ac925]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x687994]
/lib64/libpthread.so.0(+0xf7e0)[0x7fed341d67e0]
/lib64/libc.so.6(gsignal+0x35)[0x7fed3339d625]
/lib64/libc.so.6(abort+0x175)[0x7fed3339ee05]
/usr/sbin/mysqld[0x904133]
/usr/sbin/mysqld[0x906ead]
/usr/sbin/mysqld[0x8cad35]
/usr/sbin/mysqld[0x8a4558]
/usr/sbin/mysqld[0x8a4e23]
/usr/sbin/mysqld[0x897a21]
/usr/sbin/mysqld[0x88b027]
/usr/sbin/mysqld[0x8be5d3]
/usr/sbin/mysqld[0x853567]
/usr/sbin/mysqld[0x821cce]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x68a3a8]
/usr/sbin/mysqld[0x59487a]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa8c)[0x59910c]
/usr/sbin/mysqld[0x517dca]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x44d)[0x51b7ed]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7fed33389d5d]
/usr/sbin/mysqld[0x510a69]
The manual page at MySQL :: MySQL 5.7 Reference Manual :: B.5.3.3 What to Do If MySQL Keeps Crashing contains
information that should help you find out what is causing the crash.
160422 05:11:35 mysqld_safe mysqld from pid file /var/lib/mysql/localhost.localdomain.ltd.pid ended
-
Hello It looks like your InnoDB files are corrupted. It can either be database files or ibdata files. The following steps are widely used for InnoDB recovery. The first step is to make the server accessible by switching it to recovery mode. You can perform this by adding the following entry to /etc/my.cnf and restarting the server [mysql] innodb_force_recovery = 4 In most cases, the server will be up. Take the db backups using mysqldump. Once the backup is complete, stop the server and delete the dbs and Ibdata files. Then remove the entries for recovery mode and restart the server manually. Once the server is up, restore the dbs using the backups taken. A number of detailed articles with real time examples are available in the net. Please refer them and do accordingly Best Wishes :) 0 -
Hello :), Also please give a try with following guide. InnoDB Corruption Repair Guide 0 -
Hello :) Yes, as mentioned, please follow the guide available at: InnoDB Corruption Repair Guide Thank you. 0
Please sign in to leave a comment.
Comments
3 comments