Causes: accidentally use kill -9 to delete the Podman container running java program process, start the container again with an error
Description of the problem: The problem is because the port is occupied, can not start
Solution: This is because the port is occupied, you can only find out which process is occupying the port through netstat (I am showing the PID/slirp4netns ), and then kill the process number of the occupied port PID with kill -9
Read More:
- linux tomcat Run (DWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugIni）
- [Solved] Error: listen EADDRINUSE: address already in use :::5000
- [Solved] Web server failed to start. Port 8080 was already in use.
- Aliyunshield occupies port 80 error: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
- How to Solve Error: Address already in use
- Linux Error: bind error: Address already in use [How to Solve]
- Nginx Startup Error: Job for nginx.service failed because the control process exited with error code
- How to Solve NPM Error: listen EADDRINUSE 127.0.0.1:8080
- Nginx Error: [emerg] bind() to [::]:80 failed (98: Address already in use)
- VScode connect Remote Linux Server Error: Resolver error: Error
- Installation, Configuration and Simple Use of Rancher
- Docker Start Container Error: Error response from daemon: task already exists: unknown
- [docker][issue]Error response from daemon: mkdir xxx: file exists: unknown
- The problem of inconsistent host names in building rabbitmq on Linux
- Centos6.8vnc error: connect: Connection refused 10061
- [Solved] Beeline Error: Error: Could not open client transport with JDBC Failed to Connection
- Docker Error: error invoking remote method ‘docker-start-container‘: error: (http code 500) server error –
- How to Solve Docker delete container image error: Error response from daemon: conflict: unable to delete 7cc1942f1ed5 (must be forced)
- PM2 user defined Log, PID and other Log File Locations
- Linux gets the program PID according to the port