sql not working

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

my sql is not running

Postby SUDHANSUDAS19 » 03. May 2017 05:53

10:24:56 AM [main] Initializing Control Panel
10:24:56 AM [main] Windows Version: Windows 7 Professional 32-bit
10:24:56 AM [main] XAMPP Version: 5.6.30
10:24:56 AM [main] Control Panel Version: 3.2.2 [ Compiled: Nov 12th 2015 ]
10:24:56 AM [main] You are not running with administrator rights! This will work for
10:24:56 AM [main] most application stuff but whenever you do something with services
10:24:56 AM [main] there will be a security dialogue or things will break! So think
10:24:56 AM [main] about running this application with administrator rights!
10:24:56 AM [main] XAMPP Installation Directory: "c:\users\compaq\desktop\xampp\"
10:24:56 AM [main] Checking for prerequisites
10:24:56 AM [main] All prerequisites found
10:24:56 AM [main] Initializing Modules
10:24:56 AM [Apache] XAMPP Apache is already running on port 80
10:24:56 AM [Apache] XAMPP Apache is already running on port 443
10:24:56 AM [mysql] Problem detected!
10:24:56 AM [mysql] Port 3306 in use by "c:\xampp\mysql\bin\mysqld.exe"!
10:24:56 AM [mysql] MySQL WILL NOT start without the configured ports free!
10:24:56 AM [mysql] You need to uninstall/disable/reconfigure the blocking application
10:24:56 AM [mysql] or reconfigure MySQL and the Control Panel to listen on a different port
10:24:56 AM [filezilla] Problem detected!
10:24:56 AM [filezilla] Port 21 in use by "c:\xampp\filezillaftp\filezillaserver.exe"!
10:24:56 AM [filezilla] FileZilla WILL NOT start without the configured ports free!
10:24:56 AM [filezilla] You need to uninstall/disable/reconfigure the blocking application
10:24:56 AM [filezilla] or reconfigure FileZilla and the Control Panel to listen on a different port
10:24:56 AM [filezilla] Problem detected!
10:24:56 AM [filezilla] Port 14147 in use by "c:\xampp\filezillaftp\filezillaserver.exe"!
10:24:56 AM [filezilla] FileZilla WILL NOT start without the configured ports free!
10:24:56 AM [filezilla] You need to uninstall/disable/reconfigure the blocking application
10:24:56 AM [filezilla] or reconfigure FileZilla and the Control Panel to listen on a different port
10:24:56 AM [main] Enabling autostart for module "MySQL"
10:24:56 AM [main] Starting Check-Timer
10:24:56 AM [main] Control Panel Ready
10:24:57 AM [mysql] Autostart active: starting...
10:24:57 AM [mysql] Problem detected!
10:24:57 AM [mysql] Port 3306 in use by "c:\xampp\mysql\bin\mysqld.exe"!
10:24:57 AM [mysql] MySQL WILL NOT start without the configured ports free!
10:24:57 AM [mysql] You need to uninstall/disable/reconfigure the blocking application
10:24:57 AM [mysql] or reconfigure MySQL and the Control Panel to listen on a different port
10:24:57 AM [mysql] Attempting to start MySQL app...
10:24:57 AM [mysql] Status change detected: running
10:24:58 AM [mysql] Status change detected: stopped
10:24:58 AM [mysql] Error: MySQL shutdown unexpectedly.
10:24:58 AM [mysql] This may be due to a blocked port, missing dependencies,
10:24:58 AM [mysql] improper privileges, a crash, or a shutdown by another method.
10:24:58 AM [mysql] Press the Logs button to view error logs and check
10:24:58 AM [mysql] the Windows Event Viewer for more clues
10:24:58 AM [mysql] If you need more help, copy and post this
10:24:58 AM [mysql] entire log window on the forums
10:24:59 AM [mysql] Problem detected!
10:24:59 AM [mysql] Port 3306 in use by "c:\xampp\mysql\bin\mysqld.exe"!
10:24:59 AM [mysql] MySQL WILL NOT start without the configured ports free!
10:24:59 AM [mysql] You need to uninstall/disable/reconfigure the blocking application
10:24:59 AM [mysql] or reconfigure MySQL and the Control Panel to listen on a different port
10:24:59 AM [mysql] Attempting to start MySQL app...
10:24:59 AM [mysql] Status change detected: running
10:25:00 AM [mysql] Status change detected: stopped
10:25:00 AM [mysql] Error: MySQL shutdown unexpectedly.
10:25:00 AM [mysql] This may be due to a blocked port, missing dependencies,
10:25:00 AM [mysql] improper privileges, a crash, or a shutdown by another method.
10:25:00 AM [mysql] Press the Logs button to view error logs and check
10:25:00 AM [mysql] the Windows Event Viewer for more clues
10:25:00 AM [mysql] If you need more help, copy and post this
10:25:00 AM [mysql] entire log window on the forums
SUDHANSUDAS19
 
Posts: 2
Joined: 03. May 2017 05:48
XAMPP version: 3.2.2
Operating System: window 7

sql not working

Postby SUDHANSUDAS19 » 03. May 2017 05:55

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-05-03 09:22:33 1dcc 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-05-03 9:22:33 7628 [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-05-03 9:22:33 7628 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:22:33 7628 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:22:33 7628 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:22:33 7628 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:22:33 7628 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:22:33 7628 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:22:33 7628 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:22:33 7628 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:22:33 7628 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:22:34 7628 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:22:34 7628 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:22:34 7628 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835037
2017-05-03 9:22:35 7252 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:22:35 7628 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:22:35 7628 [Note] Server socket created on IP: '::'.
2017-05-03 9:22:35 7628 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:22:35 7628 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:22:35 7628 [ERROR] Aborting

2017-05-03 09:22:50 1948 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-05-03 9:22:50 6472 [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-05-03 9:22:50 6472 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:22:50 6472 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:22:50 6472 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:22:50 6472 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:22:50 6472 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:22:50 6472 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:22:50 6472 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:22:50 6472 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:22:50 6472 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:22:51 6472 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:22:51 6472 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:22:51 6472 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835541
2017-05-03 9:22:51 7668 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:22:51 6472 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:22:51 6472 [Note] Server socket created on IP: '::'.
2017-05-03 9:22:51 6472 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:22:51 6472 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:22:51 6472 [ERROR] Aborting

2017-05-03 09:23:07 1790 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-05-03 9:23:07 6032 [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-05-03 9:23:07 6032 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:23:07 6032 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:23:07 6032 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:23:07 6032 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:23:07 6032 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:23:07 6032 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:23:07 6032 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:23:07 6032 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:23:07 6032 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:23:08 6032 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:23:08 6032 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:23:08 6032 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835551
2017-05-03 9:23:08 5920 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:23:08 6032 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:23:08 6032 [Note] Server socket created on IP: '::'.
2017-05-03 9:23:08 6032 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:23:08 6032 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:23:08 6032 [ERROR] Aborting

2017-05-03 09:23:56 1434 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-05-03 9:23:56 5172 [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-05-03 9:23:56 5172 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:23:56 5172 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:23:56 5172 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:23:56 5172 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:23:56 5172 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:23:56 5172 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:23:56 5172 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:23:56 5172 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:23:56 5172 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:23:57 5172 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:23:57 5172 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:23:57 5172 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835561
2017-05-03 9:23:57 6464 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:23:57 5172 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:23:57 5172 [Note] Server socket created on IP: '::'.
2017-05-03 9:23:57 5172 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:23:57 5172 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:23:57 5172 [ERROR] Aborting

2017-05-03 09:24:09 1af8 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-05-03 9:24:09 6904 [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-05-03 9:24:09 6904 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:24:09 6904 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:24:09 6904 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:24:09 6904 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:24:09 6904 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:24:09 6904 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:24:09 6904 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:24:09 6904 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:24:09 6904 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:24:10 6904 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:24:10 6904 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:24:10 6904 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835571
2017-05-03 9:24:10 5720 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:24:10 6904 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:24:10 6904 [Note] Server socket created on IP: '::'.
2017-05-03 9:24:10 6904 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:24:10 6904 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:24:10 6904 [ERROR] Aborting

2017-05-03 09:25:14 8cc 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-05-03 9:25:14 2252 [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-05-03 9:25:14 2252 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:25:14 2252 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:25:14 2252 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:25:14 2252 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:25:14 2252 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:25:14 2252 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:25:14 2252 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:25:15 2252 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:25:15 2252 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:25:15 2252 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:25:15 2252 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:25:15 2252 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835581
2017-05-03 9:25:15 7872 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:25:15 2252 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:25:15 2252 [Note] Server socket created on IP: '::'.
2017-05-03 9:25:15 2252 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:25:15 2252 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:25:15 2252 [ERROR] Aborting

2017-05-03 09:45:38 197c 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-05-03 9:45:38 6524 [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-05-03 9:45:38 6524 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:45:38 6524 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:45:38 6524 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:45:38 6524 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:45:38 6524 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:45:38 6524 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:45:38 6524 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:45:38 6524 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:45:38 6524 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:45:38 6524 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:45:38 6524 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:45:38 6524 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835591
2017-05-03 9:45:39 7748 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:45:39 6524 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:45:39 6524 [Note] Server socket created on IP: '::'.
2017-05-03 9:45:39 6524 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:45:39 6524 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:45:39 6524 [ERROR] Aborting

2017-05-03 09:46:38 1f40 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-05-03 9:46:38 8000 [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-05-03 9:46:38 8000 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:46:38 8000 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:46:38 8000 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:46:38 8000 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:46:38 8000 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:46:38 8000 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:46:38 8000 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:46:38 8000 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:46:38 8000 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:46:38 8000 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:46:38 8000 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:46:38 8000 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835601
2017-05-03 9:46:38 4796 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:46:38 8000 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:46:38 8000 [Note] Server socket created on IP: '::'.
2017-05-03 9:46:38 8000 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:46:38 8000 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:46:38 8000 [ERROR] Aborting

2017-05-03 09:46:43 1e5c 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-05-03 9:46:43 7772 [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-05-03 9:46:43 7772 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:46:43 7772 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:46:43 7772 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:46:43 7772 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:46:43 7772 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:46:43 7772 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:46:43 7772 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:46:43 7772 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:46:43 7772 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:46:44 7772 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:46:44 7772 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:46:44 7772 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835611
2017-05-03 9:46:44 5596 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:46:44 7772 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:46:44 7772 [Note] Server socket created on IP: '::'.
2017-05-03 9:46:44 7772 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:46:44 7772 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:46:44 7772 [ERROR] Aborting

2017-05-03 09:46:49 1f24 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-05-03 9:46:49 7972 [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-05-03 9:46:49 7972 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:46:49 7972 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:46:49 7972 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:46:49 7972 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:46:49 7972 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:46:49 7972 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:46:49 7972 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:46:49 7972 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:46:49 7972 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:46:49 7972 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:46:49 7972 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:46:49 7972 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835621
2017-05-03 9:46:49 3100 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:46:49 7972 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:46:49 7972 [Note] Server socket created on IP: '::'.
2017-05-03 9:46:49 7972 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:46:50 7972 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:46:50 7972 [ERROR] Aborting

2017-05-03 09:48:07 1f40 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-05-03 9:48:07 8000 [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-05-03 9:48:07 8000 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:48:07 8000 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:48:07 8000 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:48:07 8000 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:48:07 8000 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:48:07 8000 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:48:07 8000 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:48:07 8000 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:48:08 8000 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-03 9:48:08 8000 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-03 9:48:08 8000 [Note] InnoDB: Waiting for purge to start
2017-05-03 9:48:08 8000 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835631
2017-05-03 9:48:08 3920 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-03 9:48:08 8000 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:48:08 8000 [Note] Server socket created on IP: '::'.
2017-05-03 9:48:08 8000 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2017-05-03 9:48:08 8000 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-05-03 9:48:08 8000 [ERROR] Aborting

2017-05-03 09:57:26 1668 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-05-03 9:57:26 5736 [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-05-03 9:57:26 5736 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:57:26 5736 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:57:26 5736 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:57:26 5736 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:57:26 5736 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:57:26 5736 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:57:26 5736 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:57:26 5736 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:57:27 5736 [Note] InnoDB: The first specified data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2017-05-03 9:57:27 5736 [Note] InnoDB: Setting file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1 size to 10 MB
2017-05-03 9:57:27 5736 [Note] InnoDB: Database physically writes the file full: wait...
2017-05-03 9:57:27 5736 [Note] InnoDB: Setting log file C:\Users\compaq\Desktop\xampp\mysql\data\ib_logfile101 size to 5 MB
2017-05-03 9:57:27 5736 [ERROR] InnoDB: Cannot create C:\Users\compaq\Desktop\xampp\mysql\data\ib_logfile1
2017-05-03 9:57:27 5736 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 9:57:27 5736 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 9:57:27 5736 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:57:27 5736 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 9:57:27 5736 [ERROR] Aborting

2017-05-03 09:57:37 f50 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-05-03 9:57:37 3920 [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-05-03 9:57:37 3920 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 9:57:37 3920 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 9:57:37 3920 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 9:57:37 3920 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 9:57:37 3920 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 9:57:37 3920 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 9:57:37 3920 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 9:57:37 3920 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 9:57:37 3920 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 9:57:37 3920 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 9:57:37 3920 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 9:57:37 3920 [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-05-03 9:57:37 3920 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 9:57:37 3920 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 9:57:37 3920 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 9:57:37 3920 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 9:57:37 3920 [ERROR] Aborting

2017-05-03 10:01:45 1718 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-05-03 10:01:45 5912 [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-05-03 10:01:45 5912 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:01:45 5912 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:01:45 5912 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:01:45 5912 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:01:45 5912 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:01:45 5912 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:01:45 5912 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:01:45 5912 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:01:45 5912 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:01:45 5912 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:01:45 5912 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:01:45 5912 [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-05-03 10:01:45 5912 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:01:45 5912 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:01:45 5912 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:01:45 5912 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:01:45 5912 [ERROR] Aborting

2017-05-03 10:01:47 1fcc 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-05-03 10:01:47 8140 [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-05-03 10:01:47 8140 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:01:47 8140 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:01:47 8140 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:01:47 8140 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:01:47 8140 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:01:47 8140 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:01:47 8140 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:01:47 8140 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:01:47 8140 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:01:47 8140 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:01:47 8140 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:01:47 8140 [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-05-03 10:01:47 8140 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:01:47 8140 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:01:47 8140 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:01:47 8140 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:01:47 8140 [ERROR] Aborting

2017-05-03 10:01:50 1fb4 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-05-03 10:01:50 8116 [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-05-03 10:01:50 8116 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:01:50 8116 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:01:50 8116 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:01:50 8116 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:01:50 8116 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:01:50 8116 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:01:50 8116 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:01:50 8116 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:01:50 8116 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:01:50 8116 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:01:50 8116 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:01:50 8116 [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-05-03 10:01:50 8116 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:01:50 8116 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:01:50 8116 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:01:50 8116 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:01:50 8116 [ERROR] Aborting

2017-05-03 10:05:18 1990 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-05-03 10:05:18 6544 [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-05-03 10:05:18 6544 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:05:18 6544 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:05:18 6544 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:05:18 6544 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:05:18 6544 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:05:18 6544 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:05:18 6544 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:05:18 6544 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:05:18 6544 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:05:18 6544 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:05:18 6544 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:05:18 6544 [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-05-03 10:05:18 6544 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:05:18 6544 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:05:18 6544 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:05:18 6544 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:05:18 6544 [ERROR] Aborting

2017-05-03 10:10:39 1274 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-05-03 10:10:39 4724 [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-05-03 10:10:40 4724 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:10:40 4724 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:10:40 4724 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:10:40 4724 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:10:40 4724 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:10:40 4724 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:10:40 4724 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:10:40 4724 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:10:40 4724 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:10:40 4724 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:10:40 4724 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:10:40 4724 [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-05-03 10:10:40 4724 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:10:40 4724 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:10:40 4724 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:10:40 4724 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:10:40 4724 [ERROR] Aborting

2017-05-03 10:10:43 1060 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-05-03 10:10:43 4192 [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-05-03 10:10:43 4192 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:10:43 4192 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:10:43 4192 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:10:43 4192 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:10:43 4192 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:10:43 4192 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:10:43 4192 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:10:43 4192 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:10:43 4192 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:10:43 4192 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:10:43 4192 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:10:43 4192 [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-05-03 10:10:43 4192 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:10:43 4192 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:10:43 4192 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:10:43 4192 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:10:43 4192 [ERROR] Aborting

2017-05-03 10:12:26 120c 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-05-03 10:12:26 4620 [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-05-03 10:12:26 4620 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:12:26 4620 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:12:26 4620 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:12:26 4620 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:12:26 4620 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:12:26 4620 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:12:26 4620 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:12:26 4620 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:12:26 4620 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:12:26 4620 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:12:26 4620 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:12:26 4620 [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-05-03 10:12:26 4620 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:12:26 4620 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:12:26 4620 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:12:26 4620 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:12:26 4620 [ERROR] Aborting

2017-05-03 10:18:26 1d98 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-05-03 10:18:27 7576 [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-05-03 10:18:27 7576 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:18:27 7576 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:18:27 7576 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:18:27 7576 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:18:27 7576 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:18:27 7576 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:18:27 7576 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:18:27 7576 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:18:27 7576 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:18:27 7576 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:18:27 7576 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:18:27 7576 [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-05-03 10:18:27 7576 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:18:27 7576 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:18:27 7576 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:18:27 7576 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:18:27 7576 [ERROR] Aborting

2017-05-03 10:18:49 620 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-05-03 10:18:49 1568 [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-05-03 10:18:49 1568 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:18:49 1568 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:18:49 1568 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:18:49 1568 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:18:49 1568 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:18:49 1568 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:18:49 1568 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:18:49 1568 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:18:49 1568 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:18:49 1568 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:18:49 1568 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:18:49 1568 [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-05-03 10:18:49 1568 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:18:49 1568 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:18:49 1568 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:18:49 1568 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:18:49 1568 [ERROR] Aborting

2017-05-03 10:18:52 1d7c 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-05-03 10:18:52 7548 [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-05-03 10:18:52 7548 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:18:52 7548 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:18:52 7548 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:18:52 7548 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:18:52 7548 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:18:52 7548 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:18:52 7548 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:18:52 7548 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:18:52 7548 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:18:52 7548 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:18:52 7548 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:18:52 7548 [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-05-03 10:18:52 7548 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:18:52 7548 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:18:52 7548 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:18:52 7548 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:18:52 7548 [ERROR] Aborting

2017-05-03 10:24:57 1c70 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-05-03 10:24:57 7280 [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-05-03 10:24:57 7280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:24:57 7280 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:24:57 7280 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:24:57 7280 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:24:57 7280 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:24:57 7280 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:24:57 7280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:24:57 7280 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:24:57 7280 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:24:57 7280 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:24:57 7280 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:24:57 7280 [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-05-03 10:24:57 7280 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:24:57 7280 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:24:57 7280 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:24:57 7280 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:24:57 7280 [ERROR] Aborting

2017-05-03 10:24:59 1098 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-05-03 10:24:59 4248 [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-05-03 10:24:59 4248 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 10:24:59 4248 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 10:24:59 4248 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-03 10:24:59 4248 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-05-03 10:24:59 4248 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-03 10:24:59 4248 [Note] InnoDB: Using generic crc32 instructions
2017-05-03 10:24:59 4248 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-05-03 10:24:59 4248 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 10:24:59 4248 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 10:24:59 4248 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 10:24:59 4248 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1
2017-05-03 10:24:59 4248 [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-05-03 10:24:59 4248 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 10:24:59 4248 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 10:24:59 4248 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 10:24:59 4248 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 10:24:59 4248 [ERROR] Aborting
SUDHANSUDAS19
 
Posts: 2
Joined: 03. May 2017 05:48
XAMPP version: 3.2.2
Operating System: window 7

Re: sql not working

Postby Nobbie » 03. May 2017 10:32

>2017-05-03 10:24:59 4248 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\compaq\Desktop\xampp\mysql\data\ibdata1

Due to above error message you installed Xampp into your Desktop, what is MEGAWRONG and not recommended.
Nobbie
 
Posts: 9556
Joined: 09. March 2008 13:04

Re: sql not working

Postby moonwalker_repeat » 02. June 2017 07:03

It's also running from C drive as per other messages in the first post. From the messages mentioning conflicting port useage, it looks as if Xampp is warring with itself for ports. I would recommend completely removing Xampp first by using the unintall files in Xampp (both installations if there really are two), and by doing a full search in Explorer for any files that may have been left behind, then running a registry cleaner such as Little Registry Cleaner to get rid of all the erroneous entries there.

Then try a fresh install, this time ONLY in C drive.
Don't let the low number of posts fool you. I've been a Xampp user for many years. I opened a new account because I lost my old credentials for the forum.
User avatar
moonwalker_repeat
 
Posts: 22
Joined: 30. May 2017 05:38
Location: Earth
XAMPP version: 5.6.30
Operating System: OSX, Windows 10

Re: sql not working

Postby Nobbie » 02. June 2017 11:12

moonwalker_repeat wrote:It's also running from C drive as per other messages in the first post. From the messages mentioning conflicting port useage, it looks as if Xampp is warring with itself for ports.


Thats what i thought on the first spot as well, but unfortunately the first post lacks any system date, the second post (which also includes messages from a c:/xampp installation) shows only super old messages from 2015(!), then (from one line to another) the date jumps to 2017 and so does the Xampp installation, which then is mentioned to be in c:/Users. I cannot see if there is still running an old Xampp version from C:/xampp, but its definately worth a try. Maybe SUDHANSUDAS19 simply forgot over the years, that there is still an old Xampp installation. Its a bit confusing anyway.

moonwalker_repeat wrote:then running a registry cleaner such as Little Registry Cleaner to get rid of all the erroneous entries there.


Xampp (optionally) registers only Apache and MySQL as a windows service (easily to be checked with the WIndows System Administration), but besides that Xampp does (fortunately) not put anything into the WIndows registry. It also does not store anything into *.ini files in c:/Windows, usually it is sufficient to remove the Xampp folder only. Vice verse, you can also install Xampp simply from a ZIP package (to be downloaded from Sourceforge) and extract it into the Xampp folder.
Nobbie
 
Posts: 9556
Joined: 09. March 2008 13:04

Re: sql not working

Postby moonwalker_repeat » 02. June 2017 22:53

Nobbie wrote:
moonwalker_repeat wrote:then running a registry cleaner such as Little Registry Cleaner to get rid of all the erroneous entries there.


Xampp (optionally) registers only Apache and MySQL as a windows service (easily to be checked with the WIndows System Administration), but besides that Xampp does (fortunately) not put anything into the WIndows registry. It also does not store anything into *.ini files in c:/Windows, usually it is sufficient to remove the Xampp folder only. Vice verse, you can also install Xampp simply from a ZIP package (to be downloaded from Sourceforge) and extract it into the Xampp folder.


The point is to get rid of shortcuts. If there have been multiple installations over time in multiple locations, that will get rid of them.
Don't let the low number of posts fool you. I've been a Xampp user for many years. I opened a new account because I lost my old credentials for the forum.
User avatar
moonwalker_repeat
 
Posts: 22
Joined: 30. May 2017 05:38
Location: Earth
XAMPP version: 5.6.30
Operating System: OSX, Windows 10

Re: sql not working

Postby Nobbie » 03. June 2017 11:18

Which shortcuts?
Nobbie
 
Posts: 9556
Joined: 09. March 2008 13:04


Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 4 guests