Shulou(Shulou.com)05/31 Report--

Today, I would like to talk to you about what to do about MYSQL's sudden error report RASH. Many people may not know much about it. In order to make you understand better, the editor summarized the following content for you. I hope you can get something according to this article.

MYSQL log:

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 12 34 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 amp O thread: connected to master 'replicator@10.247.63.2:3306',replication 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 socket: / tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)

/ VAR/LOG/MESSAGES log is as follows:

Jul 21 11:01:42 r21c05033 kernel: mysqld [29543]: segfault at 0000000000000038 rip 000000000077d825 rsp 0000000041fd5fa0 error 4

The error in the SLAVE MYSQL log is as follows:

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 amp O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.000458' at postion 906880987

100721 11:01:42 [ERROR] Slave Iamp O: error reconnecting to master 'replicator@10.247.63.1:3306'-retry-time: 60 retries: 86400, Error_code: 2013

100721 11:02:42 [Note] Slave: connected to master 'replicator@10.247.63.1:3306',replication resumed in log' mysql-bin.000458' at position 906880987

Many friends on the Internet also encountered similar mistakes, but MS did not find the reason. Only know BUG. Have any friends ever come across and analyzed the situation together?

Root@r21c05033.btc.aliyun.com # 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

After reading the above, do you have any further understanding of what to do when MYSQL suddenly reports an error RASH? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.