Description:
Below you'll fing my log for the two latest attempts to start mysql server with the command
safe_mysqld &
031128 18:31:07 mysqld started
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
031128 18:31:16 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
031128 18:31:19 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 30 MB
InnoDB: Database physically writes the file full: wait...
031128 18:31:23 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 30 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
031128 18:31:36 InnoDB: Started
031128 18:31:36 /usr/libexec/mysqld: Can't find file: './mysql/host.frm' (errno: 13)
031128 18:31:36 /usr/libexec/mysqld: Normal shutdown
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=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation
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=0x4002e5f4, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80e43dc
0x400918f8
0x4002eb30
0x80e3697
0x4008c484
0x420df147
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/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/C/r/Crashing.html contains
information that should help you find out what is causing the crash
031128 18:31:39 mysqld ended
031128 19:57:25 mysqld started
031128 19:57:46 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 37082
InnoDB: Doing recovery: scanned up to log sequence number 0 43892
031128 19:57:46 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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
031128 19:57:47 InnoDB: Flushing modified pages from the buffer pool...
031128 19:57:47 InnoDB: Started
031128 19:57:47 /usr/libexec/mysqld: Can't find file: './mysql/host.frm' (errno: 13)
031128 19:57:47 /usr/libexec/mysqld: Normal shutdown
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=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation
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=0x4002e5f4, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80e43dc
0x400918f8
0x4002eb30
0x80e3697
0x4008c484
0x420df147
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/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/C/r/Crashing.html contains
information that should help you find out what is causing the crash
031128 19:57:48 mysqld ended
[papa@localhost papa]$ resolve_stack_dump -s /tmp/mysqld.sym -n /tmp/mysqld.stack
0x80e43dc + 135152604
0x400918f8 + 1074338040
0x4002eb30 + 1073933104
0x80e3697 + 135149207
0x4008c484 + 1074316420
0x420df147 + 1108209991
How to repeat:
safe_mysqld &
