Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

mysql database really screwed up

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
Widgeteye
Posts: 10
Joined: 2017-02-10 19:49

mysql database really screwed up

#1 Post by Widgeteye »

When I try to start mysqld I get the following errors in the log file:

170314 19:04:24 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170314 19:04:24 [Note] Plugin 'FEDERATED' is disabled.
170314 19:04:24 InnoDB: The InnoDB memory heap is disabled
170314 19:04:24 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170314 19:04:24 InnoDB: Compressed tables use zlib 1.2.8
170314 19:04:24 InnoDB: Using Linux native AIO
170314 19:04:24 InnoDB: Initializing buffer pool, size = 128.0M
170314 19:04:24 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
170314 19:04:24 [ERROR] Plugin 'InnoDB' init function returned error.
170314 19:04:24 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
170314 19:04:24 [ERROR] Unknown/unsupported storage engine: InnoDB
170314 19:04:24 [ERROR] Aborting
170314 19:04:24 [Note] mysqld: Shutdown complete

This all started with my trying to install mythtv. Everything went downhill from there.

Is there any way to repair mysql or am I going to need to reinstall Debian??

Thanks
ARRRGG

User avatar
GarryRicketson
Posts: 5644
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: mysql database really screwed up

#2 Post by GarryRicketson »

by Widgeteye »Is there any way to repair mysql or am I going to need to reinstall Debian??
Yes there are ways to repair mysql,..
NO , you shouldn't have to reinstall Debian, but that may depend on
other details, that you have not mentioned.



In this recent thread, http://forums.debian.net/viewtopic.php? ... ql#p637821
It is discussed on how to remove and purge, MYSQL,...

The details you have not mentioned,...
What version of Debian ?
What version of MYSQL ?
How did you install this "mythtv" ? and where did you get it ?
It is not in the Debian repositories,..
https://www.mythtv.org/wiki/Installing_MythTV_on_Debian
Introduction

This page will describe how to install on Debian, using the package manager. Currently no MythTV-approved repository exists so the packages need to be built from source. This is an easy process using a script that can be checked out from git.
What else have you done to your system, ? These are things
that may determine if you need to reinstall it or not.

Some times just doing a search using the error message is very use full,
example:
Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release
This (below ) was the first hit, of many
https://support.plesk.com/hc/en-us/arti ... re-release
The solution is shown , in this (above) link,..all you need to do is read it.
So what version of MYSQL ?, is very relevant.
------
Next error:

Code: Select all

[ERROR] Plugin 'InnoDB' init function returned error. 
This error is a little more complicated, and not easy for me to explain, but there is some info and details on it in some search results,...
One last example:
mysql error Plugin 'InnoDB' init function returned error
There are several good results, but the 2nd hit, goes into a lot on troubleshooting MYSQL, like which logs to look at, etc:
https://spin.atomicobject.com/2011/05/0 ... ge-engine/

That should give you enough example on how to look up the info on
the other 2 errors:

Code: Select all

MYSQL error Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
===
MYSQL error  Unknown/unsupported storage engine: InnoDB 
Just copy/paste the messages into a search engine.

Reinstalling Debian will not solve the mysql errors, these can be solved
by configuring your mysql data base correctly.

It can be a rather tedious process, but yes it can be repaired, or configured correctly, if the admin reads and follows instructions carefully.

However, with 'mythtv", being from somewhere, who knows where, and if it was compiled correctly, that is to say there may be other problems
that go beyond just the MYSQL errors.

So any way, hope that helps.

Post Reply