Hipchat Server Upgrades to 2.2.0 fail to complete or pause requesting user input

Still need help?

The Atlassian Community is here for you.

Ask the community

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.

When will my version be deprecated?

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.

 

 

Problem

Upgrades of Hipchat Server to version 2.2.0 will pause at a configuration file prompt waiting for input or will fail to run to completion.

Hipchat Server Versions affected:

  • Hipchat Server 1.4.0, 1.4.1, or 1.4.2 attempting to upgrade to 2.2.0 or newer

Steps to Reproduce

This problem can be reproduced either by upgrading via command line or by upgrading via the web-based user interface.  The symptoms of the issue may vary, depending on the method used to upgrade. 

 

Upgrade Hipchat Server using the command line using:

hipchat upgrade --upgrade

 

When upgrading via command line console, the upgrade will eventually pause with the following action requested from the user:

Extracting templates from packages: 100%
dpkg: warning: unable to delete old directory '/etc/crowd': Directory not empty
dpkg: warning: unable to delete old directory '/etc/monit.d': Directory not empty
dpkg: warning: unable to delete old directory '/opt/atlassian/hipchat/lib/cli': Directory not empty
dpkg: warning: unable to delete old directory '/opt/atlassian/hipchat/lib': Directory not empty
ssh stop/waiting
ssh start/running, process 17695

Configuration file '/etc/default/docker'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** docker (Y/I/N/O/D/Z) [default=N] ?

 

Upgrade via web-based interface by navigating to Server Admin --> Upgrade


When upgrading using the method above, the upgrade never completes.  The user is redirected back to the server's home page and checking the Server Admin --> Upgrade page reveals that the server is still at the old version. 

Checking the /var/log/hipchat/update.log indicates an error during the execution of cs:

2017-01-31 19:24:22,916 INFO No outbound proxy is configured
2017-01-31 19:24:22,917 INFO beta
2017-01-31 19:25:13,313 ERROR Command '['apt-get', 'upgrade', '-y', '--force-yes', 'hc-chef-repo']' returned non-zero exit status 100
2017-01-31 19:25:13,313 INFO Updating system configuration, this may take a few minutes...
2017-01-31 19:25:13,313 INFO Starting chef run, see /var/log/chef.log for full details
2017-01-31 19:25:24,632 ERROR There was an unexpected error: Command '['sudo', '/opt/atlassian/hipchat/sbin/cs']' returned non-zero exit status 1

The /var/log/chef.log contains the following dependency error:

dpkg: error processing package libc-dev-bin (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libc6-dev:amd64
 libc-dev-bin
---- End output of "bash"  "/tmp/chef-script20170131-13532-1jzt6d9" ----
Ran "bash"  "/tmp/chef-script20170131-13532-1jzt6d9" returned 


Cause

There was a bug in the Hipchat Server upgrade scripts in Hipchat Server versions 1.4.0 through 1.4.2 that caused these issues. 

 

Workaround / Resolution

  • If upgrading via the command line, and the prompt for the docker configuration file is encountered, press Enter (which defaults to 'No').  This will allow the upgrade to continue and it should complete from that point forward.  The upgrade to 2.2.0 includes a new kernel release to address some security issues, which means the server must be rebooted after the upgrade in order to load the new kernel. 
  • If attempting to upgrade from the web-based interface never completes, please perform the following steps below.  The script will apply a patch to the upgrade code.  Note that for the upgrade to complete once the patch is applied, it must be executed from the command line.
    1. Log in to the Hipchat Server's command line console.
    2. Run the following commands:

      wget https://s3.amazonaws.com/hipchat-server-stable/utils/chat-113.tar.gz
      tar -zxvf chat-113.tar.gz
      cd chat-113 && sudo dont-blame-hipchat -c './install.sh'
      hipchat upgrade --upgrade
    3. Once the upgrade completes, please reboot the server to load the updated kernel included with this release. 

The requirements for patching Hipchat Servers at version 1.4.0, 1.4.1, 1.4.2 prior to upgrading are also mentioned in the Release Notes

 

 

Last modified on Nov 2, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.