Description:
Falcon crashes on mysqld startup with the error
""070207 11:48:02 [Note] Recovering after a
crash using tc.log peter mysqld got signal 11;"
etc.
(There was a crash earlier, it will take a
long time to try to reproduce it.)
If I start mysqld with --skip-innodb, no problem.
If I start mysqld with --log-bin, no problem.
If I start mysqld after removing the file
/usr/local/mysql/var/tc.log, no problem.
Guilhem Bichot suggested changing
storage/falcon/ha_falcon.h
to say "define XA_ENABLED". Unfortunately,
that did not help.
There is probably a connection with
Bug #25835 Falcon: assertion on startup
which is now closed.
I am attaching the 'tc.log' file.
I can send the contents of all the datadir,
it's a 247MB zip file.
ChangeSet@1.2424, 2007-02-05 18:16:49-06:00
How to repeat:
linux:/home/pgulutzan/mysql-5.1-falcon # /usr/local/mysql/libexec/mysqld --user=root --skip-networking
070207 12:44:50 InnoDB: Started; log sequence number 0 6205981
070207 12:44:50 [Note] Recovering after a crash using tc.log
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=0
read_buffer_size=131072
max_used_connections=0
max_connections=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 328570 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 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...
Cannot determine thread, fp=0x7fffff859100, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x6a157c
0x760aef
0x76110b
0x6a39b9
0x6a8a6c
0x2aaaab1545aa
New value of fp=0x2aaaaabc0c60 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.
