Code: Select all
Setting up mysql-server-5.5 (5.5.31+dfsg-1) ...
130906 12:42:59 [Note] Plugin 'FEDERATED' is disabled.
130906 12:42:59 InnoDB: The InnoDB memory heap is disabled
130906 12:42:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130906 12:42:59 InnoDB: Compressed tables use zlib 1.2.7
130906 12:42:59 InnoDB: Using Linux native AIO
130906 12:42:59 InnoDB: Initializing buffer pool, size = 128.0M
130906 12:42:59 InnoDB: Completed initialization of buffer pool
130906 12:42:59 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!
130906 12:42:59 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...
130906 12:42:59 InnoDB: Assertion failure in thread 3064109376 in file fsp0fsp.c line 2102
InnoDB: Failing assertion: inode
InnoDB: We intentionally generate a memory trap.
InnoDB: 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/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
11:42:59 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=151
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 = 346064 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
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0xb727b673]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0xb711d4d4]
linux-gate.so.1(__kernel_sigreturn+0x0)[0xb6dd2400]
/usr/sbin/mysqld(+0x5bdc81)[0xb73b1c81]
/usr/sbin/mysqld(+0x5caa98)[0xb73bea98]
/usr/sbin/mysqld(+0x59870d)[0xb738c70d]
/usr/sbin/mysqld(+0x544d34)[0xb7338d34]
/usr/sbin/mysqld(+0x508f9c)[0xb72fcf9c]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4e)[0xb711ffee]
/usr/sbin/mysqld(+0x20a4a2)[0xb6ffe4a2]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xb83)[0xb7002bb3]
/usr/sbin/mysqld(+0x170764)[0xb6f64764]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x65a)[0xb6f69e4a]
/usr/sbin/mysqld(main+0x27)[0xb6f5fd67]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xf5)[0xb6a5d8c5]
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.
Job failed. See system journal and 'systemctl status' for details.
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.5 (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
mysql-server depends on mysql-server-5.5; however:
Package mysql-server-5.5 is not configured yet.
dpkg: error processing mysql-server (--configure):
dependency problems - leaving unconfigured
Setting up mysql-client (5.5.31+dfsg-1) ...
Errors were encountered while processing:
mysql-server-5.5
mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
Code: Select all
wux@chauvin:~$ sudo systemctl status mysql.service
mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Fri, 06 Sep 2013 12:43:24 +0100; 22min ago
Process: 1423 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/mysql.service
Sep 06 12:43:10 chauvin mysqld[1786]: Thread pointer: 0x0
Sep 06 12:43:10 chauvin mysqld[1786]: Attempting backtrace. You can use the following information to find out
Sep 06 12:43:10 chauvin mysqld[1786]: where mysqld died. If you see no messages after this, something went
Sep 06 12:43:10 chauvin mysqld[1786]: terribly wrong...
Sep 06 12:43:10 chauvin mysqld[1786]: stack_bottom = 0 thread_stack 0x30000
Sep 06 12:43:10 chauvin mysqld[1786]: /usr/sbin/mysqld(my_print_stacktrace+0x33)[0xb730f673]
Sep 06 12:43:10 chauvin mysqld[1786]: /usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0xb71b14d4]
Sep 06 12:43:10 chauvin mysqld[1786]: linux-gate.so.1(__kernel_sigreturn+0x0)[0xb6e66400]
Sep 06 12:43:10 chauvin mysqld[1786]: /usr/sbin/mysqld(+0x5bdc81)[0xb7445c81]
Sep 06 12:43:10 chauvin mysqld[1786]: /usr/sbin/mysqld(+0x5caa98)[0xb7452a98]
but i wouldn't install it, right now.
had a look at mysqlbugs saw some similar things - no workarounds that i can see.
and i'm not sure how to report a bug
