Wednesday, March 08, 2017

Solved "XAMPP: Couldn't start MySQL!"


The error XAMPP: Couldn't start MySQL! seems to be an issue related to one or more corrupt log files; system running Red Hat. It was sorted out by the following steps.

Corrupt log file in MySQL


A review of the error log revealed the following 

170308 19:44:18 mysqld_safe mysqld from pid file /opt/lampp/var/mysql/ip-192-168-2-1.pid ended
170308 19:48:20 mysqld_safe Starting mysqld daemon with databases from /opt/lampp/var/mysql
170308 19:48:20 [Note] Plugin 'FEDERATED' is disabled.
170308 19:48:20 InnoDB: The InnoDB memory heap is disabled
170308 19:48:20 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
170308 19:48:20 InnoDB: Compressed tables use zlib 1.2.3
170308 19:48:20 InnoDB: Initializing buffer pool, size = 512.0M
170308 19:48:20 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file /opt/lampp/var/mysql/ib_logfile0 is of different size 0 5242880 bytes
InnoDB: than specified in the .cnf file 0 134217728 bytes!
170308 19:48:20 [ERROR] Plugin 'InnoDB' init function returned error.
170308 19:48:20 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
170308 19:48:20 [ERROR] Unknown/unsupported storage engine: InnoDB
170308 19:48:20 [ERROR] Aborting

Remove the corrupt log files


Since, the log file is corrupt, we will be removing the log file and try and start the session.

sudo rm /opt/lampp/var/mysql/ib_logfile0
sudo rm /opt/lampp/var/mysql/ib_logfile1

Then, start/restart lampp using 

/opt/lampp/lampp start
[or]
/opt/lampp/lampp restart


MySQL started again!

No comments:

Nature, most benign, most benevolent!

We have this habit of blaming nature for all our ills. Obviously, because man is the most intelligent creature on Earth and cannot go wro...

Copyrighted.com Registered & Protected DWYE-NHTO-NBNH-7FFM