MySQL Forums :: Newbie :: MYsql getting crash


Advanced Search

MYsql getting crash
Posted by: chella kutty ()
Date: October 08, 2009 03:05AM

Dear all

Now started facing problem like mysql service got automatically restarted with Error Signal 11. it’s happening multiple times in day . I have checked the mysql error Log and got Error’s like


Number of processes running now: 0
091008 09:18:53 mysqld restarted
091008 9:18:53 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...
091008 9:18:54 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 1078279975.
InnoDB: Doing recovery: scanned up to log sequence number 2 1078279975
InnoDB: Last MySQL binlog file position 0 20917, file name ./mysql-bin.000007
091008 9:18:56 InnoDB: Started; log sequence number 2 1078279975
091008 9:18:56 [Note] Recovering after a crash using mysql-bin
091008 9:18:56 [Note] Starting crash recovery...
091008 9:18:56 [Note] Crash recovery finished.
091008 9:18:56 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.22-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
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.

key_buffer_size=268435456
read_buffer_size=2093056
max_used_connections=7
max_connections=800
threads_connected=5
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3535737 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


Number of processes running now: 0
091008 09:19:43 mysqld restarted
091008 9:19:44 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...
091008 9:19:45 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 1078367930.
InnoDB: Doing recovery: scanned up to log sequence number 2 1078370635
091008 9:19:45 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 243987, file name ./mysql-bin.000009
091008 9:19:47 InnoDB: Started; log sequence number 2 1078370635
091008 9:19:47 [Note] Recovering after a crash using mysql-bin
091008 9:19:47 [Note] Starting crash recovery...
091008 9:19:47 [Note] Crash recovery finished.
091008 9:19:47 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.22-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
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.

key_buffer_size=268435456
read_buffer_size=2093056
max_used_connections=2
max_connections=800
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3535737 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


Number of processes running now: 0
091008 09:19:51 mysqld restarted
091008 9:19:52 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...
091008 9:19:53 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 1078367930.
InnoDB: Doing recovery: scanned up to log sequence number 2 1078372246
091008 9:19:54 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 1314, file name ./mysql-bin.000010
091008 9:19:55 InnoDB: Started; log sequence number 2 1078372246
091008 9:19:55 [Note] Recovering after a crash using mysql-bin
091008 9:19:55 [Note] Starting crash recovery...
091008 9:19:55 [Note] Crash recovery finished.
091008 9:19:55 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.22-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
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.

key_buffer_size=268435456
read_buffer_size=2093056
max_used_connections=30
max_connections=800
threads_connected=28
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3535737 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


The System Error Log :

kernel: mysqld[16293]: segfault at 00000000bc9457c8 rip 00002aaabc94577e rsp 0000000000002aaa error 6


Can any one suggest on this ? what could be the reason ?

Mysql Version : 5.0.22
OS : RHEL 5.2

Options: ReplyQuote


Subject Written By Posted
MYsql getting crash chella kutty 10/08/2009 03:05AM
Re: MYsql getting crash Rick James 10/10/2009 10:55PM
Re: MYsql getting crash chella kutty 10/26/2009 11:51PM
Re: MYsql getting crash Ramesh Kumar 10/21/2009 10:57PM
Re: MYsql getting crash Rick James 10/21/2009 11:13PM
Re: MYsql getting crash Ramesh Kumar 10/22/2009 12:23AM
Re: MYsql getting crash Rick James 10/22/2009 09:21AM
Re: MYsql getting crash chella kutty 10/26/2009 11:56PM
Re: MYsql getting crash Rick James 10/27/2009 07:37AM
Re: MYsql getting crash Ramesh Kumar 10/28/2009 03:16AM
Re: MYsql getting crash Rick James 10/28/2009 10:23PM
Re: MYsql getting crash Ramesh Kumar 10/29/2009 12:24AM
Re: MYsql getting crash Rick James 10/29/2009 08:20PM
Re: MYsql getting crash Ramesh Kumar 10/29/2009 11:39PM
Re: MYsql getting crash Rick James 10/30/2009 10:16AM
Re: MYsql getting crash Ramesh Kumar 11/06/2009 02:33AM
Re: MYsql getting crash Rick James 11/06/2009 10:28AM
Re: MYsql getting crash sudhanshu pandey 10/27/2009 03:14AM
Re: MYsql getting crash sudhanshu pandey 10/27/2009 03:16AM
Re: MYsql getting crash Linus Mwaniki 12/06/2009 07:51AM
Re: MYsql getting crash roy ho 12/30/2009 11:42PM
Re: MYsql getting crash Rick James 12/31/2009 03:06AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.