Skip to main content

MySQL stop to work - Help

fcbinfo
Hi there. The mysql shows working, but the websites can't access databases. I look in the folder, the data is there, but no access. When I try to go for phpmyadmin, over the whm with root password, the phpmyadmin ask for password and on cpanel for users too, it ask for password. Error file has 64mb, hard to open. Can someone help with this problem? Thanks.

Comments

3 comments

Date Votes
  • fcbinfo
    The last from error log. 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)[0x83f1d63] /usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x82be334] [0x1ee400] /lib/libc.so.6(abort+0x17a)[0x6913aa] /usr/sbin/mysqld[0x84ae4e8] /usr/sbin/mysqld[0x84aea82] /usr/sbin/mysqld[0x858a999] /usr/sbin/mysqld[0x857e830] /usr/sbin/mysqld[0x84acfce] /usr/sbin/mysqld[0x849f2c6] /lib/libpthread.so.0[0x804a49] /lib/libc.so.6(clone+0x5e)[0x747aae] 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. 131111 13:31:17 mysqld_safe Number of processes running now: 0 131111 13:31:17 mysqld_safe mysqld restarted 131111 13:31:17 [Note] Plugin 'FEDERATED' is disabled. 131111 13:31:17 InnoDB: The InnoDB memory heap is disabled 131111 13:31:17 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 131111 13:31:17 InnoDB: Compressed tables use zlib 1.2.3 131111 13:31:17 InnoDB: Using Linux native AIO 131111 13:31:17 InnoDB: Initializing buffer pool, size = 128.0M 131111 13:31:17 InnoDB: Completed initialization of buffer pool 131111 13:31:17 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 1932460779 131111 13:31:17 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... InnoDB: Doing recovery: scanned up to log sequence number 1932465700 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 1B69900 131111 13:31:18 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Cleaning up trx with id 1B67D73 131111 13:31:18 InnoDB: Waiting for the background threads to start 131111 13:31:19 InnoDB: 5.5.32 started; log sequence number 1932465700 131111 13:31:19 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 131111 13:31:19 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 131111 13:31:19 [Note] Server socket created on IP: '0.0.0.0'. 131111 13:31:19 InnoDB: Error: page 231 log sequence number 1932513594 InnoDB: is in the future! Current system log sequence number 1932465700. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: for more information. 131111 13:31:19 InnoDB: Error: page 230 log sequence number 1932498004 InnoDB: is in the future! Current system log sequence number 1932465700. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: for more information. 131111 13:31:19 [Note] Event Scheduler: Loaded 0 events 131111 13:31:19 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 131111 13:31:19 InnoDB: Assertion failure in thread 2804165488 in file trx0purge.c line 840 InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no 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. 15:31:19 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=8388608 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 = 337912 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)[0x83f1d63] /usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x82be334] [0xcba400] /lib/libc.so.6(abort+0x17a)[0x6913aa] /usr/sbin/mysqld[0x84ae4e8] /usr/sbin/mysqld[0x84aea82] /usr/sbin/mysqld[0x858a999] /usr/sbin/mysqld[0x857e830] /usr/sbin/mysqld[0x84acfce] /usr/sbin/mysqld[0x849f2c6] /lib/libpthread.so.0[0x804a49] /lib/libc.so.6(clone+0x5e)[0x747aae] 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. 131111 13:31:19 mysqld_safe Number of processes running now: 0 131111 13:31:19 mysqld_safe mysqld restarted 131111 13:31:19 [Note] Plugin 'FEDERATED' is disabled. 131111 13:31:19 InnoDB: The InnoDB memory heap is disabled 131111 13:31:19 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 131111 13:31:19 InnoDB: Compressed tables use zlib 1.2.3 131111 13:31:19 InnoDB: Using Linux native AIO 131111 13:31:19 InnoDB: Initializing buffer pool, size = 128.0M 131111 13:31:19 InnoDB: Completed initialization of buffer pool 131111 13:31:19 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 1932460779 131111 13:31:19 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... InnoDB: Doing recovery: scanned up to log sequence number 1932465700 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 1B69900 131111 13:31:20 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Cleaning up trx with id 1B67D73 131111 13:31:20 InnoDB: Waiting for the background threads to start 131111 13:31:21 InnoDB: 5.5.32 started; log sequence number 1932465700 131111 13:31:21 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 131111 13:31:21 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 131111 13:31:21 [Note] Server socket created on IP: '0.0.0.0'. 131111 13:31:21 InnoDB: Error: page 231 log sequence number 1932513594 InnoDB: is in the future! Current system log sequence number 1932465700. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: for more information. 131111 13:31:21 InnoDB: Error: page 230 log sequence number 1932498004 InnoDB: is in the future! Current system log sequence number 1932465700. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: for more information. 131111 13:31:21 [Note] Event Scheduler: Loaded 0 events 131111 13:31:21 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 131111 13:31:21 InnoDB: Assertion failure in thread 2804165488 in file trx0purge.c line 840 InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no 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. 15:31:21 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=8388608 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 = 337912 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)[0x83f1d63] /usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x82be334] [0x5fe400] /lib/libc.so.6(abort+0x17a)[0x6913aa] /usr/sbin/mysqld[0x84ae4e8] /usr/sbin/mysqld[0x84aea82] /usr/sbin/mysqld[0x858a999] /usr/sbin/mysqld[0x857e830] /usr/sbin/mysqld[0x84acfce] /usr/sbin/mysqld[0x849f2c6] /lib/libpthread.so.0[0x804a49] /lib/libc.so.6(clone+0x5e)[0x747aae] 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. 131111 13:31:21 mysqld_safe Number of processes running now: 0 131111 13:31:21 mysqld_safe mysqld restarted 131111 13:31:21 [Note] Plugin 'FEDERATED' is disabled. 131111 13:31:21 InnoDB: The InnoDB memory heap is disabled 131111 13:31:21 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 131111 13:31:21 InnoDB: Compressed tables use zlib 1.2.3 131111 13:31:21 InnoDB: Using Linux native AIO 131111 13:31:21 InnoDB: Initializing buffer pool, size = 128.0M 131111 13:31:21 InnoDB: Completed initialization of buffer pool 131111 13:31:22 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 1932460779 131111 13:31:22 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... InnoDB: Doing recovery: scanned up to log sequence number 1932465700 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 1B69900 131111 13:31:22 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Cleaning up trx with id 1B67D73 131111 13:31:22 InnoDB: Waiting for the background threads to start
    0
  • fcbinfo
    Fixed with this option on my.cnf innodb_force_recovery = 4 Anyway, working only with this this line, if i remove this, stop to work. =/
    0
  • cPanelMichael
    Hello :) This indicates InnoDB corruption. MySQL documents InnoDB troubleshooting at: [url=http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html]MySQL :: MySQL 5.5 Reference Manual :: 14.3.20 InnoDB Troubleshooting Please note that disabling InnoDB may allow MySQL to run, but it's going to disable any tables that utilize InnoDB. Thank you.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post