[Bug 295293] [NEW] InnoDB: Assertion failure in thread...
Thomas C.
thomas.creutz at gmx.de
Fri Nov 7 19:25:03 GMT 2008
Public bug reported:
I got a error with my mysql-database Server... but there told me, that it is not compiled with -fomit-frame-pointer?
ok.. tried also innodb_force_recovery = 4 in my.cnf, but is dosnt help.
I run mysql with gdb an make a backtrace.. hope that we can find what's
wrong...
Nov 7 19:59:45 nb mysqld_safe[18307]: started
Nov 7 19:59:45 nb mysqld[18310]: InnoDB: Log scan progressed past the checkpoint lsn 0 1752709
Nov 7 19:59:45 nb mysqld[18310]: 081107 19:59:45 InnoDB: Database was not shut down normally!
Nov 7 19:59:45 nb mysqld[18310]: InnoDB: Starting crash recovery.
Nov 7 19:59:45 nb mysqld[18310]: InnoDB: Reading tablespace information from the .ibd files...
Nov 7 19:59:45 nb mysqld[18310]: InnoDB: Restoring possible half-written data pages from the doublewrite
Nov 7 19:59:45 nb mysqld[18310]: InnoDB: buffer...
Nov 7 19:59:59 nb /etc/init.d/mysql[18776]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Nov 7 19:59:59 nb /etc/init.d/mysql[18776]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Nov 7 19:59:59 nb /etc/init.d/mysql[18776]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Nov 7 19:59:59 nb /etc/init.d/mysql[18776]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Nov 7 19:59:59 nb /etc/init.d/mysql[18776]:
Nov 7 20:00:11 nb mysqld[18310]: InnoDB: Error: tried to read 1048576 bytes at offset 0 1048576.
Nov 7 20:00:11 nb mysqld[18310]: InnoDB: Was only able to read 8192.
Nov 7 20:00:11 nb mysqld[18310]: InnoDB: Fatal error: cannot read from file. OS error number 17.
Nov 7 20:00:11 nb mysqld[18310]: 081107 20:00:11InnoDB: Assertion failure in thread 140476003809008 in file os0file.c line 2211
Nov 7 20:00:11 nb mysqld[18310]: InnoDB: We intentionally generate a memory trap.
Nov 7 20:00:11 nb mysqld[18310]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Nov 7 20:00:11 nb mysqld[18310]: InnoDB: If you get repeated assertion failures or crashes, even
Nov 7 20:00:11 nb mysqld[18310]: InnoDB: immediately after the mysqld startup, there may be
Nov 7 20:00:11 nb mysqld[18310]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Nov 7 20:00:11 nb mysqld[18310]: InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
Nov 7 20:00:11 nb mysqld[18310]: InnoDB: about forcing recovery.
Nov 7 20:00:11 nb mysqld[18310]: 081107 20:00:11 - mysqld got signal 11 ;
Nov 7 20:00:11 nb mysqld[18310]: This could be because you hit a bug. It is also possible that this binary
Nov 7 20:00:11 nb mysqld[18310]: or one of the libraries it was linked against is corrupt, improperly built,
Nov 7 20:00:11 nb mysqld[18310]: or misconfigured. This error can also be caused by malfunctioning hardware.
Nov 7 20:00:11 nb mysqld[18310]: We will try our best to scrape up some info that will hopefully help diagnose
Nov 7 20:00:11 nb mysqld[18310]: the problem, but since we have already crashed, something is definitely wrong
Nov 7 20:00:11 nb mysqld[18310]: and this may fail.
Nov 7 20:00:11 nb mysqld[18310]:
Nov 7 20:00:11 nb mysqld[18310]: key_buffer_size=0
Nov 7 20:00:11 nb mysqld[18310]: read_buffer_size=131072
Nov 7 20:00:11 nb mysqld[18310]: max_used_connections=0
Nov 7 20:00:11 nb mysqld[18310]: max_connections=100
Nov 7 20:00:11 nb mysqld[18310]: threads_connected=0
Nov 7 20:00:11 nb mysqld[18310]: It is possible that mysqld could use up to
Nov 7 20:00:11 nb mysqld[18310]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K
Nov 7 20:00:11 nb mysqld[18310]: bytes of memory
Nov 7 20:00:11 nb mysqld[18310]: Hope that's ok; if not, decrease some variables in the equation.
Nov 7 20:00:11 nb mysqld[18310]:
Nov 7 20:00:11 nb mysqld[18310]: thd=(nil)
Nov 7 20:00:11 nb mysqld[18310]: Attempting backtrace. You can use the following information to find out
Nov 7 20:00:11 nb mysqld[18310]: where mysqld died. If you see no messages after this, something went
Nov 7 20:00:11 nb mysqld[18310]: terribly wrong...
Nov 7 20:00:11 nb mysqld[18310]: frame pointer is NULL, did you compile with
Nov 7 20:00:11 nb mysqld[18310]: -fomit-frame-pointer? Aborting backtrace!
Nov 7 20:00:11 nb mysqld[18310]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Nov 7 20:00:11 nb mysqld[18310]: information that should help you find out what is causing the crash.
Nov 7 20:00:11 nb mysqld_safe[19047]: ended
root at nb:/~# gdb mysqld
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
(gdb) r --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock
Starting program: /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x7fc59321c6f0 (LWP 12621)]
[New Thread 0x41efc950 (LWP 12627)]
[Thread 0x41efc950 (LWP 12627) exited]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x41efc950 (LWP 12628)]
[New Thread 0x426fd950 (LWP 12629)]
[New Thread 0x40da1950 (LWP 12630)]
[New Thread 0x42efe950 (LWP 12631)]
InnoDB: Log scan progressed past the checkpoint lsn 0 1752709
081107 20:19: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: Error: tried to read 1048576 bytes at offset 0 1048576.
InnoDB: Was only able to read 8192.
InnoDB: Fatal error: cannot read from file. OS error number 17.
081107 20:19:49InnoDB: Assertion failure in thread 140486553749232 in file os0file.c line 2211
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fc59321c6f0 (LWP 12621)]
0x0000000000803ff7 in os_file_read ()
(gdb) bt
#0 0x0000000000803ff7 in os_file_read ()
#1 0x00000000007d0b5e in fil_io ()
#2 0x000000000078f241 in trx_sys_doublewrite_init_or_restore_pages ()
#3 0x00000000007b8cf2 in recv_scan_log_recs ()
#4 0x00000000007b96f6 in ?? ()
#5 0x00000000007b9cb6 in recv_recovery_from_checkpoint_start ()
#6 0x0000000000714d43 in innobase_start_or_create_for_mysql ()
#7 0x0000000000695e64 in innobase_init ()
#8 0x000000000068bbfa in ha_init ()
#9 0x00000000005d6085 in ?? ()
#10 0x00000000005d82aa in main ()
(gdb)
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: fglrx
Package: mysql-server 5.0.67-0ubuntu6
PackageArchitecture: all
ProcEnviron:
LANGUAGE=de
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: mysql-dfsg-5.0
Uname: Linux 2.6.27-7-generic x86_64
** Affects: mysql-dfsg-5.0 (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug
--
InnoDB: Assertion failure in thread...
https://bugs.launchpad.net/bugs/295293
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
More information about the Ubuntu-server-bugs
mailing list