120610 20:27:15 [Note] Plugin 'FEDERATED' is disabled. 120610 20:27:15 InnoDB: The InnoDB memory heap is disabled 120610 20:27:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins 120610 20:27:15 InnoDB: Compressed tables use zlib 1.2.3.4 120610 20:27:15 InnoDB: Initializing buffer pool, size = 128.0M 120610 20:27:15 InnoDB: Completed initialization of buffer pool 120610 20:27:15 InnoDB: highest supported file format is Barracuda. InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 0. InnoDB: You may have to recover from a backup. 120610 20:27:15 InnoDB: Page dump in ascii and hex (16384 bytes): [...] InnoDB: End of page dump 120610 20:27:15 InnoDB: Page checksum 2647458526, prior-to-4.0.14-form checksum 2448222090 InnoDB: stored checksum 3029590750, prior-to-4.0.14-form stored checksum 2448222090 InnoDB: Page lsn 0 44227, low 4 bytes of lsn at page end 44227 InnoDB: Page number (if stored to page already) 0, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a file space header page InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 0. InnoDB: You may have to recover from a backup. InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table. You can use CHECK InnoDB: TABLE to scan your table for corruption. InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. 120610 20:27:15 InnoDB: Assertion failure in thread 3078387456 in file buf0buf.c line 3608 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. 16:27:15 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 = 346063 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)[0x8b9af3] /usr/sbin/mysqld(handle_fatal_signal+0x484)[0x766be4] [0x340400] /usr/sbin/mysqld(+0x583947)[0x9ca947] /usr/sbin/mysqld(+0x584042)[0x9cb042] /usr/sbin/mysqld(+0x5745fa)[0x9bb5fa] /usr/sbin/mysqld(+0x5b2954)[0x9f9954] /usr/sbin/mysqld(+0x53085a)[0x97785a] /usr/sbin/mysqld(+0x4f93d2)[0x9403d2] /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4e)[0x7691de] /usr/sbin/mysqld(+0x1f7c82)[0x63ec82] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0xbc3)[0x642623] /usr/sbin/mysqld(+0x1640ba)[0x5ab0ba] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x672)[0x5aece2] /usr/sbin/mysqld(main+0x27)[0x5a47c7] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xe664d3] 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011220 Title: package mysql-server-5.5 5.5.22-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1011220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
