Thanks for replying
5.1.55
On 19/04/2011 13:55, Suresh Kuna wrote:
What is the version of MYSQL you are using currently ?
On Tue, Apr 19, 2011 at 3:46 PM, Brent Clark
<brentgclarkl...@gmail.com <mailto:brentgclarkl...@gmail.com>> wrote:
Ive added
innodb_force_recovery=4
Still no go.
-------- Original Message --------
Subject: Mysql issue / crashing
Date: Tue, 19 Apr 2011 12:15:30 +0200
From: Brent Clark <brentgclarkl...@gmail.com
<mailto:brentgclarkl...@gmail.com>>
To: mysql@lists.mysql.com <mailto:mysql@lists.mysql.com>
Hiya
Im getting the following
I ran myisamchk --silent --force */*.MYI
But still I get the following.
I cant see how I can bring Mysql up.
# mysqld2912
110419 12:13:22 [Warning] 'for replication startup options' is
deprecated and will be removed in a future release. Please use
''CHANGE
MASTER'' instead.
110419 12:13:22 [Note] Plugin 'FEDERATED' is disabled.
110419 12:13:22 InnoDB: Initializing buffer pool, size = 512.0M
110419 12:13:22 InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 10 96395066
110419 12:13:22 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 10 96451805
110419 12:13:22 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 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 110419 12:13:22 - 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=201326592
read_buffer_size=2097152
max_used_connections=0
max_threads=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
606853 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 = (nil) thread_stack 0x20000
mysqld(my_print_stacktrace+0x2d) [0xb75de06d]
mysqld(handle_segfault+0x49c) [0xb72ac0cc]
[0xb7018400]
mysqld(page_cur_parse_insert_rec+0x580) [0xb7500390]
mysqld [0xb74ea325]
mysqld(recv_recover_page+0x502) [0xb74ec2e2]
mysqld(buf_page_io_complete+0x624) [0xb74a22e4]
mysqld(fil_aio_wait+0x12d) [0xb74bdb8d]
mysqld [0xb7533d80]
/lib/i686/cmov/libpthread.so.0 [0xb6ffd4c0]
/lib/i686/cmov/libc.so.6(clone+0x5e) [0xb6ded84e]
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
--
Thanks
Suresh Kuna
MySQL DBA
