Jira Unavailable After Changing the IP Address of the Jira Server (Using MySQL)
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
Summary
Symptoms
After relocating the JIRA server in the network, JIRA fails to start.
The following appears in the atlassian-jira.log:
1
2
CommunicationsException: Communications link failure
The last packet sent successfully to the server was 0 milliseconds ago.Diagnosis
Generally, this issue is seen with MySQL because of its peculiar security paradigm.
Cause
There are two possible causes to this issue:
MySQL will only accept connections through its bind_address. Therefore, the value listed for the Bind Address of the MySQL server must agree with the interface used by JIRA to connect with the server:
MySQL requires that each user be associated with a host. To process a login, the user name, host, and password must all agree:
Solution
Resolution
Ensure that the MySQL my.cnf file includes the correct bind_address value
Ensure that the JIRA user in MySQL is configured to log in from the JIRA host
Was this helpful?