Error with MySQL

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Error with MySQL

Postby Frag » 29. May 2015 21:30

From 2 days I have a problem with XAMPP, and exactly with MySQL, pops up this error:

Code: Select all
22:00:44  [main]    XAMPP Installation Directory: "d:\xampp\"
22:00:44  [main]    Checking for prerequisites
22:00:45  [main]    All prerequisites found
22:00:45  [main]    Initializing Modules
22:00:45  [Apache]    XAMPP Apache is already running on port 80
22:00:45  [Apache]    XAMPP Apache is already running on port 443
22:00:45  [main]    Starting Check-Timer
22:00:45  [main]    Control Panel Ready



22:00:46  [mysql]    Attempting to start MySQL app...
22:00:47  [mysql]    Status change detected: running
22:00:48  [mysql]    Status change detected: stopped
22:00:48  [mysql]    Error: MySQL shutdown unexpectedly.
22:00:48  [mysql]    This may be due to a blocked port, missing dependencies,
22:00:48  [mysql]    improper privileges, a crash, or a shutdown by another method.
22:00:48  [mysql]    Press the Logs button to view error logs and check
22:00:48  [mysql]    the Windows Event Viewer for more clues
22:00:48  [mysql]    If you need more help, copy and post this
22:00:48  [mysql]    entire log window on the forums
Frag
 
Posts: 6
Joined: 27. May 2015 18:49
Operating System: Win 8.1

Re: Error with MySQL

Postby Frag » 29. May 2015 22:28

mysql_error.log

Code: Select all
2015-05-29 21:57:11 9592 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 21:57:11 1b80 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.
2015-05-29 21:57:11 9592 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 21:57:11 9592 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 21:57:11 9592 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 21:57:11 9592 [Note] InnoDB: Memory barrier is not used
2015-05-29 21:57:11 9592 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 21:57:11 9592 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 21:57:11 9592 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 21:57:11 9592 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 21:57:11 9592 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 21:57:11 9592 [Note] InnoDB: 128 rollback segment(s) are active.
2015-05-29 21:57:11 9592 [Note] InnoDB: Waiting for purge to start
2015-05-29 21:57:11 9592 [Note] InnoDB: 5.6.24 started; log sequence number 1665234
2015-05-29 21:57:11 9592 [Note] Server hostname (bind-address): '*'; port: 3306
2015-05-29 21:57:11 9592 [Note] IPv6 is available.
2015-05-29 21:57:11 9592 [Note]   - '::' resolves to '::';
2015-05-29 21:57:11 9592 [Note] Server socket created on IP: '::'.
2015-05-29 21:58:17 5220 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 21:58:17 648 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.
2015-05-29 21:58:17 5220 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 21:58:17 5220 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 21:58:17 5220 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 21:58:17 5220 [Note] InnoDB: Memory barrier is not used
2015-05-29 21:58:17 5220 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 21:58:17 5220 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 21:58:17 5220 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 21:58:17 5220 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 21:58:17 5220 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 21:58:17 5220 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 21:58:17 5220 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 21:58:17 5220 [Note] InnoDB: Starting crash recovery.
2015-05-29 21:58:17 5220 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 21:58:17 5220 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.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.
2015-05-29 21:58:19 3344 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 21:58:19 23b4 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.
2015-05-29 21:58:19 3344 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 21:58:19 3344 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 21:58:19 3344 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 21:58:19 3344 [Note] InnoDB: Memory barrier is not used
2015-05-29 21:58:19 3344 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 21:58:19 3344 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 21:58:19 3344 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 21:58:19 3344 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 21:58:19 3344 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 21:58:19 3344 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 21:58:19 3344 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 21:58:19 3344 [Note] InnoDB: Starting crash recovery.
2015-05-29 21:58:19 3344 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 21:58:19 3344 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.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.
2015-05-29 21:58:53 10684 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 21:58:53 6cc 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.
2015-05-29 21:58:53 10684 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 21:58:53 10684 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 21:58:53 10684 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 21:58:53 10684 [Note] InnoDB: Memory barrier is not used
2015-05-29 21:58:53 10684 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 21:58:53 10684 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 21:58:53 10684 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 21:58:53 10684 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 21:58:53 10684 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 21:58:53 10684 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 21:58:53 10684 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 21:58:53 10684 [Note] InnoDB: Starting crash recovery.
2015-05-29 21:58:53 10684 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 21:58:53 10684 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.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.
2015-05-29 22:00:47 9956 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 22:00:47 3c4 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.
2015-05-29 22:00:47 9956 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 22:00:47 9956 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 22:00:47 9956 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 22:00:47 9956 [Note] InnoDB: Memory barrier is not used
2015-05-29 22:00:47 9956 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 22:00:47 9956 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 22:00:47 9956 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 22:00:47 9956 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 22:00:47 9956 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 22:00:47 9956 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 22:00:47 9956 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 22:00:47 9956 [Note] InnoDB: Starting crash recovery.
2015-05-29 22:00:47 9956 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 22:00:47 9956 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.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.
2015-05-29 22:26:17 5168 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 22:26:17 15d4 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.
2015-05-29 22:26:17 5168 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 22:26:17 5168 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 22:26:17 5168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 22:26:17 5168 [Note] InnoDB: Memory barrier is not used
2015-05-29 22:26:17 5168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 22:26:17 5168 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 22:26:17 5168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 22:26:17 5168 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 22:26:17 5168 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 22:26:17 5168 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 22:26:17 5168 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 22:26:17 5168 [Note] InnoDB: Starting crash recovery.
2015-05-29 22:26:17 5168 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 22:26:17 5168 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.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.
2015-05-29 22:36:29 4048 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 22:36:29 c10 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.
2015-05-29 22:36:29 4048 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 22:36:29 4048 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 22:36:29 4048 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 22:36:29 4048 [Note] InnoDB: Memory barrier is not used
2015-05-29 22:36:29 4048 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 22:36:29 4048 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 22:36:29 4048 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 22:36:29 4048 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 22:36:29 4048 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 22:36:29 4048 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 22:36:29 4048 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 22:36:29 4048 [Note] InnoDB: Starting crash recovery.
2015-05-29 22:36:29 4048 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 22:36:29 4048 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.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.
Frag
 
Posts: 6
Joined: 27. May 2015 18:49
Operating System: Win 8.1

Re: Error with MySQL

Postby mark.mcdonald » 29. May 2015 22:44

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.
mark.mcdonald
 
Posts: 160
Joined: 13. March 2015 15:48
Location: Edmonton
Operating System: Windows Server 2012 R2

Re: Error with MySQL

Postby Frag » 07. June 2015 13:39

More info to fix?

1 open the file - where it is?
I found only the mysql folder, I have not found a folder mysqld or file my.cnf
Frag
 
Posts: 6
Joined: 27. May 2015 18:49
Operating System: Win 8.1

Re: Error with MySQL

Postby Frag » 07. June 2015 16:16

OK, I fix this :)

I copied the files XAMPP renewal, I removed the old database and works!
Frag
 
Posts: 6
Joined: 27. May 2015 18:49
Operating System: Win 8.1


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 75 guests