Admin received alerts email "failed to start (exit status 0) – /etc/init.d/user-sync: Starting user-sync... ok"
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.
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.
The following versions have been deprecated:
- Hipchat Server 1.3 (EOL Date: Aug 17, 2017)
- Hipchat Server 2.0 (EOL Date: Jun 17, 2018)
- Hipchat Server 2.1 (EOL Date: Dec 8, 2018)
The following version will be deprecated soon:
- Hipchat Server 2.2 (EOL Date: May 30, 2019)
You can read more about Atlassian's End of Life policy here.
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.
After a server upgrade to 2.0 build 1.4.1, admin started to receive the following alerts emails:
Action: alert Desc: failed to start (exit status 0) – /etc/init.d/user-sync: Starting user-sync... ok Event: Execution failed Service: java
Starting from server v1.2 build 1.2.8, user-sync service is no longer used but the file exists on the server v2.0 build 1.4.1 hence admin received the misleading email. Note: This however does not imposed any harm to the server.
Run the following command to disable alerts for user-sync:
sudo dont-blame-hipchat service monit start monit summary monit stop user-sync || true rm -f /etc/monit.d/user-sync.monitrc /usr/sbin/update-rc.d -f user-sync remove || true rm -f /etc/init.d/user-sync dpkg --purge hc-user-sync
Internally, we're working on a script to clean this up in the upcoming Hipchat Server release.
Was this helpful?Yes Provide feedback about this article