Search found 1082 matches: InnoDB

Searched query: +InnoDB

Return to advanced search

Re: Error with MySQL

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.
by Frag
29. May 2015 22:28
 
Forum: XAMPP for Windows
Topic: Error with MySQL
Replies: 4
Views: 439

Re: joomla installation stuck

ygwolf wrote:Is this reasonable?

Maybe. If you serach the internet there are two common solutions for this problem:
- increase the max_execution_time limit
- change from InnoDB to MyISAM
Both seem to be plausible.

ygwolf wrote:how do I get to this code?

This is a joomla specific question better been asked at a joomla specific board.

best wishes,
Altrea
by Altrea
25. May 2015 13:39
 
Forum: XAMPP for Windows
Topic: joomla installation stuck
Replies: 4
Views: 171

Re: Recover Locally Hosted Site off Crashed HDD - XAMPP

Micci101 wrote:2015-05-20 10:54:10 2708 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.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.

Have you tried steps 2 or 3?
It's normal for the message regarding UAC to come up. This won't be an issue.
by mark.mcdonald
20. May 2015 15:30
 
Forum: XAMPP for Windows
Topic: Recover Locally Hosted Site off Crashed HDD - XAMPP
Replies: 20
Views: 811

Re: Recover Locally Hosted Site off Crashed HDD - XAMPP

2015-05-20 10:48:47 5920 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 10:48:47 8dc 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-20 10:48:47 5920 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 10:48:47 5920 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 10:48:47 5920 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 10:48:47 5920 [Note] InnoDB: Memory barrier is not used
2015-05-20 10:48:47 5920 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 10:48:47 5920 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 10:48:47 5920 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 10:48:47 5920 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 10:48:47 5920 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 10:48:47 5920 [Note] InnoDB: 128 rollback segment(s) are active.
2015-05-20 10:48:48 5920 [Note] InnoDB: Waiting for purge to start
2015-05-20 10:48:48 5920 [Note] InnoDB: 5.6.21 started; log sequence number 1665234
2015-05-20 10:48:48 5920 [Note] Server hostname (bind-address): '*'; port: 3306
2015-05-20 10:48:48 5920 [Note] IPv6 is available.
2015-05-20 10:48:48 5920 [Note] - '::' resolves to '::';
2015-05-20 10:48:48 5920 [Note] Server socket created on IP: '::'.
2015-05-20 10:54:10 2708 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 10:54:10 3f8 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-20 10:54:10 2708 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 10:54:10 2708 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 10:54:10 2708 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 10:54:10 2708 [Note] InnoDB: Memory barrier is not used
2015-05-20 10:54:10 2708 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 10:54:10 2708 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 10:54:10 2708 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 10:54:10 2708 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 10:54:10 2708 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 10:54:10 2708 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665244 in the ib_logfiles!
2015-05-20 10:54:10 2708 [Note] InnoDB: Database was not shutdown normally!
2015-05-20 10:54:10 2708 [Note] InnoDB: Starting crash recovery.
2015-05-20 10:54:10 2708 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-20 10:54:10 2708 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.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-20 16:05:02 128 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 16:05:02 d48 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-20 16:05:02 128 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 16:05:02 128 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 16:05:02 128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 16:05:02 128 [Note] InnoDB: Memory barrier is not used
2015-05-20 16:05:02 128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 16:05:02 128 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 16:05:02 128 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 16:05:02 128 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 16:05:02 128 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 16:05:02 128 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665244 in the ib_logfiles!
2015-05-20 16:05:02 128 [Note] InnoDB: Database was not shutdown normally!
2015-05-20 16:05:02 128 [Note] InnoDB: Starting crash recovery.
2015-05-20 16:05:02 128 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-20 16:05:02 128 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.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.
by Micci101
20. May 2015 15:06
 
Forum: XAMPP for Windows
Topic: Recover Locally Hosted Site off Crashed HDD - XAMPP
Replies: 20
Views: 811

Errcode: 13 - Permission denied

Dear all,
I have installed XAMPP just now and didnt change any settings.
When I try to start MySQL, it pops out this warning.
Please help.....
That file 'C:\xampp\tmp\ib526E.tmp' actually exists but it said to be not found..

Code: Select all
2015-05-13 14:59:18 2292 [Note] Plugin 'FEDERATED' is disabled.
2015-05-13 14:59:18 eac 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-13 14:59:18 2292 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-13 14:59:18 2292 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-13 14:59:18 2292 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-13 14:59:18 2292 [Note] InnoDB: Memory barrier is not used
2015-05-13 14:59:18 2292 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-13 14:59:18 2292 [Note] InnoDB: Not using CPU crc32 instructions
c:\xampp\mysql\bin\mysqld.exe: File 'C:\xampp\tmp\ib526E.tmp' not found (Errcode: 13 - Permission denied)
2015-05-13 14:59:18 eac  InnoDB: Error: unable to create temporary file; errno: 13
2015-05-13 14:59:18 2292 [ERROR] Plugin 'InnoDB' init function returned error.
2015-05-13 14:59:18 2292 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2015-05-13 14:59:18 2292 [ERROR] Unknown/unsupported storage engine: InnoDB
2015-05-13 14:59:18 2292 [ERROR] Aborting

2015-05-13 14:59:18 2292 [Note] Binlog end
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'partition'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_METRICS'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_CMPMEM'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_CMP'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_LOCKS'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'INNODB_TRX'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'BLACKHOLE'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'ARCHIVE'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'MRG_MYISAM'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'MyISAM'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'MEMORY'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'CSV'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'sha256_password'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'mysql_old_password'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'mysql_native_password'
2015-05-13 14:59:18 2292 [Note] Shutting down plugin 'binlog'
2015-05-13 14:59:18 2292 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete
by windllwing
13. May 2015 08:10
 
Forum: XAMPP for Windows
Topic: Errcode: 13 - Permission denied
Replies: 2
Views: 281

auto-create xampp/tmp directory

in the portable xampp with php 5.5, there is no xampp/tmp Directory.

Thus, switching mysql to innodb, mysql dies upon Startup because it cannot create temporary files.

The ini files specify xampp/tmp, but the Directory just does not exist. Should be created upon installing.

thanks,

Klaus
by opto
13. May 2015 07:43
 
Forum: XAMPP-Wunschzettel
Topic: auto-create xampp/tmp directory
Replies: 0
Views: 122

Can't start mysql or apache

I can't start mysql or apache;
the error is:
20:39:05 [mysql] Status change detected: running
20:39:07 [mysql] Status change detected: stopped
20:39:07 [mysql] Error: MySQL shutdown unexpectedly.
20:39:07 [mysql] This may be due to a blocked port, missing dependencies,
20:39:07 [mysql] improper privileges, a crash, or a shutdown by another method.
20:39:07 [mysql] Press the Logs button to view error logs and check
20:39:07 [mysql] the Windows Event Viewer for more clues
20:39:07 [mysql] If you need more help, copy and post this
20:39:07 [mysql] entire log window on the forums
20:39:18 [Apache] Status change detected: running

detailed description:
2015-05-11 20:34:02 8864 [Note] Plugin 'FEDERATED' is disabled.
2015-05-11 20:34:02 2590 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-11 20:34:02 8864 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-11 20:34:02 8864 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-11 20:34:02 8864 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-11 20:34:02 8864 [Note] InnoDB: Memory barrier is not used
2015-05-11 20:34:02 8864 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-11 20:34:02 8864 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-11 20:34:02 8864 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-11 20:34:02 8864 [Note] InnoDB: Completed initialization of buffer pool
2015-05-11 20:34:02 8864 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-11 20:34:02 8864 [Note] InnoDB: 128 rollback segment(s) are active.
2015-05-11 20:34:02 8864 [Note] InnoDB: Waiting for purge to start
2015-05-11 20:34:02 8864 [Note] InnoDB: 5.6.24 started; log sequence number 1665234
2015-05-11 20:34:02 8864 [Note] Server hostname (bind-address): '*'; port: 3306
2015-05-11 20:34:02 8864 [Note] IPv6 is available.
2015-05-11 20:34:02 8864 [Note] - '::' resolves to '::';
2015-05-11 20:34:02 8864 [Note] Server socket created on IP: '::'.
2015-05-11 20:34:02 8864 [ERROR] Can't start server: Bind on TCP/IP port: No such file or directory
2015-05-11 20:34:02 8864 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2015-05-11 20:34:02 8864 [ERROR] Aborting

2015-05-11 20:34:02 8864 [Note] Binlog end
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'partition'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_METRICS'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_CMPMEM'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_CMP'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_LOCKS'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'INNODB_TRX'
2015-05-11 20:34:02 8864 [Note] Shutting down plugin 'InnoDB'
2015-05-11 20:34:02 8864 [Note] InnoDB: FTS optimize thread exiting.
2015-05-11 20:34:02 8864 [Note] InnoDB: Starting shutdown...
2015-05-11 20:34:04 8864 [Note] InnoDB: Shutdown completed; log sequence number 1665244
2015-05-11 20:34:04 8864 [Note] Shutting down plugin 'BLACKHOLE'
2015-05-11 20:34:04 8864 [Note] Shutting down plugin 'ARCHIVE'
2015-05-11 20:34:04 8864 [Note] Shutting down plugin 'MRG_MYISAM'
2015-05-11 20:34:04 8864 [Note] Shutting down plugin 'MyISAM'
2015-05-11 20:34:04 8864 [Note] Shutting down plugin 'MEMORY'
2015-05-11 20:34:04 8864 [Note] Shutting down plugin 'CSV'
2015-05-11 20:34:04 8864 [Note] Shutting down plugin 'sha256_password'
2015-05-11 20:34:04 8864 [Note] Shutting down plugin 'mysql_old_password'
2015-05-11 20:34:04 8864 [Note] Shutting down plugin 'mysql_native_password'
2015-05-11 20:34:04 8864 [Note] Shutting down plugin 'binlog'
2015-05-11 20:34:04 8864 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

by cuberub
11. May 2015 19:47
 
Forum: XAMPP for Windows
Topic: Can't start mysql or apache
Replies: 3
Views: 511

Error in mysql installation

I have installed Xamp 1.7.2 in windows xp. While trying to start mysql, i am getting following error
#2003 - Can't connect to MySQL server on 'localhost' (10061).

I have checked port configuration and port 3306 is used by SQL only. My error log says:
150502 16:55:18 [Note] Plugin 'FEDERATED' is disabled.
150502 16:55:19 [Note] PrimeBase XT (PBXT) Engine 1.0.08 RC loaded...
150502 16:55:19 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
150502 16:55:24 InnoDB: Started; log sequence number 0 46409
150502 16:55:25 [Note] Event Scheduler: Loaded 0 events
150502 16:55:25 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.1.37' socket: '' port: 3306 Source distribution

Can someone please help me to fix this.

THanks
by prav
02. May 2015 13:18
 
Forum: Apache
Topic: Error in mysql installation
Replies: 0
Views: 152

Error: MySQL shutdown unexpectedly

Hi guys, I just installed the newest version of XAMPP( 5.6.8 ) And MYSQL is not working.

The message I get in XAMPP is as follows:
16:58:59 [mysql] Error: MySQL shutdown unexpectedly.
16:58:59 [mysql] This may be due to a blocked port, missing dependencies,
16:58:59 [mysql] improper privileges, a crash, or a shutdown by another method.
16:58:59 [mysql] Press the Logs button to view error logs and check
16:58:59 [mysql] the Windows Event Viewer for more clues
16:58:59 [mysql] If you need more help, copy and post this
16:58:59 [mysql] entire log window on the forums


And in the mysql_error.log the message is the following:
2015-05-01 16:58:59 12744 [Note] Plugin 'FEDERATED' is disabled.
2015-05-01 16:58:59 239c 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-01 16:58:59 12744 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-01 16:58:59 12744 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-01 16:58:59 12744 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-01 16:58:59 12744 [Note] InnoDB: Memory barrier is not used
2015-05-01 16:58:59 12744 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-01 16:58:59 12744 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-01 16:58:59 12744 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-01 16:58:59 12744 [Note] InnoDB: Completed initialization of buffer pool
2015-05-01 16:58:59 12744 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-01 16:58:59 239c InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-05-01 16:58:59 12744 [ERROR] InnoDB: File E:\xamp\mysql\data\ib_logfile0: 'aio read' returned OS error 187. Cannot continue operation


I appreciate all the help as I don't know how to solve this.
Thanks in advance
by D4ffieduck
01. May 2015 16:12
 
Forum: XAMPP for Windows
Topic: Error: MySQL shutdown unexpectedly
Replies: 2
Views: 288

Re: XAMPP: Innodb error/warning messages in mysql_error.log

TomXampp wrote:Everything executes correctly, and my site runs without a problem. However, the mysql_error.log file contains an InnoDB Warning message

This is a warning, not an error. This is an informational message that lets you know that a certain aspect of mysql has been cut back. 99% of users using XAMPP don't need to worry or do anything with this as this warning is generated with every install of XAMPP. I have not seen this cause an issue yet with any development with xampp.
by mark.mcdonald
27. April 2015 20:04
 
Forum: XAMPP for Windows
Topic: XAMPP: Innodb error/warning messages in mysql_error.log
Replies: 1
Views: 241

XAMPP: Innodb error/warning messages in mysql_error.log

I'm using the current version of XAMPP (5.6.8 ) on a Windows 8.1 machine. Everything executes correctly, and my site runs without a problem. However, the mysql_error.log file contains an InnoDB Warning message, as on the second line here:

Code: Select all
2015-04-27 09:15:30 5828 [Note] Plugin 'FEDERATED' is disabled.
2015-04-27 09:15:30 d7c 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-04-27 09:15:30 5828 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-04-27 09:15:30 5828 [Note] InnoDB: The InnoDB memory heap is disabled
2015-04-27 09:15:30 5828 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-04-27 09:15:30 5828 [Note] InnoDB: Memory barrier is not used
2015-04-27 09:15:30 5828 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-04-27 09:15:30 5828 [Note] InnoDB: Not using CPU crc32 instructions
2015-04-27 09:15:30 5828 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-04-27 09:15:30 5828 [Note] InnoDB: Completed initialization of buffer pool
2015-04-27 09:15:30 5828 [Note] InnoDB: Highest supported file format is Barracuda.
2015-04-27 09:15:30 5828 [Note] InnoDB: 128 rollback segment(s) are active.
2015-04-27 09:15:30 5828 [Note] InnoDB: Waiting for purge to start
2015-04-27 09:15:30 5828 [Note] InnoDB: 5.6.24 started; log sequence number 1665374
2015-04-27 09:15:30 5828 [Note] Server hostname (bind-address): '*'; port: 3306
2015-04-27 09:15:30 5828 [Note] IPv6 is available.
2015-04-27 09:15:30 5828 [Note]   - '::' resolves to '::';
2015-04-27 09:15:30 5828 [Note] Server socket created on IP: '::'.
2015-04-27 09:15:30 5828 [Note] Event Scheduler: Loaded 0 events
2015-04-27 09:15:30 5828 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.24'  socket: ''  port: 3306  MySQL Community Server (GPL)


I discovered that commenting-out this line:

Code: Select all
innodb_additional_mem_pool_size = 2M


...in the my.ini file suppressed that message. However...

1) I'm not sure what to do with the other notice (now suppressed) that "innodb_use_sys_malloc" will be deprecated; I couldn't located that in the my.ini file...is it elsewhere?

2) Likewise, I'm not sure how to disable "InnoDB's internal memory allocator", the third thing listed in the warning message that is suppressed when that one line in MY.INI is commented-out.

3) Is there anything else in the mysql_error.log file, as shown here, that I should attend to? (The rest of the lines remain when the "innodb_additional_mem_pool_size" is commented-out.)

Many thanks!
by TomXampp
27. April 2015 16:01
 
Forum: XAMPP for Windows
Topic: XAMPP: Innodb error/warning messages in mysql_error.log
Replies: 1
Views: 241

Re: Mysql stürzt bei starker Belastung ab

Ist nicht so das ich nich googlen kann :P
Code: Select all
6   ENXIO   No such device or address


sagt mir null.

Der Fehlercode
Code: Select all
2015-04-21 01:53:25 156724 [ERROR] InnoDB: File (unknown): 'flush' returned OS error 106. Cannot continue operation


Sagt mir laut der zahl 106 das ich eine Diskette einlegen soll :lol:
by mersense
21. April 2015 08:55
 
Forum: XAMPP für Windows
Topic: Mysql stürzt bei starker Belastung ab
Replies: 5
Views: 264

Re: Mysql stürzt bei starker Belastung ab

Hi,

Google mal nach "InnoDB: Operating system error number 6".
Du wirst vielfach denselben Hinweis bekommen.

Mit freundlichen Grüßen,
Altrea
by Altrea
21. April 2015 07:47
 
Forum: XAMPP für Windows
Topic: Mysql stürzt bei starker Belastung ab
Replies: 5
Views: 264

Mysql stürzt bei starker Belastung ab

Hallo, ich habe gestern für einen Arma 2 Dayz Server eine Datenbank per PHPmyadmin importiert, ab da an fing der Spaß an. Beim hochladen ist mir der Server schon öfters mit der Meldung "#2003 Mysql Server has gone away" abgeschmiert, hab zuerst gedacht das es an der .sql Datei liegt die ich hochlade, beim dritten mal hats allerdings problemlos funktioniert. Soweit so gut, sobald das Spiel anfängt die Datenbank auszulesen schmiert er nach 3-4sec ab.

Serverhardware 6x 2Ghz E5-2620
RAM 8GB DDR3 ECC
500GB SSD

Hier der Error Log, nicht von den Zeiten irritieren lassen das is der letzte log wo ich irgendwann kein bock mehr hatte, da is der Server komischerweise erst nach paar Stunden abgeschmiert.

Code: Select all
2015-04-20 21:37:11 156724 [Note] Plugin 'FEDERATED' is disabled.
2015-04-20 21:37:11 22530 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-04-20 21:37:11 156724 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-04-20 21:37:11 156724 [Note] InnoDB: The InnoDB memory heap is disabled
2015-04-20 21:37:11 156724 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-04-20 21:37:11 156724 [Note] InnoDB: Memory barrier is not used
2015-04-20 21:37:11 156724 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-04-20 21:37:11 156724 [Note] InnoDB: Not using CPU crc32 instructions
2015-04-20 21:37:11 156724 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-04-20 21:37:11 156724 [Note] InnoDB: Completed initialization of buffer pool
2015-04-20 21:37:11 156724 [Note] InnoDB: Highest supported file format is Barracuda.
2015-04-20 21:37:11 156724 [Note] InnoDB: Log scan progressed past the checkpoint lsn 906004722
2015-04-20 21:37:11 156724 [Note] InnoDB: Database was not shutdown normally!
2015-04-20 21:37:11 156724 [Note] InnoDB: Starting crash recovery.
2015-04-20 21:37:11 156724 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-04-20 21:37:12 156724 [Note] InnoDB: Restoring possible half-written data pages
2015-04-20 21:37:12 156724 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 906005157
2015-04-20 21:37:13 156724 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2015-04-20 21:37:13 156724 [Note] InnoDB: 128 rollback segment(s) are active.
2015-04-20 21:37:13 156724 [Note] InnoDB: Waiting for purge to start
2015-04-20 21:37:13 156724 [Note] InnoDB: 5.6.21 started; log sequence number 906005157
2015-04-20 21:37:13 156724 [Note] Server hostname (bind-address): '*'; port: 3306
2015-04-20 21:37:13 156724 [Note] IPv6 is available.
2015-04-20 21:37:13 156724 [Note]   - '::' resolves to '::';
2015-04-20 21:37:13 156724 [Note] Server socket created on IP: '::'.
2015-04-20 21:37:13 156724 [Note] Event Scheduler: Loaded 0 events
2015-04-20 21:37:13 156724 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.21'  socket: ''  port: 3306  MySQL Community Server (GPL)
2015-04-21 01:53:25 4fe34  InnoDB: Operating system error number 6 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-04-21 01:53:25 156724 [ERROR] InnoDB: File (unknown): 'flush' returned OS error 106. Cannot continue operation
by mersense
21. April 2015 07:29
 
Forum: XAMPP für Windows
Topic: Mysql stürzt bei starker Belastung ab
Replies: 5
Views: 264

Error: MySQL shutdown unexpectedly.

I have a similar error:

5:43:28 PM [mysql] Error: MySQL shutdown unexpectedly.
5:43:28 PM [mysql] This may be due to a blocked port, missing dependencies,
5:43:28 PM [mysql] improper privileges, a crash, or a shutdown by another method.
5:43:28 PM [mysql] Press the Logs button to view error logs and check
5:43:28 PM [mysql] the Windows Event Viewer for more clues
5:43:28 PM [mysql] If you need more help, copy and post this
5:43:28 PM [mysql] entire log window on the forums

And the log:

2015-04-20 17:43:26 6864 [Note] Plugin 'FEDERATED' is disabled.
2015-04-20 17:43:26 19d4 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-04-20 17:43:26 6864 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-04-20 17:43:26 6864 [Note] InnoDB: The InnoDB memory heap is disabled
2015-04-20 17:43:26 6864 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-04-20 17:43:26 6864 [Note] InnoDB: Memory barrier is not used
2015-04-20 17:43:26 6864 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-04-20 17:43:26 6864 [Note] InnoDB: Not using CPU crc32 instructions
2015-04-20 17:43:26 6864 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-04-20 17:43:26 6864 [Note] InnoDB: Completed initialization of buffer pool
2015-04-20 17:43:26 6864 [Note] InnoDB: Highest supported file format is Barracuda.
2015-04-20 17:43:27 6864 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 264820691 in the ib_logfiles!
2015-04-20 17:43:27 6864 [Note] InnoDB: Database was not shutdown normally!
2015-04-20 17:43:27 6864 [Note] InnoDB: Starting crash recovery.
2015-04-20 17:43:27 6864 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-04-20 17:43:27 6864 [Note] InnoDB: Restoring possible half-written data pages
2015-04-20 17:43:27 6864 [Note] InnoDB: from the doublewrite buffer...
2015-04-20 17:43:28 6864 [Note] InnoDB: 128 rollback segment(s) are active.
2015-04-20 17:43:28 6864 [Note] InnoDB: Waiting for purge to start
2015-04-20 17:43:28 6864 [Note] InnoDB: 5.6.20 started; log sequence number 264820691
2015-04-20 17:43:28 6864 [Note] Server hostname (bind-address): '*'; port: 3306
2015-04-20 17:43:28 6864 [Note] IPv6 is available.
2015-04-20 17:43:28 6864 [Note] - '::' resolves to '::';
2015-04-20 17:43:28 6864 [Note] Server socket created on IP: '::'.
2015-04-20 17:43:28 6864 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist

[EDIT by Altrea: splitted from original topic - "One thread per unique user and issue" rule => viewtopic.php?f=16&t=67782]
by iccpdn
20. April 2015 15:48
 
Forum: XAMPP for Windows
Topic: Error: MySQL shutdown unexpectedly.
Replies: 1
Views: 279
PreviousNext

Return to advanced search