[mythtv-users] MySQL borked

Phill Edwards philledwards at gmail.com
Fri May 24 23:37:25 UTC 2013


Sorry for the long post here...
I had a power outage and ever since I've been unable to start the
MySQL daemon on my MythBuntu box. I had these errors in
/var/log/mysql/error.log:

130524 20:07:43 [Note] Plugin 'FEDERATED' is disabled.
130524 20:07:43 InnoDB: The InnoDB memory heap is disabled
130524 20:07:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130524 20:07:43 InnoDB: Compressed tables use zlib 1.2.3.4
130524 20:07:43 InnoDB: Initializing buffer pool, size = 128.0M
130524 20:07:43 InnoDB: Completed initialization of buffer pool
130524 20:07:43 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130524 20:07:43 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...
130524 20:07:43 InnoDB: Waiting for the background threads to start
130524 20:07:44 InnoDB: 5.5.31 started; log sequence number 72354077
130524 20:07:44 InnoDB: Assertion failure in thread 140690101622528 in
file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >=
FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
nnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >=
FIL_PAGE_DATAInnoDB: 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/...-recovery.html
InnoDB: about forcing recovery.
10:07:44 UTC - 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=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=100
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 =
4945524 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 = 0 thread_stack 0x30000
130524 20:07:44 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130524 20:07:44 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130524 20:07:44 [Note] Server socket created on IP: '0.0.0.0'.
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7ff50f30a7b9]
/usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7ff50f1d08f3]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7ff50df1dcb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7ff50d589425]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7ff50d58cb8b]
/usr/sbin/mysqld(+0x5b4dba)[0x7ff50f369dba]
/usr/sbin/mysqld(+0x5b55a5)[0x7ff50f36a5a5]
/usr/sbin/mysqld(+0x67b5af)[0x7ff50f4305af]
/usr/sbin/mysqld(+0x671b05)[0x7ff50f426b05]
/usr/sbin/mysqld(+0x5b747e)[0x7ff50f36c47e]
/usr/sbin/mysqld(+0x5a835c)[0x7ff50f35d35c]
/usr/sbin/mysqld(+0x5ac793)[0x7ff50f361793]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7ff50df15e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff50d646ccd]
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.


I think MySQL got corrupted when the power outage occurred. So I took
a backup of the data using SELECT INTO OUTFILE. Then I uninstalled
mysql-server using dpkg so it didn't also remove mythtv-backend and
reinstalled mysql-server. But the MySQL daemon still won't start and
now there's no messages in /var/log/mysql and I just see this in
/var/log/syslog when I sttempt to start it:

May 25 09:18:10 mbe kernel: [   65.926805] init: mythtv-backend main
process (2634) terminated with status 130
May 25 09:18:10 mbe kernel: [   65.926862] init: mythtv-backend
respawning too fast, stopped
May 25 09:19:17 mbe kernel: [  133.451116] init: mysql main process
(2695) terminated with status 1
May 25 09:19:17 mbe kernel: [  133.451176] init: mysql main process
ended, respawning
May 25 09:19:18 mbe kernel: [  134.364194] init: mysql post-start
process (2696) terminated with status 1
May 25 09:19:19 mbe kernel: [  135.499248] init: mysql main process
(2746) terminated with status 1
May 25 09:19:19 mbe kernel: [  135.499310] init: mysql main process
ended, respawning
May 25 09:19:20 mbe kernel: [  136.439777] init: mysql post-start
process (2747) terminated with status 1
May 25 09:19:21 mbe kernel: [  137.572966] init: mysql main process
(2797) terminated with status 1
May 25 09:19:21 mbe kernel: [  137.573029] init: mysql respawning too
fast, stopped
May 25 09:30:00 mbe kernel: [  775.813977] init: mysql main process
(3663) terminated with status 1
May 25 09:30:00 mbe kernel: [  775.814039] init: mysql main process
ended, respawning
May 25 09:30:00 mbe kernel: [  776.743367] init: mysql post-start
process (3664) terminated with status 1
May 25 09:30:02 mbe kernel: [  777.892491] init: mysql main process
(3714) terminated with status 1
May 25 09:30:02 mbe kernel: [  777.892573] init: mysql main process
ended, respawning
May 25 09:30:03 mbe kernel: [  778.829413] init: mysql post-start
process (3715) terminated with status 1
May 25 09:30:04 mbe kernel: [  779.931853] init: mysql main process
(3765) terminated with status 1
May 25 09:30:04 mbe kernel: [  779.931915] init: mysql respawning too
fast, stopped


Short of trashing the machine and restoring from a backup (which is a
couple of months old), does anyone know how I can fix this? I thought
reinstalling mysql-server would solve it for sure, but as it hasn't
I'm a bit stuck.


More information about the mythtv-users mailing list