XAMPP MySQL Server refuses to start/run

[Agent67]

So I'm trying to quickly finish the mySQL chapter of the PHP/MySQL book we have to work through this year till Chapter 12, but my XAMPP MySQL server refuses to run. The Apache server runs fine tho.

The error I get:

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

What I found in the log:

2023-04-04 9:38:20 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-04-04 9:38:20 0 [Note] InnoDB: Uses event mutexes
2023-04-04 9:38:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-04-04 9:38:20 0 [Note] InnoDB: Number of pools: 1
2023-04-04 9:38:20 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-04-04 9:38:20 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-04-04 9:38:20 0 [Note] InnoDB: Completed initialization of buffer pool
2023-04-04 9:38:20 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-04-04 9:38:20 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-04-04 9:38:20 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-04-04 9:38:20 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-04-04 9:38:20 0 [Note] InnoDB: Waiting for purge to start
2023-04-04 9:38:20 0 [Note] InnoDB: 10.4.27 started; log sequence number 428444; transaction id 327
2023-04-04 9:38:20 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-04-04 9:38:20 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-04-04 9:38:20 0 [Note] Server socket created on IP: '::'.
2023-04-04 9:38:20 0 [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.
2023-04-04 9:38:20 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2023-04-04 9:38:20 0 [ERROR] Aborting

I'm not sure what the hell I can do to solve this. Any ideas, guys?

 

[prod]

I think the last 3 lines gives you a hint into the potential issue:

2023-04-04 9:38:20 0 [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.
2023-04-04 9:38:20 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2023-04-04 9:38:20 0 [ERROR] Aborting

Check if you have anything else running on 3306?

 

[Agent67]

I think the last 3 lines gives you a hint into the potential issue:



Check if you have anything else running on 3306?

TCP 0.0.0.0:3306 [insert desktop name here] LISTENING
[mysqld.exe]

Seems open?

 

[prod]

Seems open?

That looks to me like it's already running and you're trying to start another instance on the same port?

 

[Agent67]

That looks to me like it's already running and you're trying to start another instance on the same port?

So LISTENING means running and not ESTABLISHED?

 

[Agent67]

Got it.

Killed the "mysqld.exe" process, and tried to boot the server again, and it worked.

 

[prod]

So LISTENING means running and not ESTABLISHED?

I might be wrong, but LISTENING to me means that mysqld.exe is basically waiting for network requests on that IP and port (0.0.0.0:3306). So it looks like MySQL is already running

edit: see you solved it