数据库无法启动Starting MySQL..The server quit without updating PID file (/usr/local/mys

曼陀羅

元旦回来就这样了。。啥也没干

[ 本帖最后由 曼陀羅 于 2016-1-3 22:28 编辑 ]

曼陀羅

160103 22:19:38 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160103 22:19:38 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-log) starting as process 21755 ...
160103 22:19:38 [Note] Plugin 'FEDERATED' is disabled.
160103 22:19:38 InnoDB: The InnoDB memory heap is disabled
160103 22:19:38 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160103 22:19:38 InnoDB: Compressed tables use zlib 1.2.3
160103 22:19:38 InnoDB: Initializing buffer pool, size = 16.0M
160103 22:19:38 InnoDB: Completed initialization of buffer pool
160103 22:19:38 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 7088377
160103 22:19:38  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 7128788
InnoDB: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 4800
160103 22:19:38  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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: Last MySQL binlog file position 0 19751, file name ./mysql-bin.000893
InnoDB: Cleaning up trx with id 4452
InnoDB: Cleaning up trx with id 42E5
160103 22:19:38  InnoDB: Waiting for the background threads to start
160103 22:19:39 InnoDB: 5.5.46 started; log sequence number 7128788
160103 22:19:39 [Note] Recovering after a crash using mysql-bin
160103 22:19:39 [Note] Starting crash recovery...
160103 22:19:39 [Note] Crash recovery finished.
160103 22:19:39 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
160103 22:19:39 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
160103 22:19:39 [Note] Server socket created on IP: '0.0.0.0'.
160103 22:19:39  InnoDB: Assertion failure in thread 2850012016 in file trx0purge.c line 840
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
14:19:39 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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=500
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 = 404081 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 0x30000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)[0x8392c13]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)[0x8286492]
[0xb77d1500]
/lib/libc.so.6(abort+0x17a)[0xb747914a]
/usr/local/mysql/bin/mysqld[0x83e9fc8]
/usr/local/mysql/bin/mysqld[0x83ea547]
/usr/local/mysql/bin/mysqld[0x84a287e]
/usr/local/mysql/bin/mysqld[0x8498f8e]
/usr/local/mysql/bin/mysqld[0x83e8e5e]
/usr/local/mysql/bin/mysqld[0x83dc5a5]
/usr/local/mysql/bin/mysqld[0x83e04b7]
/lib/libpthread.so.0(+0x6b69)[0xb7770b69]
/lib/libc.so.6(clone+0x5e)[0xb752fc9e]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
160103 22:19:39 mysqld_safe mysqld from pid file /usr/local/mysql/var/ferristale.pid ended