 | | | -none- | -none- 2007-10-03 - By Ofer Inbar
Back
We have MySQL 5.0.27 running on about 10 different RedHat EL4 boxes,
all from the same RPMs. Every night we run mysqladmin flush-logs from
crontab (as well as some other things) on most of these servers.
One on server, mysqld is dying with signal 11 every single night right
during the mysqladmin flush-logs command. None of the others ever do that.
This is repeatable. It happens every night.
We're investigating possible causes, but in the meantime I'm also
curious if anyone else on this list has run into something similar
and has some suggestions.
Here's the backtrace portion of the error log from the most recent crash:
| 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=0x45394f78, backtrace may not be correct.
| Stack range sanity check OK, backtrace follows:
| 0x5f737400746f6f72
| New value of fp=0x1874230 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
| Trying to get some variables.
| Some pointers may be invalid and cause the dump to abort...
| thd->query at (nil) is invalid pointer
| thd->thread_id=12310
-- Cos
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=mysql@(protected)
|
|
|