Help，MySQL不停的重启

akflanker

我的MySQL数据库运行了一段时间后，就不停的重启。想把数据倒出来，但是一直报数据库错误。。。。。。

似乎是bug？


You are running a statically-linked LinuxThreads binary on an NPTL system.
This can result in crashes on some distributions due to LT/NPTL conflicts.
You should either build a dynamically-linked binary, or force LinuxThreads
to be used with the LD_ASSUME_KERNEL environment variable. Please consult
the documentation for your distribution on how to do that.
InnoDB: Log scan progressed past the checkpoint lsn 10 3005229284
080714 20:49: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...
InnoDB: Doing recovery: scanned up to log sequence number 10 3006757860
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 124 row operations to undo
InnoDB: Trx id counter is 0 236731648
080714 20:49:53  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 76889371, file name /archive/logs/mysqld-bin.000028
InnoDB: Starting in background the rollback of uncommitted transactions
080714 20:49:57  InnoDB: Rolling back trx with id 0 236730385, 124 rows to undo
080714 20:49:57  InnoDB: Started; log sequence number 10 3006757860
080714 20:49:57 [Note] /opt/mysql/libexec/mysqld: ready for connections.
Version: '5.0.51-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
080714 20:50:02 - 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=16384
read_buffer_size=258048
max_used_connections=0
max_connections=200
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 63214 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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...
Cannot determine thread, fp=0xbeffeac8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80d5051
0x83592fc
0x82cf414
0x823e8ff
0x825c5d2
0x825cc44
0x824474a
0x823d750
0x821ce5d
0x8272670
0x8353c35
0x838cd2a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

枫影谁用了

你在my.cnf里的某些值设置得高了吧。

akflanker

原帖由 枫影谁用了 于 2008-7-15 11:40 发表
你在my.cnf里的某些值设置得高了吧。

[client]
port                            =       3306
socket                          =       /tmp/mysql.sock

[mysqld]
port                            =       3306
socket                          =       /tmp/mysql.sock
server-id                       =       1
old_passwords                   =       1
max_connections                 =       200
pid-file                        =       /archive/mysql/mysqld.pid
basedir                         =       /opt/mysql
datadir                         =       /archive/mysql

skip-name-resolve

key_buffer                      =       16K
max_allowed_packet              =       1M
table_cache                     =       512
sort_buffer_size                =       64K
read_buffer_size                =       256K
read_rnd_buffer_size            =       256K
net_buffer_length               =       2K
thread_stack                    =       64K

#innodb_fast_shutdown           = 2

log-bin                         =       /archive/logs/mysqld-bin
#log                             =       /archive/logs/mysqld.log
log-err                         =       /archive/logs/mysqld-err.log
long_query_time                 =       3
log_long_format
log-slow-queries                =       /archive/logs/mysqld-slow.log


innodb_data_home_dir            =       /archive/mysql/
innodb_data_file_path           =       ibdata1:1000M:autoextend
innodb_log_group_home_dir       =       /archive/logs/
innodb_buffer_pool_size         =       2G
innodb_additional_mem_pool_siz  =       256M
innodb_log_file_size            =       5M
innodb_log_buffer_size          =       8M
innodb_flush_log_at_trx_commit  =       1
innodb_lock_wait_timeout        =       50
innodb_file_per_table

[mysql]
no-auto-rehash

[isamchk]
key_buffer = 512M
sort_buffer_size = 512M
read_buffer = 8M
write_buffer = 8M

[myisamchk]
key_buffer = 512M
sort_buffer_size = 512M
read_buffer = 8M
write_buffer = 8M

枫影谁用了

innodb_buffer_pool_size 改成1024M.。呵呵

枫影谁用了

你的是32位的OS吧。我以前也遇过这样的问题。

或1800M试下可以，其它错误信息里有写公式出来。

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 63214 K
bytes of memory

yejr

innodb_buffer_pool_size         =       2G
innodb_additional_mem_pool_siz  =       256M

调低这2个先

akflanker

原帖由 枫影谁用了 于 2008-7-15 11:58 发表
你的是32位的OS吧。我以前也遇过这样的问题。

或1800M试下可以，其它错误信息里有写公式出来。

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_ ...

现在是不重启了，但是现在dump数据库的时候就报

mysqldump: Got error: 1033: Incorrect information in file: './mm/account.frm' when using LOCK TABLES


是不是数据已经损坏了？这种问题有办法修复吗？

枫影谁用了

原帖由 akflanker 于 2008-7-15 12:52 发表



现在是不重启了，但是现在dump数据库的时候就报

mysqldump: Got error: 1033: Incorrect information in file: './mm/account.frm' when using LOCK TABLES


是不是数据已经损坏了？这种问题有办法 ...

是MYISAM?

check table 看看。

akflanker

原帖由 枫影谁用了 于 2008-7-15 12:58 发表


是MYISAM?

check table 看看。

Innodb

枫影谁用了

原帖由 akflanker 于 2008-7-15 12:59 发表




Innodb

你这个帐号是root帐号吗？