Sponsor:

Server and Web Integrator
Link:
Kloxo-MR logo
6.5.0 or 7.0.0
Click for "How to install"
Donation/Sponsorship:
Kloxo-MR is open-source.
Donate and or Sponsorship always welcome.
Click to:
Click Here
Please login or register. 2017-11-07, 18:31:09

Author Topic: Unknown storage engine 'InnoDB'  (Read 867 times)

0 Members and 1 Guest are viewing this topic.

Offline m7shapan

  • Junior Member
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Unknown storage engine 'InnoDB'
« on: 2016-12-03, 11:36:51 »
Hello
I'm facing this problem when I try to create tables in the database, and I notice that all my database engine is MyISAM ?
any way to help create tables correctly and change the existing tables type to InnoDB

Online MRatWork

  • Administrator
  • The Elite
  • *****
  • Posts: 15,381
  • Karma: +112/-9
  • Gender: Male
    • View Profile
    • MRatWork Forum
Re: Unknown storage engine 'InnoDB'
« Reply #1 on: 2016-12-04, 02:30:23 »
Inform here 'cat /etc/my.cnf; cat /etc/my.cnf.d/server.cnf'.
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

Offline m7shapan

  • Junior Member
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Re: Unknown storage engine 'InnoDB'
« Reply #2 on: 2016-12-04, 19:16:42 »
Code: [Select]
#
# This group is read both both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include all files from the config directory
#
!includedir /etc/my.cnf.d

#
# These groups are read by MariaDB server.
# Use it for options that only the server (but not clients) should see
#
# See the examples of server my.cnf files in /usr/share/mysql/
#

# this is read by the standalone daemon and embedded servers
[server]

# this is only for the mysqld standalone daemon
[mysqld]
performance_schema=on
default-storage-engine=myisam
skip-innodb
#OpenVZ AIO bug fix
innodb_use_native_aio=0

# this is only for embedded server
[embedded]

# This group is only read by MariaDB servers, not by MySQL.
# If you use the same .cnf file for MySQL and MariaDB,
# you can put MariaDB-only options here
[mariadb]

# This group is only read by MariaDB-10.0 servers.
# If you use the same .cnf file for MariaDB of different versions,
# use this group for options that older servers don't understand
[mariadb-10.0]

Online MRatWork

  • Administrator
  • The Elite
  • *****
  • Posts: 15,381
  • Karma: +112/-9
  • Gender: Male
    • View Profile
    • MRatWork Forum
Re: Unknown storage engine 'InnoDB'
« Reply #3 on: 2016-12-04, 19:27:19 »
Change 'skip-innodb' to '#skip-innodb' in '/etc/my.cnf.d/server.cnf' and then restart with 'sh /script/restart-mysql'.
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

Offline fantasymc

  • Junior Member
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Re: Unknown storage engine 'InnoDB'
« Reply #4 on: 2017-06-13, 03:57:12 »
I also have problem same with this subject, i try reboot and run
'sh /script/mysql-convert --engne=myisam' in 2 times process.
below is my.cnf

[mysqld]
skip-innodb
default-storage-engine=myisam
innodb_force_recovery=6
#OpenVZ AIO bug fix
innodb_use_native_aio=0
# Settings user and group are ignored when systemd is used (fedora >= 15).
# If you need to run mysqld under different user or group,
# customize your systemd unit file for mysqld according to the
# instructions in http://fedoraproject.org/wiki/Systemd
user=mysql

datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

# Semisynchronous Replication
# http://dev.mysql.com/doc/refman/5.5/en/replication-semisync.html
# uncomment next line on MASTER
;plugin-load=rpl_semi_sync_master=semisync_master.so
# uncomment next line on SLAVE
;plugin-load=rpl_semi_sync_slave=semisync_slave.so

# Others options for Semisynchronous Replication
;rpl_semi_sync_master_enabled=1
;rpl_semi_sync_master_timeout=10
;rpl_semi_sync_slave_enabled=1

# http://dev.mysql.com/doc/refman/5.5/en/performance-schema.html
;performance_schema


[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

Please give me what should i do to find and fix my problem.

Thanks you.

Online MRatWork

  • Administrator
  • The Elite
  • *****
  • Posts: 15,381
  • Karma: +112/-9
  • Gender: Male
    • View Profile
    • MRatWork Forum
Re: Unknown storage engine 'InnoDB'
« Reply #5 on: 2017-06-13, 11:36:52 »
Change 'skip-innodb' to '#skip-innodb' under '[mysqld]' in /etc/my.cnf. And then 'sh /script/restart-mysql'.
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

Offline fantasymc

  • Junior Member
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Re: Unknown storage engine 'InnoDB'
« Reply #6 on: 2017-06-13, 11:54:52 »
Dear MRatWork,

i already change it to #skip-innodb, and did service mysqld restart, now it show Got error -1 from storage engine.

this is tail -100 /var/log/mysqld.log

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.
170613 16:47:33  InnoDB: Error: page 19561 log sequence number 48165464201
InnoDB: is in the future! Current system log sequence number 9419.
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.
170613 16:47:33  InnoDB: Error: page 19562 log sequence number 48165464216
InnoDB: is in the future! Current system log sequence number 9419.
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.
170613 16:47:33  InnoDB: Error: page 19559 log sequence number 48165464251
InnoDB: is in the future! Current system log sequence number 9419.
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.
170613 16:47:33  InnoDB: Error: page 40019 log sequence number 48166426182
InnoDB: is in the future! Current system log sequence number 9419.
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.
170613 16:47:35  InnoDB: Error: page 19691 log sequence number 31982746099
InnoDB: is in the future! Current system log sequence number 9419.
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.
170613 16:47:35  InnoDB: Error: page 26600 log sequence number 7285548658
InnoDB: is in the future! Current system log sequence number 9419.
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.
170613 16:47:35  InnoDB: Error: page 13284 log sequence number 48120571499
InnoDB: is in the future! Current system log sequence number 9419.
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.
170613 16:47:35  InnoDB: Error: page 26598 log sequence number 30032196393
InnoDB: is in the future! Current system log sequence number 9429.
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.
170613 16:47:37  InnoDB: Error: page 32563 log sequence number 14120
InnoDB: is in the future! Current system log sequence number 9429.
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.
170613 16:47:37  InnoDB: Error: page 15309 log sequence number 15566
InnoDB: is in the future! Current system log sequence number 9429.
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.
170613 16:47:37  InnoDB: Error: page 32191 log sequence number 15566
InnoDB: is in the future! Current system log sequence number 9429.
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.
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.
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.
170613 16:47:39  InnoDB: Error: page 32082 log sequence number 48165406681
InnoDB: is in the future! Current system log sequence number 9429.
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.
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.
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.
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.

If i change to #innodb_force_recovery=1 and did service mysqld restart, it show
MySQL Daemon failed to start.

Online MRatWork

  • Administrator
  • The Elite
  • *****
  • Posts: 15,381
  • Karma: +112/-9
  • Gender: Male
    • View Profile
    • MRatWork Forum
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

Online MRatWork

  • Administrator
  • The Elite
  • *****
  • Posts: 15,381
  • Karma: +112/-9
  • Gender: Male
    • View Profile
    • MRatWork Forum
Re: Unknown storage engine 'InnoDB'
« Reply #8 on: 2017-06-13, 12:18:36 »
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

Offline fantasymc

  • Junior Member
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Re: Unknown storage engine 'InnoDB'
« Reply #9 on: 2017-06-16, 09:46:14 »
Dear MRatWork,

Thanks you for your help but i can't fix my issue, i reload os and re-install Kloxo Mr.

 


MRatWork Affiliates:    BIGRAF(R) Inc.    House of LMAR    EFARgrafix

Page created in 0.036 seconds with 17 queries.

web stats analysis
 
Mirror created by MasterkinG32.CoM