Skip navigation links

MySQL Forums :: InnoDB :: InnoDB: Failing assertion: page_get_n_recs(page) > 1


Advanced Search

Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1
Posted by: Anton Dischner ()
Date: May 10, 2011 12:57AM

Hi,

yesterday i wrote: no problem. Today one of the test servers crashed.

I poste the complete errlog. Mysql was 5.5.9 and was upgraded to 5.5.11

Server is a SLES 10 SP3 x86/64, 4GB

110307 15:41:02 mysqld_safe Starting mysqld daemon with databases from /raid/mysql
110307 15:41:02 [Note] Plugin 'FEDERATED' is disabled.
110307 15:41:02 InnoDB: The InnoDB memory heap is disabled
110307 15:41:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110307 15:41:02 InnoDB: Compressed tables use zlib 1.2.3
110307 15:41:02 InnoDB: Using Linux native AIO
110307 15:41:02 InnoDB: Initializing buffer pool, size = 1000.0M
110307 15:41:03 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file /raid/mysql/ibdata1 did not exist:
InnoDB: a new database to be created!
110307 15:41:03 InnoDB: Setting file /raid/mysql/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
110307 15:41:03 InnoDB: Log file /raid/mysql/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /raid/mysql/ib_logfile0 size to 1024 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000
110307 15:41:14 InnoDB: Log file /raid/mysql/ib_logfile1 did not exist: new to be created
InnoDB: Setting log file /raid/mysql/ib_logfile1 size to 1024 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
110307 15:41:38 InnoDB: Waiting for the background threads to start
110307 15:41:39 InnoDB: 1.1.5 started; log sequence number 0
110307 15:41:39 [Note] Event Scheduler: Loaded 0 events
110307 15:41:39 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.9-log' socket: '/raid/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
110418 8:51:25 [Note] /usr/sbin/mysqld: Normal shutdown

110418 8:51:25 [Note] Event Scheduler: Purging the queue. 0 events
110418 8:51:27 [Warning] /usr/sbin/mysqld: Forcing close of thread 3 user: 'klch'

110418 8:51:27 InnoDB: Starting shutdown...
110418 8:51:32 InnoDB: Shutdown completed; log sequence number 492679016153
110418 8:51:32 [Note] /usr/sbin/mysqld: Shutdown complete

110418 08:51:32 mysqld_safe mysqld from pid file /raid/mysql/klchsgc.pid ended
110418 09:05:15 mysqld_safe Starting mysqld daemon with databases from /raid/mysql
110418 9:05:15 [Note] Plugin 'FEDERATED' is disabled.
110418 9:05:15 InnoDB: The InnoDB memory heap is disabled
110418 9:05:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110418 9:05:15 InnoDB: Compressed tables use zlib 1.2.3
110418 9:05:15 InnoDB: Using Linux native AIO
110418 9:05:15 InnoDB: Initializing buffer pool, size = 1000.0M
110418 9:05:16 InnoDB: Completed initialization of buffer pool
110418 9:05:16 InnoDB: highest supported file format is Barracuda.
110418 9:05:17 InnoDB: Waiting for the background threads to start
110418 9:05:18 InnoDB: 1.1.6 started; log sequence number 492679016153
110418 9:05:18 [Note] Event Scheduler: Loaded 0 events
110418 9:05:18 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.11-log' socket: '/raid/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
110510 3:02:53 InnoDB: Assertion failure in thread 1115703616 in file /export/home/pb2/build/sb_0-3159149-1301581921.2/rpm/BUILD/mysql-5.5.11/mysql-5.5.11/storage/innobase/ibuf/ibuf0ibuf.c line 4130
InnoDB: Failing assertion: page_get_n_recs(page) > 1
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110510 3:02:53 - mysqld got signal 6 ;
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=8388608
read_buffer_size=131072
max_used_connections=33
max_threads=1001
thread_count=21
connection_count=21
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2197762 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7bcd19]
/usr/sbin/mysqld(handle_segfault+0x37b)[0x4f9f1b]
/lib64/libpthread.so.0[0x2ae185ae6d60]
/lib64/libc.so.6(gsignal+0x35)[0x2ae1861bff45]
/lib64/libc.so.6(abort+0x110)[0x2ae1861c1340]
/usr/sbin/mysqld[0x8ef99a]
/usr/sbin/mysqld[0x8a9c45]
/usr/sbin/mysqld[0x8d88f8]
/usr/sbin/mysqld[0x861170]
/lib64/libpthread.so.0[0x2ae185adf193]
/lib64/libc.so.6(__clone+0x6d)[0x2ae186250dfd]
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.
110510 03:02:53 mysqld_safe Number of processes running now: 0
110510 03:02:53 mysqld_safe mysqld restarted
110510 3:02:54 [Note] Plugin 'FEDERATED' is disabled.
110510 3:02:54 InnoDB: The InnoDB memory heap is disabled
110510 3:02:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110510 3:02:54 InnoDB: Compressed tables use zlib 1.2.3
110510 3:02:54 InnoDB: Using Linux native AIO
110510 3:02:54 InnoDB: Initializing buffer pool, size = 1000.0M
110510 3:02:54 InnoDB: Completed initialization of buffer pool
110510 3:02:54 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 636209887282
110510 3:02:54 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 636212732311
110510 3:02:56 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 110510 3:02:56 InnoDB: Assertion failure in thread 1115703616 in file /export/home/pb2/build/sb_0-3159149-1301581921.2/rpm/BUILD/mysql-5.5.11/mysql-5.5.11/storage/innobase/ibuf/ibuf0ibuf.c line 4130
18 InnoDB: Failing assertion: page_get_n_recs(page) > 1
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110510 3:02:56 - mysqld got signal 6 ;
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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=1001
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2197762 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7bcd19]
/usr/sbin/mysqld(handle_segfault+0x37b)[0x4f9f1b]
/lib64/libpthread.so.0[0x2b8cee345d60]
/lib64/libc.so.6(gsignal+0x35)[0x2b8ceea1ef45]
/lib64/libc.so.6(abort+0x110)[0x2b8ceea20340]
/usr/sbin/mysqld[0x8ef99a]
/usr/sbin/mysqld[0x8a9c45]
/usr/sbin/mysqld[0x8d88f8]
/usr/sbin/mysqld[0x861170]
/lib64/libpthread.so.0[0x2b8cee33e193]
/lib64/libc.so.6(__clone+0x6d)[0x2b8ceeaafdfd]
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.
110510 03:02:56 mysqld_safe mysqld from pid file /raid/mysql/klchsgc.pid ended
110510 06:58:06 mysqld_safe Starting mysqld daemon with databases from /raid/mysql
110510 6:58:06 [Note] Plugin 'FEDERATED' is disabled.
110510 6:58:06 InnoDB: The InnoDB memory heap is disabled
110510 6:58:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110510 6:58:06 InnoDB: Compressed tables use zlib 1.2.3
110510 6:58:06 InnoDB: Using Linux native AIO
110510 6:58:06 InnoDB: Initializing buffer pool, size = 1000.0M
110510 6:58:07 InnoDB: Completed initialization of buffer pool
110510 6:58:07 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 636209887282
110510 6:58:07 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 636212732311
110510 6:58:08 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 110510 6:58:08 InnoDB: Assertion failure in thread 1115703616 in file /export/home/pb2/build/sb_0-3159149-1301581921.2/rpm/BUILD/mysql-5.5.11/mysql-5.5.11/storage/innobase/ibuf/ibuf0ibuf.c line 4130
InnoDB: Failing assertion: page_get_n_recs(page) > 1
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110510 6:58:08 - mysqld got signal 6 ;
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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=1001
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2197762 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7bcd19]
18 /usr/sbin/mysqld(handle_segfault+0x37b)[0x4f9f1b]
/lib64/libpthread.so.0[0x2ba7d2696d60]
/lib64/libc.so.6(gsignal+0x35)[0x2ba7d2d6ff45]
/lib64/libc.so.6(abort+0x110)[0x2ba7d2d71340]
/usr/sbin/mysqld[0x8ef99a]
/usr/sbin/mysqld[0x8a9c45]
/usr/sbin/mysqld[0x8d88f8]
/usr/sbin/mysqld[0x861170]
/lib64/libpthread.so.0[0x2ba7d268f193]
/lib64/libc.so.6(__clone+0x6d)[0x2ba7d2e00dfd]
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.
110510 06:58:08 mysqld_safe mysqld from pid file /raid/mysql/klchsgc.pid ended
110510 06:58:26 mysqld_safe Starting mysqld daemon with databases from /raid/mysql
110510 6:58:26 [Note] Plugin 'FEDERATED' is disabled.
110510 6:58:26 InnoDB: The InnoDB memory heap is disabled
110510 6:58:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110510 6:58:26 InnoDB: Compressed tables use zlib 1.2.3
110510 6:58:26 InnoDB: Using Linux native AIO
110510 6:58:26 InnoDB: Initializing buffer pool, size = 1000.0M
110510 6:58:27 InnoDB: Completed initialization of buffer pool
110510 6:58:27 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 636209887282
110510 6:58:27 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 636212732311
110510 6:58:28 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 110510 6:58:28 InnoDB: Assertion failure in thread 1115703616 in file /export/home/pb2/build/sb_0-3159149-1301581921.2/rpm/BUILD/mysql-5.5.11/mysql-5.5.11/storage/innobase/ibuf/ibuf0ibuf.c line 4130
InnoDB: Failing assertion: page_get_n_recs(page) > 1
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110510 6:58:28 - mysqld got signal 6 ;
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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=1001
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2197762 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 0x40000
18 /usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7bcd19]
/usr/sbin/mysqld(handle_segfault+0x37b)[0x4f9f1b]
/lib64/libpthread.so.0[0x2ba6b99b7d60]
/lib64/libc.so.6(gsignal+0x35)[0x2ba6ba090f45]
/lib64/libc.so.6(abort+0x110)[0x2ba6ba092340]
/usr/sbin/mysqld[0x8ef99a]
/usr/sbin/mysqld[0x8a9c45]
/usr/sbin/mysqld[0x8d88f8]
/usr/sbin/mysqld[0x861170]
/lib64/libpthread.so.0[0x2ba6b99b0193]
/lib64/libc.so.6(__clone+0x6d)[0x2ba6ba121dfd]
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.
110510 06:58:28 mysqld_safe mysqld from pid file /raid/mysql/klchsgc.pid ended

Options: ReplyQuote


Subject Views Written By Posted
InnoDB: Failing assertion: page_get_n_recs(page) > 1 2489 Anton Dischner 01/28/2011 03:00AM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 895 Anton Dischner 01/31/2011 04:05AM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 1146 Nico Schmidt 02/08/2011 01:27PM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 1698 Morten Svan├Žs 02/25/2011 04:29AM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 1210 Anton Dischner 03/07/2011 01:41AM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 1678 Anton Dischner 03/07/2011 08:03AM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 823 Laurent Bigonville 05/09/2011 03:07AM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 697 Anton Dischner 05/09/2011 03:19AM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 924 Anton Dischner 05/10/2011 12:57AM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 1339 Anton Dischner 05/10/2011 02:44AM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 1225 Ger Apeldoorn 05/23/2011 06:46AM
Re: InnoDB: Failing assertion: page_get_n_recs(page) > 1 1488 Anton Dischner 05/23/2011 07:09AM


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.