Search found 1331 matches: InnoDB

Searched query: +InnoDB

Return to advanced search

My SQL crashing on XAMPP 3.2.2

Hi folks,

Hopefully someone ca help me out there. Every time I open XAMPP MySQL attempts to start but fails and I am greeted with the following message.....

Attempting to start MySQL app...
12:22:43 [mysql] Status change detected: running
12:22:44 [mysql] Status change detected: stopped
12:22:44 [mysql] Error: MySQL shutdown unexpectedly.
12:22:44 [mysql] This may be due to a blocked port, missing dependencies,
12:22:44 [mysql] improper privileges, a crash, or a shutdown by another method.
12:22:44 [mysql] Press the Logs button to view error logs and check
12:22:44 [mysql] the Windows Event Viewer for more clues
12:22:44 [mysql] If you need more help, copy and post this
12:22:44 [mysql] entire log window on the forums

Here is the error log for MySQL, I have searched online and have yet to find a solution

2017-02-28 12:16:46 1a28 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.
2017-02-28 12:16:46 6696 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-02-28 12:16:46 6696 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-02-28 12:16:46 6696 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-28 12:16:46 6696 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-28 12:16:46 6696 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-02-28 12:16:46 6696 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-28 12:16:46 6696 [Note] InnoDB: Using generic crc32 instructions
2017-02-28 12:16:46 6696 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-02-28 12:16:46 6696 [Note] InnoDB: Completed initialization of buffer pool
2017-02-28 12:16:46 6696 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-02-28 12:16:46 6696 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-02-28 12:16:46 6696 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
2017-02-28 12:16:46 6696 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-02-28 12:16:46 6696 [ERROR] Plugin 'InnoDB' init function returned error.
2017-02-28 12:16:46 6696 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-02-28 12:16:46 6696 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-28 12:16:46 6696 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-02-28 12:16:46 6696 [ERROR] Aborting
by charliewizz
28. February 2017 13:17
 
Forum: XAMPP for Windows
Topic: My SQL crashing on XAMPP 3.2.2
Replies: 0
Views: 536

Re: Verbindung zu Mysql mit PHP ist Falsch

Das ist alles ziemlich strange, jetzt startet Apache Server wieder ohne Fehlermeldung, aber mysql geht immer noch nciht, hier ist der text aus der mysql log datei:

2015-11-10 15:26:56 10fc 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-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2015-11-10 15:27:11 5152 [Note] Event Scheduler: Purging the queue. 0 events
2015-11-10 15:27:11 5732 [Note] InnoDB: FTS optimize thread exiting.
2015-11-10 15:27:11 5152 [Note] InnoDB: Starting shutdown...
2015-11-10 15:27:13 5152 [Note] InnoDB: Shutdown completed; log sequence number 1835037
2015-11-10 15:27:13 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2017-02-26 21:40:53 834 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.
2017-02-26 21:40:53 2100 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-02-26 21:40:53 2100 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-02-26 21:40:53 2100 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-26 21:40:53 2100 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-26 21:40:53 2100 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-02-26 21:40:53 2100 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-26 21:40:53 2100 [Note] InnoDB: Using generic crc32 instructions
2017-02-26 21:40:53 2100 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-02-26 21:40:53 2100 [Note] InnoDB: Completed initialization of buffer pool
2017-02-26 21:40:53 2100 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-26 21:40:55 2100 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-26 21:40:55 2100 [Note] InnoDB: Waiting for purge to start
2017-02-26 21:40:55 2100 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835037
2017-02-26 21:40:56 5732 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-02-26 21:40:56 2100 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-26 21:40:56 2100 [Note] Server socket created on IP: '::'.
2017-02-26 21:40:56 2100 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-02-27 07:32:32 1750 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.
2017-02-27 7:32:32 5968 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-02-27 7:32:32 5968 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-02-27 7:32:32 5968 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-27 7:32:32 5968 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-27 7:32:32 5968 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-02-27 7:32:32 5968 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-27 7:32:32 5968 [Note] InnoDB: Using generic crc32 instructions
2017-02-27 7:32:32 5968 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-02-27 7:32:32 5968 [Note] InnoDB: Completed initialization of buffer pool
2017-02-27 7:32:33 5968 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-27 7:32:33 5968 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 1835452 in the ib_logfiles!
2017-02-27 7:32:33 5968 [Note] InnoDB: Database was not shutdown normally!
2017-02-27 7:32:33 5968 [Note] InnoDB: Starting crash recovery.
2017-02-27 7:32:33 5968 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-27 7:32:35 5968 [Note] InnoDB: Restoring possible half-written data pages
2017-02-27 7:32:35 5968 [Note] InnoDB: from the doublewrite buffer...
2017-02-27 7:32:38 5968 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-27 7:32:39 5968 [Note] InnoDB: Waiting for purge to start
2017-02-27 7:32:39 5968 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835452
2017-02-27 7:32:39 5508 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-02-27 7:32:39 5968 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-27 7:32:39 5968 [Note] Server socket created on IP: '::'.
2017-02-27 7:32:40 5968 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-02-27 10:41:42 10bc 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.
2017-02-27 10:41:42 4284 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-02-27 10:41:42 4284 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-02-27 10:41:42 4284 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-27 10:41:42 4284 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-27 10:41:42 4284 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-02-27 10:41:42 4284 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-27 10:41:42 4284 [Note] InnoDB: Using generic crc32 instructions
2017-02-27 10:41:42 4284 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-02-27 10:41:42 4284 [Note] InnoDB: Completed initialization of buffer pool
2017-02-27 10:41:42 4284 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-27 10:41:42 4284 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 1919068 in the ib_logfiles!
2017-02-27 10:41:42 4284 [Note] InnoDB: Database was not shutdown normally!
2017-02-27 10:41:42 4284 [Note] InnoDB: Starting crash recovery.
2017-02-27 10:41:42 4284 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-27 10:41:43 4284 [Note] InnoDB: Restoring possible half-written data pages
2017-02-27 10:41:43 4284 [Note] InnoDB: from the doublewrite buffer...
2017-02-27 10:41:46 4284 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-27 10:41:46 4284 [Note] InnoDB: Waiting for purge to start
2017-02-27 10:41:46 4284 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1919068
2017-02-27 10:41:46 6848 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-02-27 10:41:46 4284 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-27 10:41:46 4284 [Note] Server socket created on IP: '::'.
2017-02-27 10:41:46 4284 [ERROR] mysqld.exe: Table '.\mysql\user' is marked as crashed and should be repaired
2017-02-27 10:41:46 4284 [Warning] Checking table: '.\mysql\user'
2017-02-27 10:41:46 4284 [ERROR] mysql.user: 1 client is using or hasn't closed the table properly
2017-02-27 10:41:46 4284 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-02-27 10:57:39 e38 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.
2017-02-27 10:57:39 3640 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-02-27 10:57:39 3640 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-02-27 10:57:39 3640 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-27 10:57:39 3640 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-27 10:57:39 3640 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-02-27 10:57:39 3640 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-27 10:57:39 3640 [Note] InnoDB: Using generic crc32 instructions
2017-02-27 10:57:40 3640 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-02-27 10:57:40 3640 [Note] InnoDB: Completed initialization of buffer pool
2017-02-27 10:57:40 3640 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-27 10:57:40 3640 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 1919078 in the ib_logfiles!
2017-02-27 10:57:40 3640 [Note] InnoDB: Database was not shutdown normally!
2017-02-27 10:57:40 3640 [Note] InnoDB: Starting crash recovery.
2017-02-27 10:57:40 3640 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-27 10:57:43 3640 [Note] InnoDB: Restoring possible half-written data pages
2017-02-27 10:57:43 3640 [Note] InnoDB: from the doublewrite buffer...
2017-02-27 10:57:47 3640 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-27 10:57:47 3640 [Note] InnoDB: Waiting for purge to start
2017-02-27 10:57:47 3640 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1919078
2017-02-27 10:57:47 4080 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-02-27 10:57:47 3640 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-27 10:57:48 3640 [Note] Server socket created on IP: '::'.
2017-02-27 10:57:48 3640 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-02-27 15:01:43 1794 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.
2017-02-27 15:01:43 6036 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-02-27 15:01:43 6036 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-02-27 15:01:43 6036 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-27 15:01:43 6036 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-27 15:01:43 6036 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-02-27 15:01:43 6036 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-27 15:01:43 6036 [Note] InnoDB: Using generic crc32 instructions
2017-02-27 15:01:43 6036 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-02-27 15:01:43 6036 [Note] InnoDB: Completed initialization of buffer pool
2017-02-27 15:01:44 6036 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-27 15:01:44 6036 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 1919088 in the ib_logfiles!
2017-02-27 15:01:44 6036 [Note] InnoDB: Database was not shutdown normally!
2017-02-27 15:01:44 6036 [Note] InnoDB: Starting crash recovery.
2017-02-27 15:01:44 6036 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-27 15:01:45 6036 [Note] InnoDB: Restoring possible half-written data pages
2017-02-27 15:01:45 6036 [Note] InnoDB: from the doublewrite buffer...
2017-02-27 15:01:48 6036 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-27 15:01:48 6036 [Note] InnoDB: Waiting for purge to start
2017-02-27 15:01:48 6036 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1919088
2017-02-27 15:01:48 4880 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-02-27 15:01:48 6036 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-27 15:01:48 6036 [Note] Server socket created on IP: '::'.
2017-02-27 15:01:48 6036 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-02-27 16:27:03 1360 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.
2017-02-27 16:27:03 4960 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-02-27 16:27:03 4960 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-02-27 16:27:03 4960 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-27 16:27:03 4960 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-27 16:27:03 4960 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-02-27 16:27:03 4960 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-27 16:27:03 4960 [Note] InnoDB: Using generic crc32 instructions
2017-02-27 16:27:03 4960 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-02-27 16:27:03 4960 [Note] InnoDB: Completed initialization of buffer pool
2017-02-27 16:27:04 4960 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-27 16:27:04 4960 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 1919098 in the ib_logfiles!
2017-02-27 16:27:04 4960 [Note] InnoDB: Database was not shutdown normally!
2017-02-27 16:27:04 4960 [Note] InnoDB: Starting crash recovery.
2017-02-27 16:27:04 4960 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-27 16:27:05 4960 [Note] InnoDB: Restoring possible half-written data pages
2017-02-27 16:27:05 4960 [Note] InnoDB: from the doublewrite buffer...
2017-02-27 16:27:07 4960 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-27 16:27:07 4960 [Note] InnoDB: Waiting for purge to start
2017-02-27 16:27:07 4960 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1919098
2017-02-27 16:27:07 5036 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-02-27 16:27:07 4960 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-27 16:27:07 4960 [Note] Server socket created on IP: '::'.
2017-02-27 16:27:07 4960 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution



Wenn jemand dort eine Info findet wo das Problem ist lass mich wissen ich denke ich deinstalliere sonst alles und installiere es neu und wenn das nicht hilft gehts halt nicht.
by MaikApache
27. February 2017 16:22
 
Forum: XAMPP für Windows
Topic: Verbindung zu Mysql mit PHP ist Falsch
Replies: 26
Views: 2176

Re: MySQL Server startet nicht

habe nun die mysql_error.log vom Desktop genommen, Inhalt gelöscht und auf dem Laptop installiert. nach dem Neustart vom mysql sieht das wie folgt aus

170222 9:03:17 [Note] Plugin 'FEDERATED' is disabled.
170222 9:03:17 InnoDB: The InnoDB memory heap is disabled
170222 9:03:17 InnoDB: Mutexes and rw_locks use Windows interlocked functions
170222 9:03:17 InnoDB: Compressed tables use zlib 1.2.3
170222 9:03:17 InnoDB: Initializing buffer pool, size = 16.0M
170222 9:03:17 InnoDB: Completed initialization of buffer pool
170222 9:03:17 InnoDB: highest supported file format is Barracuda.
170222 9:03:17 InnoDB: Waiting for the background threads to start
170222 9:03:18 InnoDB: 1.1.8 started; log sequence number 1595675
170222 9:03:19 [Note] Event Scheduler: Loaded 0 events
170222 9:03:19 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error
170222 9:03:37 [ERROR] Error in accept: No error

....das geht jetzt seitenweise wo weiter!
by MikeE
22. February 2017 09:01
 
Forum: XAMPP für Windows
Topic: MySQL Server startet nicht
Replies: 7
Views: 1078

Re: MySQL shutdown

Okay so I did that. Here is the error log for mysql, which repeats until it's aborted:

2015-11-10 15:26:56 10fc 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-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2015-11-10 15:27:11 5152 [Note] Event Scheduler: Purging the queue. 0 events
2015-11-10 15:27:11 5732 [Note] InnoDB: FTS optimize thread exiting.
2015-11-10 15:27:11 5152 [Note] InnoDB: Starting shutdown...
2015-11-10 15:27:13 5152 [Note] InnoDB: Shutdown completed; log sequence number 1835037
2015-11-10 15:27:13 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2017-02-13 15:57:57 188c 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.
2017-02-13 15:57:57 6284 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.


Here is a list of things I have tried:
Deleting ibdata1. Reappears during next install attempt.
Skype is not even logged in.
Navigating to the file that needs to open port in directory, but .exe file is not there…?
Changing the port from 3306 to 3307 in xampp\mysql\bin\my
Changing everything from xampp to xampp_new
Cmd prompt netstat -an to check if 3306 was listening, and it is. Damn it shit goddamn
Analyzed error:
Problem detected!
3:38:40 PM [mysql] Port 3306 in use by ""C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe" --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.7\my.ini" MySQL57"!
3:38:40 PM [mysql] MySQL WILL NOT start without the configured ports free!
3:38:40 PM [mysql] You need to uninstall/disable/reconfigure the blocking application
3:38:40 PM [mysql] or reconfigure MySQL and the Control Panel to listen on a different port

Then tried to changed my.ini so that it was listening to a different port but I’m not allowed to edit the file… :(
Then went into services to stop the previously-installed separate mysql and got the error posted above.
by ur_mom
16. February 2017 15:29
 
Forum: XAMPP for Windows
Topic: MySQL shutdown
Replies: 2
Views: 592

Re: XAMPP funktioniert aber kein localhost/

Hallo zusammen,

als ich das erste Mal versucht habe XAMPP zu starten kam eine Meldung (ungefähr so) es sei sinnvoll den Port 80 zu ändern. Dann habe ich nach einer Anleitung aus dem Internet diesen Port bei Apache in 8080 geändert. Sonst habe ich keine anderen Weisheiten aus dieser Anleitung. Danach ist ja wenigstens der Apache und MySQL „grün“ geworden.
Nachstehend habe ich log Dateien hinzugefügt.
Nachstehend die error_log von Apache:
[Mon Feb 13 16:18:18.639676 2017] [ssl:warn] [pid 6128:tid 516] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Feb 13 16:18:18.680718 2017] [core:warn] [pid 6128:tid 516] AH00098: pid file C:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Feb 13 16:18:18.756725 2017] [ssl:warn] [pid 6128:tid 516] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Feb 13 16:18:18.943735 2017] [mpm_winnt:notice] [pid 6128:tid 516] AH00455: Apache/2.4.25 (Win32) OpenSSL/1.0.2j PHP/7.1.1 configured -- resuming normal operations
[Mon Feb 13 16:18:18.943735 2017] [mpm_winnt:notice] [pid 6128:tid 516] AH00456: Apache Lounge VC14 Server built: Dec 17 2016 10:42:52
[Mon Feb 13 16:18:18.943735 2017] [core:notice] [pid 6128:tid 516] AH00094: Command line: 'c:\\xampp\\apache\\bin\\httpd.exe -d C:/xampp/apache'
[Mon Feb 13 16:18:18.950695 2017] [mpm_winnt:notice] [pid 6128:tid 516] AH00418: Parent: Created child process 8628
[Mon Feb 13 16:18:19.623759 2017] [ssl:warn] [pid 8628:tid 580] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Feb 13 16:18:19.734778 2017] [ssl:warn] [pid 8628:tid 580] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Feb 13 16:18:19.762782 2017] [mpm_winnt:notice] [pid 8628:tid 580] AH00354: Child: Starting 150 worker threads.
Nachstehend die error-log von My SQL
2017-02-13 16:18:28 8652 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-02-13 16:18:28 8652 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-13 16:18:28 8652 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-13 16:18:28 8652 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-02-13 16:18:28 8652 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-13 16:18:28 8652 [Note] InnoDB: Using generic crc32 instructions
2017-02-13 16:18:28 8652 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-02-13 16:18:28 8652 [Note] InnoDB: Completed initialization of buffer pool
2017-02-13 16:18:28 8652 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-13 16:18:28 8652 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 1835057 in the ib_logfiles!
2017-02-13 16:18:28 8652 [Note] InnoDB: Database was not shutdown normally!
2017-02-13 16:18:28 8652 [Note] InnoDB: Starting crash recovery.
2017-02-13 16:18:28 8652 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-13 16:18:28 8652 [Note] InnoDB: Restoring possible half-written data pages
2017-02-13 16:18:28 8652 [Note] InnoDB: from the doublewrite buffer...
2017-02-13 16:18:28 8652 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-13 16:18:28 8652 [Note] InnoDB: Waiting for purge to start
2017-02-13 16:18:28 8652 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835057
2017-02-13 16:18:28 7444 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-02-13 16:18:28 8652 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-13 16:18:28 8652 [Note] Server socket created on IP: '::'.
2017-02-13 16:18:28 8652 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
Nachstehend der Control Dialog:
16:17:00 [main] Initialisere Control Panel
16:17:00 [main] Windows Version: Home 64-bit
16:17:00 [main] XAMPP Version: 7.1.1
16:17:00 [main] Control Panel Version: 3.2.2 [ Compiled: Nov 12th 2015 ]
16:17:00 [main] Dein Benutzerprofil besitzt keine Administratorenrechte! Das reicht aus für die meisten
16:17:00 [main] Anwendungsfunktionen, aber wann immer du etwas mit Windows-Diensten tun möchtest,
16:17:00 [main] wird eine Sicherheitsabfrage erscheinen oder etwas wird garnicht erst funktionieren!
16:17:00 [main] Also denke daran diese Anwendung mit Administratorrechten zu starten!
16:17:00 [main] XAMPP Installationsverzeichnis: "c:\xampp\"
16:17:00 [main] Voraussetzungen werden geprüft
16:17:01 [main] Alle Voraussetzungen sind erfüllt
16:17:01 [main] Initialisiere Module
16:17:01 [main] Das Mercury Modul ist deaktiviert
16:17:01 [main] Das Tomcat Modul ist deaktiviert
16:17:01 [main] Starte Check-Timer
16:17:01 [main] Control Panel bereit
16:18:17 [Apache] Versuche Apache zu starten...
16:18:17 [Apache] Statusänderung erkannt: gestartet
16:18:28 [mysql] Versuche MySQL zu starten...
16:18:28 [mysql] Statusänderung erkannt: gestartet
by Klausi1
13. February 2017 16:27
 
Forum: XAMPP für Windows
Topic: XAMPP funktioniert aber kein localhost/
Replies: 20
Views: 2411

XAMPP funktioniert aber kein localhost/

Hallo,
habe gerade erstmals auf einem neuen PC XAMPP installiert nach Anleitungen im Internet. Auf dem Control Panel ist Apache und mysql grün. Wenn ich jetzt versuche über localhost/phpmyadmin auf das Programm zu gehen erscheint nur eine weiße Seite. (Auf dem alten PC ging alles prima)
Nachstehend habe ich die Log Datei eingefügt, kann damit leider absolut nichts anfangen. Wer bitte kann mir einen Hinweis geben wo ein Fehler liegt? Bin für jeden Hinweis dankbar. Version 7.1.1. und Win10.
Habe auch im Ordner htdocs meine Homepage hinterlegt. Geht leider auch nicht.

2017-02-12 22:00:36 9856 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-02-12 22:00:36 9856 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-12 22:00:36 9856 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-12 22:00:36 9856 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-02-12 22:00:36 9856 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-12 22:00:36 9856 [Note] InnoDB: Using generic crc32 instructions
2017-02-12 22:00:36 9856 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-02-12 22:00:36 9856 [Note] InnoDB: Completed initialization of buffer pool
2017-02-12 22:00:36 9856 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-12 22:00:36 9856 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 1835047 in the ib_logfiles!
2017-02-12 22:00:36 9856 [Note] InnoDB: Database was not shutdown normally!
2017-02-12 22:00:36 9856 [Note] InnoDB: Starting crash recovery.
2017-02-12 22:00:36 9856 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-12 22:00:36 9856 [Note] InnoDB: Restoring possible half-written data pages
2017-02-12 22:00:36 9856 [Note] InnoDB: from the doublewrite buffer...
2017-02-12 22:00:36 9856 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-12 22:00:36 9856 [Note] InnoDB: Waiting for purge to start
2017-02-12 22:00:36 9856 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835047
2017-02-12 22:00:36 1528 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-02-12 22:00:36 9856 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-12 22:00:36 9856 [Note] Server socket created on IP: '::'.
2017-02-12 22:00:36 9856 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
by Klausi1
12. February 2017 22:25
 
Forum: XAMPP für Windows
Topic: XAMPP funktioniert aber kein localhost/
Replies: 20
Views: 2411

Re: Query pivot 2 tables

No. I tested it again by copying the whole statement and it is still working.
Please doublecheck that you are copying the whole statement.

The statement is based on the structure and data you told us here
Code: Select all
--
-- Tabellenstruktur für Tabelle `users`
--

CREATE TABLE `users` (
  `ID` int(11) NOT NULL,
  `name` varchar(50) NOT NULL,
  `surname` varchar(50) NOT NULL,
  `dob` date NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Daten für Tabelle `users`
--

INSERT INTO `users` (`ID`, `name`, `surname`, `dob`) VALUES
(1, 'Smith', 'John', '2000-01-06'),
(2, 'Doe', 'Joe', '1958-08-25'),
(3, 'Mayer', 'Holly', '1960-05-09');

-- --------------------------------------------------------

--
-- Tabellenstruktur für Tabelle `user_profiles`
--

CREATE TABLE `user_profiles` (
  `ID` int(11) NOT NULL,
  `profile-key` varchar(50) NOT NULL,
  `profile.value` varchar(50) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Daten für Tabelle `user_profiles`
--

INSERT INTO `user_profiles` (`ID`, `profile-key`, `profile.value`) VALUES
(1, 'profile.tel', '123 453 456'),
(1, 'profile.mobile', '235 445 23'),
(1, 'profile.address', '22, Church Street'),
(1, 'profile.city', 'Dodge city'),
(2, 'profile.tel', '565 5654 32'),
(2, 'profile.mobile', '2528 25 1213'),
(2, 'profile.address', '1234, 6th Avenue'),
(2, 'profile.city', 'New London'),
(3, 'profile.tel', '457 578 45'),
(3, 'profile.mobile', '121 545 88'),
(3, 'profile.address', '3, North Street'),
(3, 'profile.city', 'Chicago');

--
-- Indizes der exportierten Tabellen
--

--
-- Indizes für die Tabelle `users`
--
ALTER TABLE `users`
  ADD PRIMARY KEY (`ID`);

--
-- AUTO_INCREMENT für exportierte Tabellen
--

--
-- AUTO_INCREMENT für Tabelle `users`
--
ALTER TABLE `users`
  MODIFY `ID` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
by Altrea
12. February 2017 17:56
 
Forum: XAMPP for Windows
Topic: Query pivot 2 tables
Replies: 31
Views: 1990

Case sensitivity causes error in mySQL start

Hi all,

I have XAMPP Version: 7.1.1, Control Panel Version: 3.2.2

One site i am bringing to a local machine for dev from a Linux box unfortunately has multiple tables with the same name, except for a case difference ( e.g. table: my_table_name and My_Table_Name ) Naturally this is causing issues with identical column values in the ID column on import in Xampp as the tables are imported over each other owing to case sensitivity.

I added lower_case_table_names = 0 into the my.ini and restarted.
mySQL failed with the following error log showing.

Error: MySQL shutdown unexpectedly.
1:01:17 p.m. [mysql] This may be due to a blocked port, missing dependencies,
1:01:17 p.m. [mysql] improper privileges, a crash, or a shutdown by another method.
....
Logs show ...
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-02-11 12:14:02 5192 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2017-02-11 12:14:02 5192 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).

repeat many times over.
....
2017-02-11 12:21:30 2268 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 4333687
2017-02-11 12:21:30 2688 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-02-11 12:21:30 2268 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-11 12:21:30 2268 [Note] Server socket created on IP: '::'.
2017-02-11 12:21:30 2268 [ERROR] mysqld.exe: Table '.\mysql\user' is marked as crashed and should be repaired
2017-02-11 12:21:30 2268 [Warning] Checking table: '.\mysql\user'
2017-02-11 12:21:30 2268 [ERROR] mysql.user: 1 client is using or hasn't closed the table properly
2017-02-11 12:21:30 2268 [ERROR] mysqld.exe: Table '.\mysql\db' is marked as crashed and should be repaired
2017-02-11 12:21:30 2268 [Warning] Checking table: '.\mysql\db'
2017-02-11 12:21:30 2268 [ERROR] mysql.db: 1 client is using or hasn't closed the table properly
2017-02-11 12:21:30 2268 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution


Reversing the setting allows the mySQL to restart.
it comes back with a clean log - just the normal [Note] messages and no errors.

It is quite possible there is something in the mySQL system for Xampp that is case insensitive and as soon as case sensitivity is forced it errors.

It is worth noting that mySQL database table / column [mysql].[column_stats].[min_value'] is in position 4 - not 3. similarly max_value is in position 5 , not 4.

Happy to provide debugging, logs etc as required.
windows 7. Xampp running with admin privelges.
by oitconz
11. February 2017 01:04
 
Forum: XAMPP for Windows
Topic: Case sensitivity causes error in mySQL start
Replies: 0
Views: 692

MySQL Connecting, But No Port

Mysql starts up, but there is no port #. See here: https://www.screencast.com/t/vharfvr3iCJ

(If I connect on Apache, or any other service/module, they connect, and it shows a port. It's simply mysql that connects but isn't showing a port.)

I looked to see if any other programs are using port 3306, and I couldn't find anything.

Again, what is weird is MySQL runs, but it shows no port #.

I modified my config file for a very large .sql import, but I don't think that is the issue. Using sqlyog I was able to connect to localhost on port 3306 using the current config file.

Here is my config file:

# Example MySQL config file for small systems.
#
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't use much resources.
#
# You can copy this file to
# D:/xampp/mysql/bin/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is D:/xampp/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
# password = your_password
port = 3306
socket = "D:/xampp/mysql/mysql.sock"


# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port= 3306
socket = "D:/xampp/mysql/mysql.sock"
basedir = "D:/xampp/mysql"
tmpdir = "D:/xampp/tmp"
datadir = "D:/xampp/mysql/data"
pid_file = "mysql.pid"
# enable-named-pipe
key_buffer = 16M
max_allowed_packet = 1M
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
log_error = "mysql_error.log"

# Change here for bind listening
# bind-address="127.0.0.1"
# bind-address = ::1 # for ipv6

# Where do all the plugins live
plugin_dir = "D:/xampp/mysql/lib/plugin/"

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
# commented in by lampp security
#skip-networking
#skip-federated

# Replication Master Server (default)
# binary logging is required for replication
# log-bin deactivated by default since XAMPP 1.4.11
#log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin


# Point the following paths to different dedicated disks
#tmpdir = "D:/xampp/tmp"
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Comment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir = "D:/xampp/mysql/data"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "D:/xampp/mysql/data"
#innodb_log_arch_dir = "D:/xampp/mysql/data"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 2G
innodb_additional_mem_pool_size = 1G
## Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 4G
innodb_log_buffer_size = 1G
innodb_flush_log_at_trx_commit = 0
innodb_lock_wait_timeout = 50

## UTF 8 Settings
#init-connect=\'SET NAMES utf8\'
#collation_server=utf8_unicode_ci
#character_set_server=utf8
#skip-character-set-client-handshake
#character_sets-dir="D:/xampp/mysql/share/charsets"

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout



Any ideas on what the issue might be?

Thanks,
Thomas
by twa25
30. January 2017 19:37
 
Forum: XAMPP for Windows
Topic: MySQL Connecting, But No Port
Replies: 1
Views: 560

Re: apache stopped working

I should mention I AM logged in as Administrator.
This is the log error message I see for My Sql:
2015-11-10 15:26:56 10fc 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-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2015-11-10 15:27:11 5152 [Note] Event Scheduler: Purging the queue. 0 events
2015-11-10 15:27:11 5732 [Note] InnoDB: FTS optimize thread exiting.
2015-11-10 15:27:11 5152 [Note] InnoDB: Starting shutdown...
2015-11-10 15:27:13 5152 [Note] InnoDB: Shutdown completed; log sequence number 1835037
2015-11-10 15:27:13 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete

I am just a novice trying to install Wordpress on my computer. Having problems doing so.
Any advice about what I need to do will be welcomed.
by cath999
29. January 2017 15:35
 
Forum: XAMPP for Windows
Topic: apache stopped working
Replies: 6
Views: 1133

Re: Kann plötzlich keine Datenbank mehr importieren

Tastenplayer wrote:Zudem kam gestern im installierten Forum diese Meldung: HTTP-Eingabe-Kodierung:mbstring.http_input muss auf pass eingestellt sein. HTTP-Ausgabe-Kodierung:mbstring.http_output muss auf pass eingestellt sein.
In drei installierten Foren ist diese Meldung nie gekommen - es muss also irgend etwas passiert sein in der Xampp db gestern.


Das hat überhaupt gar nichts mit der Datenbank zu tun, obwohl ich hier leider nur eine verstümmelte Fehlermeldung bekomme, habe ich die in Google eingegegen und kriege u.a. an erster Stelle diesen Treffer:

http://www.ongray-design.de/forum/viewtopic.php?t=926

Das ist eine Inkompatibilität von phpBB3 zu PHP 5.6 (damals - vielleicht auch zu anderen Releases). Ich habe mir den Strang nicht komplett durchgelesen, vielleicht ist auch irgendwo eine Lösung dabei, aber das hat mit der DB Nullkommagarnichts zu tun. Und es ist ein Problem von phpBB3 (wie ich vorher schon gesagt habe), da kann ich nicht viel zu sagen.

Leider steht nicht viel Info in Deiner Beschreibung, ich würde raten, dass Du aus einer alten(?) Xampp Umgebung irgendwelche Daten in eine neue Xampp Umgebung portieren willst. Keine Ahnung. Aber es muss nicht an MariaDB liegenm, früher wurde in Xampp und MySQL mit der Engine MyISAM gearbeitet, das hat Oracle (die haben MySQL gekauft) schon vor einiger Zeit auf InnoDB umgestellt. Je nachdem, was da in phpBB3 gespeichert ist, kann es schon sein, dass es alleine deswegen so lange Portierungszeiten gibt. InnoDB funktioniert intern vollkommen anders als MyISAM und ist in manchen Dingen viel langsamer. Ich weiß auch über die Umgebung nichts, aber ob MariaDB die Ursache allen Übels ist, das ist nur sehr sehr schwer zu sagen. Letztendlich kannst Du auch einfach MySQL installieren (von der MySQL Seite), dann starte NICHT von Xampp das MariaDB, sondern starte diesen MySQL Server. Das müßte problemlos funktionieren, natürlich hast Du dann eine neue Datenbank und musst neu alles anlegen, aber dann ist MariaDB auf alle Fälle raus.
by Nobbie
27. January 2017 11:23
 
Forum: XAMPP für Windows
Topic: Kann plötzlich keine Datenbank mehr importieren
Replies: 6
Views: 679

MySQL Invalid Status

Hello,

I'm facing with a strange problem.

I'm running XAMPP 5.6.23.0 under Sierra, I have created plists to start MySQL and Apache automatically. This works fine (Applications work).
However to make the MySQL Plist working I had to do : chmod 600 my.cnf

The MySQL plist is as follows :

Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>EnableTransactions</key>
<true/>
<key>Label</key>
<string>apachefriends.xampp.mysql.start</string>
<key>ProgramArguments</key>
<array>
<string>/Applications/XAMPP/xamppfiles/xampp</string>
<string>startmysql</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>WorkingDirectory</key>
<string>/Applications/XAMPP/xamppfiles</string>
<key>KeepAlive</key>
<false/>
<key>AbandonProcessGroup</key>
<true/>
</dict>
</plist>


If I start the control panel, the MySQL status goes to "Checking" then "Stopped" but the Apache status is "Running". This is wrong because MySQL works.

From the control panel, If I stop all, obviously all server status go to "Stopped". However, MySQL remains active (because my applications which connect to any data base still works).

Now, If I'm trying to restart MySQL from the control panel, status goes to "Starting" and after a while (about 20 seconds) returns to "Stopped". At this time, I checked the err log file, and noticed a loop for messages written into this file (see bellow). That I do not understand.

So I tried to push further my investigations.

I removed the PList from /Library/LaunchDaemons, and just tried to start MySQl from the control panel. This time everything went OK. It seems to me there is a sort of incompatibility with Plist and the Control-panel procedures.



Any idea ? Thanks a lot in advance

Gégé

macbook-pro-de-gerard.home.err

2017-01-15 10:53:59 1843 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/macbook-pro-de-gerard.home.pid ended
2017-01-15 11:02:39 1183 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
2017-01-15 11:02:39 140736210990016 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2017-01-15 11:02:39 140736210990016 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.13-MariaDB) starting as process 1325 ...
2017-01-15 11:02:39 140736210990016 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
2017-01-15 11:02:39 140736210990016 [ERROR] mysqld: Can't lock aria control file '/Applications/XAMPP/xamppfiles/var/mysql/aria_log_control' for exclusive use, error: 35. Will retry for 30 seconds
2017-01-15 11:03:10 140736210990016 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/Applications/XAMPP/xamppfiles/var/mysql/aria_log_control'
2017-01-15 11:03:10 140736210990016 [ERROR] Plugin 'Aria' init function returned error.
2017-01-15 11:03:10 140736210990016 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Memory barrier is not used
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Using SSE crc32 instructions
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Completed initialization of buffer pool
2017-01-15 11:03:10 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Retrying to lock the first data file
2017-01-15 11:03:11 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:11 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:12 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:12 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:13 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:13 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:14 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:14 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:15 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:15 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:16 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:16 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:17 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:17 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:18 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:18 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:19 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:19 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:20 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:20


it loops forever.... but if I exit from control panel (stop) the loops terminates and the following messages are added to the error log.


InnoDB: Error number 35 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2017-01-15 11:28:11 140735724544960 [ERROR] InnoDB: Can't open '/Applications/XAMPP/xamppfiles/var/mysql/ibdata1'
2017-01-15 11:28:11 140735724544960 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-01-15 11:28:11 140735724544960 [ERROR] Plugin 'InnoDB' init function returned error.
2017-01-15 11:28:11 140735724544960 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-01-15 11:28:11 140735724544960 [Note] Plugin 'FEEDBACK' is disabled.
2017-01-15 11:28:11 140735724544960 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-01-15 11:28:11 140735724544960 [ERROR] Aborting

2017-01-15 11:28:11 883 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/macbook-pro-de-gerard.home.pid ended
by gegeMartinelli
15. January 2017 11:42
 
Forum: XAMPP for Mac OS X
Topic: MySQL Invalid Status
Replies: 8
Views: 1006

Error: MySQL shutdown unexpectedly.

This thing occur when i started mysql.

logs:
2015-11-10 15:26:56 10fc 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-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2015-11-10 15:27:11 5152 [Note] Event Scheduler: Purging the queue. 0 events
2015-11-10 15:27:11 5732 [Note] InnoDB: FTS optimize thread exiting.
2015-11-10 15:27:11 5152 [Note] InnoDB: Starting shutdown...
2015-11-10 15:27:13 5152 [Note] InnoDB: Shutdown completed; log sequence number 1835037
2015-11-10 15:27:13 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete
by jangshii
13. January 2017 09:41
 
Forum: XAMPP for Windows
Topic: Error: MySQL shutdown unexpectedly.
Replies: 0
Views: 387

Can't Start Apache or MySQL

I'm getting the following errors when I try to start Apache and MySQL

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


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

And this is the only error I find from when I tried starting them:

2017-01-10 12:45:07 27b8 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.
2017-01-10 12:45:07 10168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-01-10 12:45:07 10168 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-10 12:45:07 10168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-01-10 12:45:07 10168 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-01-10 12:45:07 10168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-10 12:45:07 10168 [Note] InnoDB: Using generic crc32 instructions
2017-01-10 12:45:07 10168 [Note] InnoDB: Initializing buffer pool, size = 20.0M
2017-01-10 12:45:07 10168 [Note] InnoDB: Completed initialization of buffer pool
2017-01-10 12:45:07 10168 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-10 12:45:07 10168 [Note] InnoDB: The log sequence numbers 3109477 and 3109477 in ibdata files do not match the log sequence number 14050130 in the ib_logfiles!
2017-01-10 12:45:07 10168 [Note] InnoDB: Database was not shutdown normally!
2017-01-10 12:45:07 10168 [Note] InnoDB: Starting crash recovery.
2017-01-10 12:45:07 10168 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-10 12:45:07 10168 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace amsoil/wp_comments-DESKTOP-7V1BDFV uses space ID: 37 at filepath: .\amsoil\wp_comments-desktop-7v1bdfv.ibd. Cannot open tablespace amsoil/wp_comments which uses space ID: 37 at filepath: .\amsoil\wp_comments.ibd
InnoDB: Error: could not open single-table tablespace file .\amsoil\wp_comments.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.

Any ideas how to fix this?

Thank you!
by redf150flames
10. January 2017 21:42
 
Forum: XAMPP for Windows
Topic: Can't Start Apache or MySQL
Replies: 0
Views: 495

Re: change database structure for InnoDB a MyISAM

Hi,

With help of an SQL Statement:
http://stackoverflow.com/questions/3856 ... nto-innodb

best wishes,
Altrea
by Altrea
23. December 2016 21:01
 
Forum: XAMPP for Windows
Topic: change database structure for InnoDB a MyISAM
Replies: 1
Views: 317
PreviousNext

Return to advanced search