Database startup failure

## Reason 1: Port 13306 is Occupied
**Tips：Before V3.3.4.2 Port 3306 is Occupied**
If the MySQL service fails to start, it may be because port 13306 is occupied by another process. You can use the following commands to check for port occupation:

On Linux systems:

```bash
sudo lsof -i :13306
# Or use the netstat command (requires installation of net-tools)
sudo netstat -tulnp | grep :3306

```
On Windows systems: Open Command Prompt (cmd) and run the following command:

```bash
netstat -ano | findstr :13306

```
After executing the command, you will see output similar to the following:

```bash
tcp        0      0 0.0.0.0:13306       0.0.0.0:*        LISTEN      1234

```
Killing the Process Occupying the Port
If you find that port 13306 is occupied by another process, you can terminate that process.
On Linux systems:

```
sudo kill -9 <Process ID>

```
On Windows systems: Run the following command in Command Prompt:

```
taskkill /PID <Process ID> /F

```
## Reason 2: Changed LarkXR Installation Directory
If LarkXR was previously installed on the server and registered as a system service, changing the deployment directory will result in an incorrect path recorded in the service. In this case, you need to follow these steps:
**Delete the PxyMysql8 Service:**
Open cmd as an administrator and run:

```bash
sc delete PxyMysql8

```
**Restart the Server:**
Restart the server to ensure all configuration updates take effect.

**Restart the Database Service:**
After the server restarts, manually start the database service to ensure it is running properly.