XAMPP Not executing

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

XAMPP Not executing

Postby Wyattlg02 » 04. January 2019 19:05

So Yesterday I had posted a topic about the page not actually loading for me to work off of it (the PHP page) now today I go and XAMPP is OFF like completely shut down, I go back to turn it on and I get the following error:

I've read the text, and it says a port is blocked which is shouldn't be, could there be any other errors making this message display? We are running a TeamSpeak 3 server, but I dont think that would conflict

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


As well as this

Code: Select all
12:02:52 PM  [Apache]    If you need more help, copy and post this
12:02:52 PM  [Apache]    entire log window on the forums
12:07:04 PM  [mysql]    Problem detected!
12:07:04 PM  [mysql]    Port 3306 in use by "Unable to open process"!
12:07:04 PM  [mysql]    MySQL WILL NOT start without the configured ports free!
12:07:04 PM  [mysql]    You need to uninstall/disable/reconfigure the blocking application
12:07:04 PM  [mysql]    or reconfigure MySQL and the Control Panel to listen on a different port
12:07:04 PM  [mysql]    Attempting to start MySQL app...


I have checked twice and IIS is not turned on, the port 3306 is open TCP/UDP on the inside network and outside.
Wyattlg02
 
Posts: 10
Joined: 03. January 2019 19:04
XAMPP version: 3.2.2
Operating System: Win 16 Server

Re: XAMPP Not executing

Postby Altrea » 04. January 2019 19:22

Please read and follow this threads to provide us all needed information to identify your issue:
[Q&A] Insufficient debug information - Apache starting issue
[Q&A] Apache won't start
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 9799
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Re: XAMPP Not executing

Postby Wyattlg02 » 04. January 2019 19:46

Okay, so after looking at those links you provided, I have the Apache side of things working (at least it hasn't shut down.) on the other hand, MySQL turns on for 3-5 seconds then shuts down, this is the error log:

Code: Select all
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

2019-01-03 12:09:01 13e4 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.
2019-01-03 12:09:01 5092 [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.

2019-01-03 12:09:01 5092 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-03 12:09:01 5092 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-03 12:09:01 5092 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-01-03 12:09:01 5092 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-01-03 12:09:01 5092 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-03 12:09:01 5092 [Note] InnoDB: Using generic crc32 instructions
2019-01-03 12:09:01 5092 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-01-03 12:09:01 5092 [Note] InnoDB: Completed initialization of buffer pool
2019-01-03 12:09:01 5092 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-03 12:09:02 5092 [Note] InnoDB: 128 rollback segment(s) are active.
2019-01-03 12:09:02 5092 [Note] InnoDB: Waiting for purge to start
2019-01-03 12:09:02 5092 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 1835037
2019-01-03 12:09:02 4596 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-01-03 12:09:02 5092 [Note] Plugin 'FEEDBACK' is disabled.
2019-01-03 12:09:02 5092 [Note] Server socket created on IP: '::'.
2019-01-03 12:09:02 5092 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.37-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:40:20 10388 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-03 19:42:11 10664 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-01-03 19:42:11 10664 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-01-04 12:43:02 1584 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.
2019-01-04 12:43:02 5508 [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.

2019-01-04 12:43:03 5508 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-04 12:43:03 5508 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-04 12:43:03 5508 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-01-04 12:43:03 5508 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-01-04 12:43:03 5508 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-04 12:43:03 5508 [Note] InnoDB: Using generic crc32 instructions
2019-01-04 12:43:03 5508 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-01-04 12:43:03 5508 [Note] InnoDB: Completed initialization of buffer pool
2019-01-04 12:43:03 5508 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-04 12:43:03 5508 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence number 2765999 in the ib_logfiles!
2019-01-04 12:43:03 5508 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-01-04 12:43:04 5508 [Note] InnoDB: 128 rollback segment(s) are active.
2019-01-04 12:43:04 5508 [Note] InnoDB: Waiting for purge to start
2019-01-04 12:43:04 5508 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 2765999
2019-01-04 12:43:04 5476 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-01-04 12:43:04 5508 [Note] Plugin 'FEEDBACK' is disabled.
2019-01-04 12:43:04 5508 [Note] Server socket created on IP: '::'.
2019-01-04 12:43:04 5508 [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.


2019-01-04 12:43:04 5508 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2019-01-04 12:43:04 5508 [ERROR] Aborting

2019-01-04 12:43:13 ef0 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.
2019-01-04 12:43:13 3824 [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.

2019-01-04 12:43:13 3824 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-04 12:43:13 3824 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-04 12:43:13 3824 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-01-04 12:43:13 3824 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-01-04 12:43:13 3824 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-04 12:43:13 3824 [Note] InnoDB: Using generic crc32 instructions
2019-01-04 12:43:13 3824 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-01-04 12:43:13 3824 [Note] InnoDB: Completed initialization of buffer pool
2019-01-04 12:43:13 3824 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-04 12:43:13 3824 [Note] InnoDB: 128 rollback segment(s) are active.
2019-01-04 12:43:13 3824 [Note] InnoDB: Waiting for purge to start
2019-01-04 12:43:14 3824 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 2766009
2019-01-04 12:43:14 5440 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-01-04 12:43:14 3824 [Note] Plugin 'FEEDBACK' is disabled.
2019-01-04 12:43:14 3824 [Note] Server socket created on IP: '::'.
2019-01-04 12:43:14 3824 [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.


2019-01-04 12:43:14 3824 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2019-01-04 12:43:14 3824 [ERROR] Aborting

2019-01-04 12:47:01 dc0 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.
2019-01-04 12:47:01 3520 [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.

2019-01-04 12:47:01 3520 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-04 12:47:01 3520 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-04 12:47:01 3520 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-01-04 12:47:01 3520 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-01-04 12:47:01 3520 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-04 12:47:01 3520 [Note] InnoDB: Using generic crc32 instructions
2019-01-04 12:47:01 3520 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-01-04 12:47:01 3520 [Note] InnoDB: Completed initialization of buffer pool
2019-01-04 12:47:01 3520 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-04 12:47:02 3520 [Note] InnoDB: 128 rollback segment(s) are active.
2019-01-04 12:47:02 3520 [Note] InnoDB: Waiting for purge to start
2019-01-04 12:47:02 3520 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 2766019
2019-01-04 12:47:02 7444 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-01-04 12:47:02 3520 [Note] Plugin 'FEEDBACK' is disabled.
2019-01-04 12:47:02 3520 [Note] Server socket created on IP: '::'.
2019-01-04 12:47:02 3520 [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.


2019-01-04 12:47:02 3520 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2019-01-04 12:47:02 3520 [ERROR] Aborting

2019-01-04 12:47:06 1e14 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.
2019-01-04 12:47:06 7700 [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.

2019-01-04 12:47:07 7700 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-04 12:47:07 7700 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-04 12:47:07 7700 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-01-04 12:47:07 7700 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-01-04 12:47:07 7700 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-04 12:47:07 7700 [Note] InnoDB: Using generic crc32 instructions
2019-01-04 12:47:07 7700 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-01-04 12:47:07 7700 [Note] InnoDB: Completed initialization of buffer pool
2019-01-04 12:47:07 7700 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-04 12:47:07 7700 [Note] InnoDB: 128 rollback segment(s) are active.
2019-01-04 12:47:07 7700 [Note] InnoDB: Waiting for purge to start
2019-01-04 12:47:07 7700 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 2766029
2019-01-04 12:47:07 5368 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-01-04 12:47:07 7700 [Note] Plugin 'FEEDBACK' is disabled.
2019-01-04 12:47:07 7700 [Note] Server socket created on IP: '::'.
2019-01-04 12:47:07 7700 [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.


2019-01-04 12:47:07 7700 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2019-01-04 12:47:07 7700 [ERROR] Aborting

Wyattlg02
 
Posts: 10
Joined: 03. January 2019 19:04
XAMPP version: 3.2.2
Operating System: Win 16 Server

Re: XAMPP Not executing

Postby Altrea » 04. January 2019 20:16

Maybe MariaDB has not stopped too? or there is another process listening on port 3306.
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 9799
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Re: XAMPP Not executing

Postby Wyattlg02 » 04. January 2019 20:31

Is there a way to pull up all active programs listening on that port? Should I change 3306 to something else and see if that works? We don't have MariaDB on the box.
Wyattlg02
 
Posts: 10
Joined: 03. January 2019 19:04
XAMPP version: 3.2.2
Operating System: Win 16 Server

Re: XAMPP Not executing

Postby Nobbie » 04. January 2019 20:47

Simply click the "Netstat" Button in Xampp Dialog. It shows up all processes in your environment.

if you need to go deeper, ask in a Microsoft Forum for help about taskmanager. I do not have sufficient knowlegde about Windows, as Windows is not the scope of this forum.

Anyway, due to the error log i think, that your database / harddisk has been corrupted. Did you have a disk crash and/or did you replace the data folder from Xampp?
Last edited by Nobbie on 04. January 2019 20:48, edited 1 time in total.
Nobbie
 
Posts: 11148
Joined: 09. March 2008 13:04

Re: XAMPP Not executing

Postby Altrea » 04. January 2019 20:48

Wyattlg02 wrote:Is there a way to pull up all active programs listening on that port?

very good question. Yes there is! :D
The XAMPP control panel give you at least two of these ways.
You can start the control panel with elevated administrator rights (rightclick the xampp-control.exe and choose "run as administrator". After that you should see in the control panel logs more information in the prechecks which process is using port 3306.
The other way is the Netstat button and search for the port 3306 in this list.
There are for sure many other ways too.

Wyattlg02 wrote:Should I change 3306 to something else and see if that works?

This is not recommend because many PHP webapplications are default configured to connect to that port.
One of these programs is already included in XAMPP (phpmyadmin)
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 9799
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Re: XAMPP Not executing

Postby Wyattlg02 » 04. January 2019 21:12

I have opened up the netstat window and mySQLd.exe is still open, after closing the one SQL item I saw in the task manager and refreshing the issue is still there.
Wyattlg02
 
Posts: 10
Joined: 03. January 2019 19:04
XAMPP version: 3.2.2
Operating System: Win 16 Server

Re: XAMPP Not executing

Postby Altrea » 04. January 2019 21:54

What do you mean by "closing the one SQL item"?
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 9799
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Re: XAMPP Not executing

Postby Wyattlg02 » 04. January 2019 22:31

There was an item labled SQL something in the Task Manager, I had closed it and it still hasnt loaded (not sure what it is as I have closed it)
Wyattlg02
 
Posts: 10
Joined: 03. January 2019 19:04
XAMPP version: 3.2.2
Operating System: Win 16 Server

Re: XAMPP Not executing

Postby Altrea » 04. January 2019 23:52

Mariadb is already started (process mysqld.exe) or you have another MySQL/Mariadb daemon running on that server.
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 9799
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 68 guests