Page 1 of 1

MySQL Couldn't be found [SOLVED]

PostPosted: 06. January 2012 02:49
by seablue711
I'm having the problem, used xampp and running windows 7. Apache starts with the xampp control panel, but I had to manually start the filezilla service (yep had to pull the rip-cord just like an old-fashioned lawn-mower lol) and the mysql had an error message that it couldn't be found, when I tried to do the same thing. So I guess it's just the ghost of mysql that's haunting my computer, and not the real thing? Not sure what to do. Trying to teach myself php and I need this stuff to be up and running. Any help out there is greatly appreciated thank you very much!!! PS You know it has that error message when I try to start it in the service "ERROR: MySQL service not started (-1) whatever that means, then when I try to start it in the windows services menu it says 'Error 2: file not found'


120105 19:26:20 [Note] Plugin 'FEDERATED' is disabled.
120105 19:26:20 InnoDB: The InnoDB memory heap is disabled
120105 19:26:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120105 19:26:20 InnoDB: Compressed tables use zlib 1.2.3
120105 19:26:20 InnoDB: Initializing buffer pool, size = 16.0M
120105 19:26:20 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist:
InnoDB: a new database to be created!
120105 19:26:20 InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
120105 19:26:20 InnoDB: Log file C:\xampp\mysql\data\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
120105 19:26:20 InnoDB: Log file C:\xampp\mysql\data\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
120105 19:26:21 InnoDB: Waiting for the background threads to start
120105 19:26:22 InnoDB: 1.1.8 started; log sequence number 0
120105 19:26:22 [Note] Event Scheduler: Loaded 0 events
120105 19:26:22 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)

Re: MySQL Couldn't be found

PostPosted: 06. January 2012 03:15
by Sharley
Always try and include the exact error messages when hunting for support. ;)

There are error.log files you can look at.

\xampp\apache\logs\error.log
\xampp\mysql\data\mysql_error.log and *.err files the latter can be dragged into an open text editor for reading.

BTW any particular reason you are using an old XAMPP version?

MySQL vs. Mystery Problem: 0/1

PostPosted: 06. January 2012 03:17
by seablue711
Please see below the contents of the error log as I copied and pasted, the contents of which I have no clue how to interpret. When I first installed the XAMPP and turned it on, MySQL along with Apache and Filezilla was apparently running. Then it stopped unexpectedly, and now refuses to work at all. Haven't the foggiest what has happened as I have not installed, deleted, changed, or reset anything during the time after the 'working' period. If you've any information regarding this situation (MySQL not started (-1) and "error 2:file not found" when attempting to start from windows services), it is greatly appreciated. If not, thanks for reading just the same.

120105 19:26:20 [Note] Plugin 'FEDERATED' is disabled.
120105 19:26:20 InnoDB: The InnoDB memory heap is disabled
120105 19:26:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120105 19:26:20 InnoDB: Compressed tables use zlib 1.2.3
120105 19:26:20 InnoDB: Initializing buffer pool, size = 16.0M
120105 19:26:20 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist:
InnoDB: a new database to be created!
120105 19:26:20 InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
120105 19:26:20 InnoDB: Log file C:\xampp\mysql\data\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
120105 19:26:20 InnoDB: Log file C:\xampp\mysql\data\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
120105 19:26:21 InnoDB: Waiting for the background threads to start
120105 19:26:22 InnoDB: 1.1.8 started; log sequence number 0
120105 19:26:22 [Note] Event Scheduler: Loaded 0 events
120105 19:26:22 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)

Re: MySQL Couldn't be found

PostPosted: 06. January 2012 03:29
by Sharley
The log file's last entry is saying that MySQL is ready for connection and I don't see any errors.

In the Control Panel try removing the tick in the Svc check box then answer yes to uninstall the Windows service.

If you are successful then you should able to click on MySQL Start to have it showing a green running.

Re: MySQL Couldn't be found

PostPosted: 06. January 2012 05:19
by seablue711
Did as you suggested and though it didn't seem to change anything, after uninstalling and reinstalling xampp about four times, now it's running just fine. Thank you :) very much!!

Re: MySQL Couldn't be found

PostPosted: 06. January 2012 05:25
by Sharley
If it happens again then try a different installation method by following these instructions:
viewtopic.php?p=179699#p179699

Often the installer included in XAMPP has issues with some Windows versions and is to be replaced in the next release.

Good luck. :)

I will close this topic and mark it solved.