Hipchat Server services start slowly
プラットフォームについて: 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.
問題
Services in Hipchat Server take a long time to start.
This can manifest during:
hipchat service --restart
hipchat upgrade --restart
- system reboots
診断
Diagnostic Steps
- Verify your Hipchat Server virtual machine meets the system requirements for the size of your deployment
- Check the output of top and free to verify that the system isn't running out of CPU or memory
Benchmark the amount of time needed to write a log entry using logger:
admin@example:~$time logger "hello world" real 0m1.401s user 0m0.000s sys 0m0.002sIf the real time in the output is above 0.0010s, this article may apply to you
原因
Hipchat Server is configured to write log entries to an external logging server. The latency writing log entries over the network is adding significant delay in starting services.
ソリューション
Review and modify any configurations made to the rsyslog system within the Hipchat Server virtual machine. These are typically stored under /etc/rsyslog.d/.
The grep command below may be a good starting point:
admin@example:~$ grep -HR @ /etc/rsyslog.d/
/etc/rsyslog.d/11-external.conf:*.* @192.168.1.1:514