luis

Well-Known Member
Sep 3, 2001
50
0
306
Today I have a new problem with a cpanel server, mysql won't start, in the host.err file there is this error:

Code:
130708 17:02:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130708 17:02:12 [Note] Plugin 'FEDERATED' is disabled.
130708 17:02:12  InnoDB: Initializing buffer pool, size = 8.0M
130708 17:02:12  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 43 167215116
130708 17:02:12  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 43 167220889
22:02:13 UTC - mysqld got signal 11 ;
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=8384512
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 = 338374 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x85ad4e]
/usr/sbin/mysqld(handle_fatal_signal+0x41a)[0x6b608a]
/lib64/libpthread.so.0(+0xf500)[0x7fbf08737500]
/usr/sbin/mysqld(page_cur_insert_rec_low+0x67e)[0x7aa86e]
/usr/sbin/mysqld(page_cur_parse_insert_rec+0x4c2)[0x7aaf72]
/usr/sbin/mysqld[0x79929d]
/usr/sbin/mysqld(recv_recover_page+0x31f)[0x79ac4f]
/usr/sbin/mysqld(buf_page_io_complete+0x4f8)[0x75eee8]
/usr/sbin/mysqld[0x763b40]
/usr/sbin/mysqld(buf_read_page+0x21d)[0x76446d]
/usr/sbin/mysqld(buf_page_get_gen+0x373)[0x75e043]
/usr/sbin/mysqld(ibuf_data_init_for_space+0x1d1)[0x789481]
/usr/sbin/mysqld(fil_ibuf_init_at_db_start+0x27)[0x774877]
/usr/sbin/mysqld(dict_boot+0x87c)[0x7f972c]
/usr/sbin/mysqld(innobase_start_or_create_for_mysql+0xfea)[0x7d714a]
/usr/sbin/mysqld[0x74320a]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x31)[0x6aa031]
/usr/sbin/mysqld[0x7253ad]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x644)[0x727494]
/usr/sbin/mysqld[0x5d62c6]
/usr/sbin/mysqld(main+0x1c6)[0x5d8836]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7fbf07ac6cdd]
/usr/sbin/mysqld[0x529c89]
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.
130708 17:02:13 mysqld_safe mysqld from pid file /var/lib/mysql/elipse.elipsis.com.mx.pid ended
Any clues?

Also, what is the new method to completely reinstall mysql since /scripts/mysqlup is now unusable?

Thanks in advance
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,205
363
Hello :)

It looks like there may be InnoDB corruption. The following document may be helpful to you:

Forcing InnoDB Recovery - MySQL 5.5

Reinstalling MySQL requires that you manually remove the MySQL RPMs and then utilize the following command:

Code:
/usr/local/cpanel/scripts/check_cpanel_rpms --fix
Note that reinstalling MySQL will not repair InnoDB.

Thank you.
 

fcbinfo

Well-Known Member
Dec 10, 2006
111
3
168
cPanel Access Level
Root Administrator
I have the same problem. But don't work.

There is anyway to complete remove and reinstall mysql. I have my databases backup-ed.

I Just need to complete delete and resinstall mysql. Maybe will need to reinstall OS?

Thanks.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,205
363
There is a dated thread that may be of help to you at:

MySQL InnoDB Crash Recovery

It was intended for a completely different issue, but the steps there may be helpful if you are not able to consult with a qualified system administrator and your only other option is reinstalling the OS.

Thank you.