Page 1 of 1

MySQL wont start after restart.

PostPosted: 08. March 2012 17:32
by chmorin
There was a topic below that had similar symptoms that was resolved, but it was marked as solved so I figured I'd start a new topic. I start MySQL for the first time, change the root password, and restart the service. After this restart, MySQL does not stay on anymore.

My log file contains:

Code: Select all
120308  9:16:56 [Note] Plugin 'FEDERATED' is disabled.
120308  9:16:56 InnoDB: The InnoDB memory heap is disabled
120308  9:16:56 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120308  9:16:56 InnoDB: Compressed tables use zlib 1.2.3
120308  9:16:56 InnoDB: Initializing buffer pool, size = 16.0M
120308  9:16:56 InnoDB: Completed initialization of buffer pool
120308  9:16:56 InnoDB: highest supported file format is Barracuda.
120308  9:16:57  InnoDB: Waiting for the background threads to start
120308  9:16:58 InnoDB: 1.1.8 started; log sequence number 1595675
120308  9:16:58 [ERROR] C:\xampp\mysql\bin\mysqld.exe: unknown option '--skip-locking'
120308  9:16:58 [ERROR] Aborting


Judging from the previous topic, I assume that I need to remove the '--skip-locking' option from mysqld.exe. However, I'm not sure how to do that. Can anyone help me with the process, google is not yielding any results.

Re: MySQL wont start after restart.

PostPosted: 08. March 2012 19:51
by chmorin
Okay, I found where you can comment 'skip-locking' in my.ini, however MySQL still will not start. Now this is the log:

Code: Select all
120308 12:50:22 [Note]
120308 12:51:33 [Note] Plugin 'FEDERATED' is disabled.
120308 12:51:33 InnoDB: The InnoDB memory heap is disabled
120308 12:51:33 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120308 12:51:33 InnoDB: Compressed tables use zlib 1.2.3
120308 12:51:33 InnoDB: Initializing buffer pool, size = 16.0M
120308 12:51:33 InnoDB: Completed initialization of buffer pool
120308 12:51:33 InnoDB: highest supported file format is Barracuda.
120308 12:51:34  InnoDB: Waiting for the background threads to start
120308 12:51:35 InnoDB: 1.1.8 started; log sequence number 1595675
120308 12:51:35 [ERROR] Aborting

120308 12:51:35  InnoDB: Starting shutdown...
120308 12:51:35  InnoDB: Shutdown completed; log sequence number 1595675
120308 12:51:35 [Note]

Re: MySQL wont start after restart.

PostPosted: 08. March 2012 23:49
by Sharley
In the control Panel remove the ticks in the Svc check boxes and answer yes when asked the question.

You first need to make sure that MySQL and Apache are stopped before attempting to remove the ticks.

When they have been removed successfully, reboot XP and then try again to start Apache and MySQL, but do not tick the Svc boxes.

Setting a password in XAMPP for MySQL and phpMyAdmin is done in the XAMPP Welcome (Admin) page under the Security menu item but the default is no password set (blank password) and this should be left as the default until you know that MySQL will start.

Often in XP a reboot seems to fix some unexplainable issue.

Any reason to install 1.7.5 and not 1.7.7?

BTW you can install the latest Version 3 Control Panel into 1.7.5 and just tested it and it seems to work just fine - the download post can be found in the link below my signature.
Simply extract all the files from the CPv3 folder in to the xampp installation folder and overwrite when asked - do not extract the CPv3 folder complete, only extract it's content.
Then right click the exe file to run as administrator and to create a shortcut to the desktop for example, for easier access.

Make sure that you have exited all other control panel versions before starting this latest version.

This version 3 (XCPv3) control panel has many new features including a much more detailed log window and a button to easily access the log files to help with troubleshooting start and running issues.