Cannot start MySQL, need help

Alles, was MariaDB und MySQL betrifft, kann hier besprochen werden.

Cannot start MySQL, need help

Postby HansenDesign » 09. October 2013 14:54

Hello,
I am running Win Vista Ultimate 32bit.
XAMPP 1.8.3-1
Apache 2.4.4
MySQL 5.6.11
PHP 5.5.3

Error log shows:
Code: Select all
2013-10-09 15:43:30 6572 [Note] Plugin 'FEDERATED' is disabled.
2013-10-09 15:43:30 f30 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-10-09 15:43:30 6572 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-09 15:43:30 6572 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-09 15:43:30 6572 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-09 15:43:30 6572 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-09 15:43:30 6572 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-09 15:43:30 6572 [Note] InnoDB: Completed initialization of buffer pool
2013-10-09 15:43:30 6572 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-09 15:43:30 6572 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2934894 in the ib_logfiles!
2013-10-09 15:43:30 6572 [Note] InnoDB: Database was not shutdown normally!
2013-10-09 15:43:30 6572 [Note] InnoDB: Starting crash recovery.
2013-10-09 15:43:30 6572 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-09 15:43:30 6572 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress_johann/wp_terms which uses space ID: 3 at filepath: .\wordpress_johann\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress_johann\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.


Using it to test Wordpress-sites.
I do not want to have to reinstall Wordpress or MySQL, so deleting ibdata1 is no solution for me.

Anything I can do?

EDIT: Would it help, and if yes, how, to install XAMPP 1.8.2-1 like described here http://community.apachefriends.org/f/viewtopic.php?f=16&t=60831#p227718 ?
HansenDesign
 
Posts: 2
Joined: 09. October 2013 13:02
Operating System: Windows Vista Ultimate

Re: Cannot start MySQL, need help

Postby Nobbie » 09. October 2013 16:30

From http://bugs.mysql.com/bug.php?id=67595

[27 Nov 2012 8:39] Sunny Bains

This is a duplicate of bug#67179. Just different side effect. The Windows installer apparently copied the .ibd files around and that caused the problem. The ones in data/mysql. If you want to recover your files you will have to do the following:

1. Delete the data/mysql/*.ibd files and the corresponding .frm files for the .ibd files
2. Start the server with --skip-slave-start
3. You should be able to access and backup your data


Do not delete ibdata1 (from data folder), but data/mysql/*.idb etc. (see Item "1." above).
Nobbie
 
Posts: 8770
Joined: 09. March 2008 13:04

Re: Cannot start MySQL, need help

Postby HansenDesign » 09. October 2013 16:45

Thanks, Nobbie!
Works like a charm!

As many people are having similar issues, maybe this threat and/or your solution should move to a place where most people looking for help will see it?

This threat is closed, ty.
HansenDesign
 
Posts: 2
Joined: 09. October 2013 13:02
Operating System: Windows Vista Ultimate

Re: Cannot start MySQL, need help

Postby trek4000 » 07. November 2013 12:07

I have a problem in accessing mysql server, this is the log its giving me.
2013-11-07 12:18:30 6496 [Note] Plugin 'FEDERATED' is disabled.
2013-11-07 12:18:30 1c54 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-11-07 12:18:30 6496 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-07 12:18:30 6496 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-07 12:18:30 6496 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-07 12:18:30 6496 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-07 12:18:30 6496 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-07 12:18:30 6496 [Note] InnoDB: Completed initialization of buffer pool
2013-11-07 12:18:30 6496 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-11-07 12:18:30 6496 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-11-07 12:18:30 6496 [Note] InnoDB: Database physically writes the file full: wait...
2013-11-07 12:18:31 6496 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-11-07 12:18:31 6496 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-11-07 12:18:31 6496 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-11-07 12:18:31 6496 [Warning] InnoDB: New log files created, LSN=45781
2013-11-07 12:18:31 6496 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-11-07 12:18:31 6496 [Note] InnoDB: Doublewrite buffer created
2013-11-07 12:18:33 6496 [Note] InnoDB: 128 rollback segment(s) are active.
2013-11-07 12:18:33 6496 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-11-07 12:18:33 6496 [Note] InnoDB: Foreign key constraint system tables created
2013-11-07 12:18:33 6496 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-11-07 12:18:33 6496 [Note] InnoDB: Tablespace and datafile system tables created.
2013-11-07 12:18:33 6496 [Note] InnoDB: Waiting for purge to start
2013-11-07 12:18:33 6496 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-11-07 12:18:33 6496 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: f4e22771-4795-11e3-95a8-7e3878386b31.
2013-11-07 12:18:33 6496 [Note] Server hostname (bind-address): '*'; port: 3306
2013-11-07 12:18:33 6496 [Note] IPv6 is available.
2013-11-07 12:18:33 6496 [Note] - '::' resolves to '::';
2013-11-07 12:18:33 6496 [Note] Server socket created on IP: '::'.
2013-11-07 12:18:33 6496 [ERROR] Can't start server: Bind on TCP/IP port: No such file or directory
2013-11-07 12:18:33 6496 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2013-11-07 12:18:33 6496 [ERROR] Aborting
trek4000
 
Posts: 1
Joined: 07. November 2013 11:47
Operating System: windows 7 Professional

kann mysql auch nicht starten ... trotz mehrfachem neustart

Postby koepenick33 » 18. November 2013 23:33

Hallo zusammen,

ich nutze win 7 ultimate und xampp 1.8.2-2 ... leider bekomme ich trotzneuinstallation und rechnerneustart immer die gleiche Meldung im Log:

131118 22:36:23 [Note] Plugin 'FEDERATED' is disabled.
131118 22:36:23 InnoDB: The InnoDB memory heap is disabled
131118 22:36:24 InnoDB: Mutexes and rw_locks use Windows interlocked functions
131118 22:36:24 InnoDB: Compressed tables use zlib 1.2.3
131118 22:36:24 InnoDB: Initializing buffer pool, size = 16.0M
131118 22:36:24 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!
131118 22:36:24 InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
131118 22:36:24 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...
131118 22:36:25 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
131118 22:36:26 InnoDB: Waiting for the background threads to start
131118 22:36:27 InnoDB: 5.5.32 started; log sequence number 0
131118 22:36:27 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
131118 22:36:27 [Note] - '0.0.0.0' resolves to '0.0.0.0';
131118 22:36:27 [Note] Server socket created on IP: '0.0.0.0'.
131118 22:36:27 [ERROR] Can't start server: Bind on TCP/IP port: No such file or directory
131118 22:36:27 [ERROR] Do you already have another mysqld server running on port: 3306 ?
131118 22:36:27 [ERROR] Aborting

131118 22:36:27 InnoDB: Starting shutdown...
131118 22:36:28 InnoDB: Shutdown completed; log sequence number 1595675
131118 22:36:28 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

kann mir da einer bitte einen Tip geben, wie ich dies behoben bekomme ?

Möchte dringend das cms der firma papoo in xampp integrieren, aber auch da bekomme ich keine verbindung zur datenbank.

Vielen Dank bereits an dieser stelle.
koepenick33
 
Posts: 1
Joined: 18. November 2013 23:20
Operating System: windows 7 ultimate

Re: kann mysql auch nicht starten ... trotz mehrfachem neust

Postby Nobbie » 19. November 2013 12:38

koepenick33 wrote:kann mir da einer bitte einen Tip geben, wie ich dies behoben bekomme ?


??

Hast Du nicht die vorhergehenden Beiträge hier gelesen? Im 2. Beitrag (auch von mir) steht die vollständige Lösung. Wobei auch möglich ist, dass bereits eine andere MySQL Installation läuft (oder der Port 3306 von irgendeiner Anwendung geblockt wird).
Nobbie
 
Posts: 8770
Joined: 09. March 2008 13:04

Re: Cannot start MySQL, need help

Postby zeroline » 20. May 2015 14:23

this maybe a noob question, but what does the step 2 mean?

"2. Start the server with --skip-slave-start"

could you please explain the step? thanks
zeroline
 
Posts: 1
Joined: 20. May 2015 14:19
Operating System: Windows 7 ultimate x64

Re: Cannot start MySQL, need help

Postby Nobbie » 20. May 2015 19:04

Each and every "program" is an executable file on the disk, usually with an *.exe extension. And each of these executables may be started with command line paramaters, This is very very basic Windows Knowlegde.

And the executable for MySQL Server is called "mysqld.exe", you will find it in the bin folder. And you can start each executable in different ways, one of these is simply typing in the full command in a Shell (CMD.EXE). And there you can pass command line parameters behind the program name.

And --skip-slave-start is a known paramater to mysqld.exe, all together it looks like this in a terminal:

mysqld --skip-slave-start

All in all still very basic WIndows Knowledge. I recommend a Windows Tutorial or similar.
Nobbie
 
Posts: 8770
Joined: 09. March 2008 13:04


Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 2 guests