Attachment 3497 Details for Bug 8984 – /usr/share/mysql/mysql-test/var/log/mysqld.1.err

/usr/share/mysql/mysql-test/var/log/mysqld.1.err

mysqld.1.err (text/plain), 2.47 KB, created by Dave Hodgins on 2013-02-07 23:11:09 CET

(hide)

Description:

Filename:

MIME Type:

Creator: Dave Hodgins

Created: 2013-02-07 23:11:09 CET

Size: 2.47 KB

patch

obsolete

>CURRENT_TEST: federated.federated_partition
>130207 16:51:21 InnoDB: The InnoDB memory heap is disabled
>130207 16:51:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
>130207 16:51:21 InnoDB: Compressed tables use zlib 1.2.6
>130207 16:51:21 InnoDB: Using Linux native AIO
>130207 16:51:21  InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
>InnoDB: Warning: io_setup() attempt 1 failed.
>InnoDB: Warning: io_setup() attempt 2 failed.
>InnoDB: Warning: io_setup() attempt 3 failed.
>InnoDB: Warning: io_setup() attempt 4 failed.
>InnoDB: Warning: io_setup() attempt 5 failed.
>130207 16:51:23  InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
>InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
>130207 16:51:23 InnoDB: Initializing buffer pool, size = 8.0M
>130207 16:51:23 InnoDB: Completed initialization of buffer pool
>InnoDB: The first specified data file ./ibdata1 did not exist:
>InnoDB: a new database to be created!
>130207 16:51:23  InnoDB: Setting file ./ibdata1 size to 10 MB
>InnoDB: Database physically writes the file full: wait...
>130207 16:51:23 [ERROR] 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.
>
>To report this bug, see http://kb.askmonty.org/en/reporting-bugs
>
>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.
>
>Server version: 5.5.25-MariaDB-log
>key_buffer_size=1048576
>read_buffer_size=131072
>max_used_connections=0
>max_threads=153
>thread_count=0
>It is possible that mysqld could use up to 
>key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61113 K  bytes of memory
>Hope that's ok; if not, decrease some variables in the equation.
>
>Thread pointer: 0x0x0
>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 = 0x0 thread_stack 0x48000
>??:0(??)[0x876c79a]
>??:0(??)[0x831bf0c]
>??:0(??)[0xffffe400]
>??:0(??)[0x8646936]
>??:0(??)[0x85fd3c1]
>??:0(??)[0x856b7d8]
>??:0(??)[0xb7789a37]
>??:0(??)[0xb732a98e]
>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.
>Writing a core file

CURRENT_TEST: federated.federated_partition
130207 16:51:21 InnoDB: The InnoDB memory heap is disabled
130207 16:51:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130207 16:51:21 InnoDB: Compressed tables use zlib 1.2.6
130207 16:51:21 InnoDB: Using Linux native AIO
130207 16:51:21  InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
130207 16:51:23  InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
130207 16:51:23 InnoDB: Initializing buffer pool, size = 8.0M
130207 16:51:23 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
130207 16:51:23  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
130207 16:51:23 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 5.5.25-MariaDB-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61113 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
??:0(??)[0x876c79a]
??:0(??)[0x831bf0c]
??:0(??)[0xffffe400]
??:0(??)[0x8646936]
??:0(??)[0x85fd3c1]
??:0(??)[0x856b7d8]
??:0(??)[0xb7789a37]
??:0(??)[0xb732a98e]
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.
Writing a core file

Actions: View

Attachments on bug 8984: 3496 | 3497