mysql stop working in xampp 1.8.3 using windows 7

Irgendwelche Probleme mit XAMPP für Windows? Dann ist hier genau der richtige Ort um nachzufragen.

mysql stop working in xampp 1.8.3 using windows 7

Postby anilmp40 » 24. October 2013 06:46

when i restart xampp 1.8.3 and start mysql i found this error
Code: Select all
10:49:41 AM  [mysql]    Error: MySQL shutdown unexpectedly.
10:49:41 AM  [mysql]    This may be due to a blocked port, missing dependencies,
10:49:41 AM  [mysql]    improper privileges, a crash, or a shutdown by another method.
10:49:41 AM  [mysql]    Press the Logs button to view error logs and check
10:49:41 AM  [mysql]    the Windows Event Viewer for more clues
10:49:41 AM  [mysql]    If you need more help, copy and post this
10:49:41 AM  [mysql]    entire log window on the forums

mysql_error.log file shows these errors
Code: Select all
2013-10-24 11:14:48 6460 [Note] Plugin 'FEDERATED' is disabled.
2013-10-24 11:14:48 157c 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-24 11:14:48 6460 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-24 11:14:48 6460 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-24 11:14:48 6460 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-24 11:14:48 6460 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-24 11:14:48 6460 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-24 11:14:48 6460 [Note] InnoDB: Completed initialization of buffer pool
2013-10-24 11:14:48 6460 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-24 11:14:48 6460 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600614 in the ib_logfiles!
2013-10-24 11:14:48 6460 [Note] InnoDB: Database was not shutdown normally!
2013-10-24 11:14:48 6460 [Note] InnoDB: Starting crash recovery.
2013-10-24 11:14:48 6460 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-24 11:14:48 6460 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace 7daysgift/news uses space ID: 13 at filepath: .\7daysgift\news.ibd. Cannot open tablespace 7daysgifts/login which uses space ID: 13 at filepath: .\7daysgifts\login.ibd
InnoDB: Error: could not open single-table tablespace file .\7daysgifts\login.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.

how can i resolve that problem.please help.
User avatar
anilmp40
 
Posts: 1
Joined: 24. October 2013 06:36
Location: India
XAMPP Version: 1.8.3-3
Operating System: windows 7

Re: mysql stop working in xampp 1.8.3 using windows 7

Postby WilliL » 24. October 2013 13:50

have a look to viewtopic.php?f=16&t=66746 may be theres a solution
Willi
WilliL
 
Posts: 628
Joined: 08. January 2010 10:54
XAMPP Version: 5.5.19
Operating System: Win7Home Prem 64 SP1


Return to XAMPP für Windows

Who is online

Users browsing this forum: No registered users and 3 guests