早上MYSQL突然 CRASH
100721 11:01:42 - mysqld got signal 11 ;
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.[@more@]
key_buffer_size=335544320
read_buffer_size=1048576
max_used_connections=149
max_threads=4000
threads_connected=43
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8560336 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x2aac7c25b990
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 = 0x46ba6f20 thread_stack 0x40000
100721 11:01:42 mysqld_safe Number of processes running now: 0
100721 11:01:42 mysqld_safe mysqld restarted
InnoDB: Log scan progressed past the checkpoint lsn 63 1559628325
100721 11:01:43 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 63 1564041997
100721 11:01:44 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 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 3
7 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 8
1 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 906880987, file name /home/mysql/data/mysql/mysql-bin.000458
100721 11:01:54 InnoDB: Started; log sequence number 63 1564041997
100721 11:01:54 [Note] Recovering after a crash using /home/mysql/data/mysql/mysql-bin
100721 11:01:56 [Note] Starting crash recovery...
100721 11:01:56 [Note] Crash recovery finished.
100721 11:01:57 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000456' at position 409173074, relay log
'/home/mysql/data/mysql/slave-relay.001030' position: 251
100721 11:01:57 [Note] Slave I/O thread: connected to master started in log 'mysql-bin.000
456' at position 409173074
100721 11:01:57 [Note] Event Scheduler: Loaded 0 events
100721 11:01:57 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.40-community-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
/VAR/LOG/MESSAGES 日誌如下:
Jul 21 11:01:42 r21c05033 kernel: mysqld[29543]: segfault at 0000000000000038 rip 000000000077d825 rsp 0000000041fd5fa0 error 4
SLAVE MYSQL 日誌報錯如下:
100721 11:01:42 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
100721 11:01:42 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.000458' at postion 906880987
100721 11:01:42 [ERROR] Slave I/O: error reconnecting to master - retry-time: 60 retries: 86400, Error_code: 2013
100721 11:02:42 [Note] Slave: connected to master resumed in log 'mysql-bin.000458' at position 906880987
網上很多朋友也碰到了類似的錯誤,但MS都沒有找到原因。只知道BUG. 有沒有朋友碰到過,一起分析下狀況?
# free
total used free shared buffers cached
Mem: 24677088 18645608 6031480 0 447856 16351076
-/+ buffers/cache: 1846676 22830412
Swap: 2096440 228 2096212
# /etc/my.cnf
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 8M
join_buffer_size = 16M
key_buffer_size = 320M
bulk_insert_buffer_size = 64M
myisam_sort_buffer_size = 128M
innodb_additional_mem_pool_size = 300M
innodb_buffer_pool_size = 6G
innodb_log_buffer_size = 4M
innodb_file_per_table
innodb_doublewrite=1
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/703656/viewspace-1035448/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- mysql crash with disk sector errorMySqlError
- Latch導致MySQL CrashMySql
- MySQL crash recovery恢復慢分析MySql
- MySQL InnoDB Update和Crash Recovery流程MySql
- 【MySQL】MySQL5.6新特性之crash-safeMySql
- MySQL 的 crash-safe 原理解析MySql
- MySQL:Innodb crash recovery一些程式碼MySql
- MySQL 偶爾抽風,效能突然下降MySql
- 【MySQL】一條SQL使磁碟暴漲並導致MySQL CrashMySql
- 故障分析 | MySQL : slave_compressed_protocol 導致 crashMySqlProtocol
- mysql效能測試庫的一次CRASH恢復MySql
- 排查Mysql突然變慢的一次過程MySql
- soasta:84%的人早上起來使用APPASTAPP
- postgres crash recovery
- 故障分析 | MySQL 5.7 使用臨時表導致資料庫 CrashMySql資料庫
- MySQL:5.7.11 超過最大開啟檔案數crash原因解析MySql
- 【MySQL】表索引損壞致Crash及修復過程一則MySql索引
- 突然斷電,是否會影響Mysql的執行結果MySql
- 解析 crash log(一)
- crash日誌分析
- Crash日誌解析
- DB2 CRASHDB2
- MySQL 資料庫崩潰(crash)的常見原因和解決辦法MySql資料庫
- 回顧 crash log 分析
- iOS Crash不崩潰iOS
- WKCrashSDK - crash攔截工具
- [譯][A crash course in WebAssembly] assemblyWeb
- 淺談iOS Crash(2)iOS
- 淺談iOS Crash(一)iOS
- Overview of Instance and Crash RecoveryView
- iOS-Crash日誌抓取iOS
- iOS中常見Crash總結iOS
- SQL Server進行Crash RecoverySQLServer
- Android Native Crash 收集Android
- Crash 日誌符號化符號
- TypeScript Crash Course: Property Access ModifiersTypeScript
- iOS 防止Crash之runtimeiOS
- iOS開發之避免crashiOS