Don't know if this would be of any help. I copied it from the error.log -/var/log/mysql/error.log:
100815 19:28:45 InnoDB: Started; log sequence number 1 637983031 InnoDB: Starting in background the rollback of uncommitted transactions InnoDB: Cleaning up trx with id 0 1738733 100815 19:28:45 InnoDB: Rollback of non-prepared transactions completed 100815 19:28:45 [Note] Event Scheduler: Loaded 0 events 100815 19:28:45 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.41-3ubuntu12.6' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) 100815 19:28:46 InnoDB: Assertion failure in thread 2905140080 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3314 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.1/en/forcing-recovery.html InnoDB: about forcing recovery. 100815 19:28:46 - 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 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 345919 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... stack_bottom = (nil) thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x2d) [0x7635ad] /usr/sbin/mysqld(handle_segfault+0x494) [0x42f3d4] [0x12d400] /lib/tls/i686/cmov/libc.so.6(abort+0x182) [0xb27a82] /usr/sbin/mysqld(fseg_free_step_not_header+0x243) [0x6527c3] /usr/sbin/mysqld(+0x4f8b20) [0x6c0b20] /usr/sbin/mysqld(+0x4f9003) [0x6c1003] /usr/sbin/mysqld(trx_purge_fetch_next_rec+0x28c) [0x6c134c] /usr/sbin/mysqld(row_purge_step+0x42) [0x6a1252] /usr/sbin/mysqld(que_run_threads+0x5b0) [0x68caf0] /usr/sbin/mysqld(trx_purge+0x375) [0x6bf0a5] /usr/sbin/mysqld(srv_master_thread+0xf80) [0x6b5c90] /lib/tls/i686/cmov/libpthread.so.0(+0x596e) [0xf7b96e] /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xbc7a4e] 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. This sequence of error is repeated about every two minutes. -- package mysql-server-5.1 5.1.41-3ubuntu12.3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/617678 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
