Problem after switching back to MySQL from MariaDB

jazz1611

Well-Known Member
Jun 5, 2012
82
0
56
cPanel Access Level
Root Administrator
Hi,

I have problem with other server when replace from MariaDB to MySQL. I trying import database .sql on phpmyadmin and get error:

A mistake!
Bad request.
Got error -1 from storage engine (256)

Help me resolved it. Please.
 

cPanelMichael

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

I moved this post into it's own thread because it's a different issue than the original thread you posted it to.

Please check the MySQL error log (/var/lib/mysql/$hostname.err to see if there is any output when this error message appears. It's possible you have some custom entries in your /etc/my.cnf file that are preventing the upload of the database.

Thank you.
 

jazz1611

Well-Known Member
Jun 5, 2012
82
0
56
cPanel Access Level
Root Administrator
Current my.cnf on server

[mysqld]
local-infile=0
innodb_force_recovery=6
innodb_file_per_table=1

datadir=/var/lib/mysql
tmp_table_size=50M
max_heap_table_size=50M
query_cache_limit=50M
query_cache_size=50M
query_cache_type=1
max_user_connections=45
max_connections=150
innodb_buffer_pool_size = 500M

collation_server=utf8_unicode_ci
character_set_server=utf8
character_set_client=utf8

delayed_insert_timeout=40

interactive_timeout=10
wait_timeout=60
connect_timeout=2
thread_cache_size=128
key_buffer=50M
join_buffer_size=4M
max_connect_errors=20
max_allowed_packet=16M
table_cache=5000
sort_buffer_size=256K
read_buffer_size=128K
read_rnd_buffer_size=8M
myisam_sort_buffer_size=64M
server-id=1

open_files_limit=50000
[mysql.server]
user=mysql

[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/lib/mysql/mysql.pid

[mysqldump]
quick
max_allowed_packet=16M

[mysql]
no-auto-rehash
I deleted error before and restart mysql again and see error below:

130718 01:49:09 mysqld_safe mysqld from pid file /var/lib/mysql/serv2.hostjp.net.pid ended
130718 01:49:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130718 1:49:10 [Warning] /usr/sbin/mysqld: ignoring option '--character-set-client-handshake' due to invalid value 'utf8'
130718 1:49:10 [Note] Plugin 'FEDERATED' is disabled.
130718 1:49:10 InnoDB: The InnoDB memory heap is disabled
130718 1:49:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130718 1:49:10 InnoDB: Compressed tables use zlib 1.2.3
130718 1:49:10 InnoDB: Using Linux native AIO
130718 1:49:10 InnoDB: Initializing buffer pool, size = 500.0M
130718 1:49:10 InnoDB: Completed initialization of buffer pool
130718 1:49:10 InnoDB: highest supported file format is Barracuda.
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
130718 1:49:10 InnoDB: Waiting for the background threads to start
130718 1:49:11 InnoDB: 5.5.32 started; log sequence number 0
130718 1:49:11 InnoDB: !!! innodb_force_recovery is set to 6 !!!
130718 1:49:11 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130718 1:49:11 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130718 1:49:11 [Note] Server socket created on IP: '0.0.0.0'.
130718 1:49:11 [Note] Event Scheduler: Loaded 0 events
130718 1:49:11 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
130718 1:49:13 InnoDB: error: space object of table 'waplx_lx/wp_options',
InnoDB: space id 2554 did not exist in memory. Retrying an open.
130718 1:49:13 InnoDB: Warning: allocated tablespace 2554, old maximum was 0
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
130718 1:49:13 InnoDB: error: space object of table 'waplx_lx/wp_postmeta',
InnoDB: space id 2555 did not exist in memory. Retrying an open.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,203
363
The following variable in your /etc/my.cnf file is not designed to be a permanent entry:

Code:
innodb_force_recovery=6
You will need to remove this line, restart MySQL, and see if there are any additional errors in your MySQL error log.

Thank you.
 

jazz1611

Well-Known Member
Jun 5, 2012
82
0
56
cPanel Access Level
Root Administrator
I removed and restarting it failed. I checked error log see:

InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 14.3.7.2 Forcing InnoDB Recovery
InnoDB: for more information.
00000500000001000000000000000000000000000005874eca4a463e3a362e27210400c8150902130718 3:39:29 InnoDB: Error: page 3025 log sequence number 4442349
InnoDB: is in the future! Current system log sequence number 1855078.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 14.3.7.2 Forcing InnoDB Recovery
InnoDB: for more information.
6d617967696174675f646c67642f6a6f735f6b756e656e615f7365130718 3:39:29 InnoDB: Error: page 3026 log sequence number 4446273
InnoDB: is in the future! Current system log sequence number 1855078.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 14.3.7.2 Forcing InnoDB Recovery
InnoDB: for more information.
7373696f6e73000000db637f2b000001ab10eb00000000000024078000000500000001000000000000000000000000000005884dc949453d39352d26200000d015095f6d617967696174675f646c6$
InnoDB: End of page dump
130718 3:39:29 InnoDB: Page checksum 874520237, prior-to-4.0.14-form checksum 1286876798
InnoDB: stored checksum 3828712581, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 1781613, low 4 bytes of lsn at page end 1781613
InnoDB: Page number (if stored to page already) 3598,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an index page where index id is 1
InnoDB: (index "CLUST_IND" of table "SYS_TABLES")
130718 3:39:29 InnoDB: Assertion failure in thread 139898749892352 in file page0page.ic line 745
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to MySQL Bugs.
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: MySQL :: MySQL 5.5 Reference Manual :: 14.3.7.2 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
20:39:29 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 = 338536 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+0x35)[0x7a62e5]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x682144]
/lib64/libpthread.so.0(+0xf500)[0x7f3cc70d9500]
/lib64/libc.so.6(gsignal+0x35)[0x7f3cc62a18a5]
/lib64/libc.so.6(abort+0x175)[0x7f3cc62a3085]
/usr/sbin/mysqld[0x90257c]
/usr/sbin/mysqld[0x904b00]
/usr/sbin/mysqld[0x905c9f]
/usr/sbin/mysqld[0x8f021c]
/usr/sbin/mysqld[0x8f2031]
/usr/sbin/mysqld[0x88ff38]
/usr/sbin/mysqld[0x8bb258]
/usr/sbin/mysqld[0x84aae0]
/lib64/libpthread.so.0(+0x7851)[0x7f3cc70d1851]
/lib64/libc.so.6(clone+0x6d)[0x7f3cc63578ed]
The manual page at MySQL :: MySQL 5.6 Reference Manual :: C.5.4.2 What to Do If MySQL Keeps Crashing contains
information that should help you find out what is causing the crash.
130718 03:39:29 mysqld_safe mysqld from pid file /var/lib/mysql/serv2.hostjp.net.pid ended
Can i open ticket for us resolved it? Your Request id is: 4296617.
 
Last edited:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,203
363
The error message indicates that InnoDB is still corrupted. Database recovery falls outside our scope of support, so a support ticket may not be helpful in this case. You may want to consult with a qualified system administrator if you are unable to repair InnoDB using traditional methods.

Thank you.