Hipchat Server: Data Center mode detected, scanning subnet: XXX.XXX.XX.X/XX After Reboot
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
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.
*Fisheye および Crucible は除く
This is for an outdated version of Hipchat Server
This article applies to a version of Hipchat Server which will be deprecated soon. After that period the version will no longer be supported.
You should upgrade to a more recent version of Hipchat Server as soon as you can to take advantage of new features, and security and bug fixes.
問題
The instance is no longer accessible after a reboot. The following messages will appear in the /var/log/hipchat/boot.log:
Data Center mode detected, scanning subnet: XXX.XXX.XX.X/24
Starting timer, Consul Bootstrap discovery timeout set to: 600 seconds
scanning {XXX.XXX.XX.X ffffff00} which runs from XXX.XXX.XX.X to XXX.XXX.XX.X
WARNING: other nodes should have been detected, expected: 2 , found 0: []
scanning {XXX.XXX.XX.X ffffff00} which runs from XXX.XXX.XX.X to XXX.XXX.XX.X
WARNING: other nodes should have been detected, expected: 2 , found 0: []
scanning {XXX.XXX.XX.X ffffff00} which runs from XXX.XXX.XX.X to XXX.XXX.XX.X
WARNING: other nodes should have been detected, expected: 2 , found 0: []
scanning {XXX.XXX.XX.X ffffff00} which runs from XXX.XXX.XX.X to XXX.XXX.XX.X
WARNING: other nodes should have been detected, expected: 2 , found 0: []
scanning {XXX.XXX.XX.X ffffff00} which runs from XXX.XXX.XX.X to XXX.XXX.XX.X
WARNING: other nodes should have been detected, expected: 2 , found 0: []
scanning {XXX.XXX.XX.X ffffff00} which runs from XXX.XXX.XX.X to XXX.XXX.XX.X
診断
診断
環境
- Hipchat Server 2.2.2
Diagnostic Steps
Accessing the FQDN of the instance will show the ERR_CONNECTION_TIMED_OUT error on the web browser:
Running a telnet command to reach out to the instance fails. For example:
HipChat-MacBook-Pro:~ hipchat$ echo | telnet hipchat.example.com
Trying 10.10.10.1...
telnet: connect to address 10.10.10.1: Operation timed out
telnet: Unable to connect to remote hostGoing through the /etc/chef/solo.json file shows that the run_list is set to role[datacenter].
admin@hipchat:~$ cat /etc/chef/solo.json | grep -a1 "role"
"run_list": [
"role[datacenter]"
],
原因
The value of run_list field was flipped to Data Center mode if the user runs the hipchat datacenter command on the terminal / SSH console. which triggers consul to go think that Data Center is actually in use. By default, it is supposed to be set to role[btf]. For example:
admin@hipchat:~$ cat /etc/chef/solo.json | grep -a1 "role"
"run_list": [
"role[btf]"
],
admin@hipchat:~$ hipchat datacenter
admin@hipchat:~$ cat /etc/chef/solo.json | grep -a1 "role"
"run_list": [
"role[datacenter]"
],
ソリューション
- Obtain a backup of your Hipchat Server instance first before applying the fix as per Back up and restore Hipchat Server
- Change the value of run_list field back to role[btf] after obtaining root access to the instance:
sudo dont-blame-hipchat nano /etc/chef/solo.json"role[btf]" Update the configuration changes and restart all services before rebooting the instance again by running the command below:
hipchat upgrade --restart
Take note that this will disconnect users from their current sessions. Please execute the steps preferably during low peak periodVerify that the instance is accessible again after the restart is completed