How Do I Troubleshoot The Error "Could not start server: Address already in use: bind"
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
The following KB describes on how the error "Could not start server: Address already in use: bind" can be troubleshoot and fixed. The mentioned error normally occurs when starting up the Fisheye/Crucible instance. The Fisheye/Crucible will fail to start and the following error message will be captured and recorded in the log files:-
1
2
3
4
5
6
2014-09-04 18:54:48,532 ERROR - Could not start server: Address already in use: bind
java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
...The error above suggests that there might another service running on the port dedicated to Fisheye/Crucible instance and this prevent the service from being started. Here is what you can do to troubleshoot and find out what is the service running on the port dedicated for Fisheye/Crucible.
In Windows: | In Linux: |
|---|---|
You can run the netstat command with -o parameters in command line to check the ports and the PID tied up to the port. Then based on the PID, run the tasklist command or use the task manager to find out which program/service is occupying the port dedicated to Fisheye/Crucible. Alternatively, you can use the third party tool TCPView to check the program/service occupying the specific port. | Run the command "netstat -lnptu" to determine the program/service running on the port. |
Upon determining the program/service occupying the affected port. Do free up the affected port and try to start the Fisheye/Crucible instance again. If it fails, then submit a Support Ticket with the log files for further investigation.
Was this helpful?