Hipchat Data Center: All Nodes Showing the Same ID
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Problem
You will see the following behaviour in the https://<hcdc_fqdn>/admin/cluster page where all the node IDs are identical to each other:
ID | Name | Address | System time | CPU load | Memory |
---|---|---|---|---|---|
ac5c7bbf6a | ip-10-10-10-15 | 10.10.10.15 | 2017-08-04 05:55:32 | 0.40% of 8 cores | 19.00% of 15 GB total, 1 |
ac5c7bbf6a | ip-10-10-10-20 | 10.10.10.20 | 2017-08-04 05:55:32 | 0.40% of 8 cores | 19.00% of 15 GB total, 1 |
ac5c7bbf6a | ip-10-10-10-25 | 10.10.10.25 | 2017-08-04 05:55:32 | 0.40% of 8 cores | 19.00% of 15 GB total, 1 |
This issue will not directly impact the system as the ID field are just labels.
Diagnosis
The node ID comes from the last 10 digits of server_id value on /hipchat/config/site.json. In this case:
/hipchat/config/site.json"environment": "btf", "fqdn": "hipchat.example.com", "hostname": "ip-10-10-10-15", "ipaddress": "10.10.10.15", "ipaddress_public": "10.10.10.15", "outbound_proxy": null, "server_id": "497e429f-47ab-hl85-8bdb-c7ac5c7bbf6a", "manage_ssl": false, "session_cookie": "s",
The server_id is a unique value that gets generated by /etc/init.d/hipchat on the first boot of the instance.
Cause
There is a high possibility that the same set of /hipchat/config/site.json was copied across all Hipchat Data Center nodes causing them to pick up the same ID.
Resolution
Run the following command on any of the Hipchat Data Center node terminal / SSH console to regenerate the server_id of the nodes:
/opt/atlassian/hipchat/sbin/_keys.py server_id --nochefrun --force
Once done, run hipchat datacenter restart so chef runs, restarts services, and every node will pick up the new service and the ID will be updated accordingly.