Crowd service is not restarted using "hipchat service --restart" or "hipchat upgrade --restart"
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
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.
Problem
Starting with Hipchat Server 1.4.0, the embedded Crowd service is not restarted using either of the following commands:
hipchat upgrade --restart
hipchat service --restartDiagnosis
Environment
- Hipchat Server 1.4.0 and higher.
Diagnostic Steps
Check the process id of crowd prior to running either of the commands above:
service crowd status crowd is running with pid 5552Run either of the Hipchat restart commands above and note that the process id (5552 in this example) does not change, which means the Crowd service was not restarted:
service crowd status crowd is running with pid 5552
Cause
This is by design and is not a bug in Hipchat Server 1.4.0 and higher. Crowd is not included in the list of services to be restarted using either Hipchat command.
Resolution
If Crowd needs to be restarted, it must be done separately. The following commands should be used to stop, start, restart, or check the status of the crowd service:
sudo dont-blame-hipchat
service crowd stop
service crowd start
service crowd restart
service crowd status