Hipchat Server displays 'We've been notified and will fix this issue' when connecting through a web browser

Still need help?

The Atlassian Community is here for you.

Ask the community

This article only applies to Atlassian's server products. Learn more about the differences between cloud and server.

This version of Hipchat Server is no longer supported

This article applies to a version of Hipchat Server which is beyond the Atlassian End of Life policy, and is no longer supported.

When was my version deprecated?

The following versions have been deprecated:

  • Hipchat Server 1.3 (EOL Date: Aug 17, 2017)

The following versions will be deprecated soon:

  • Hipchat Server 2.0 (EOL Date: Jun 17, 2018)
  • Hipchat Server 2.1 (EOL Date: Dec 8, 2018)
  • 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. If possible, you should also consider deploying Hipchat Data Center instead.

Problem

  • When trying to connect to https://hipchat.yourcompanyname.com, you face the error "Oops! We've been notified and will fix this issue as soon as we can".



  • Users were not able to login to any Hipchat application on any devices.

 

Diagnosis

Environment

  • Hipchat Server v1.3.5
  • Application originally deployed earlier than 2015

Diagnostic Steps

  • Restarting Hipchat Server services with HipChat upgrade --restart throws the following error: Error: Please see /var/log/chef.log

  • The following error occurs in /var/log/chef.log:

    Error: service name conflict, mysqld already defined in /var/run/mysqld/mysqld.pid

Cause

An existing configuration for the monit service conflicts with part of the upgrade process to Hipchat v1.3.5. This should only occur for Hipchat Servers deployed earlier than 2015 listed in HipChat Server 1.x Release Notes.

Resolution

Run the following commands to remove the conflicting configuration file and re-run the upgrade process:

sudo dont-blame-hipchat "rm -f /etc/monit.d/mysqld.monitrc"

hipchat upgrade --force-upgrade

 

 

Last modified on Jan 19, 2018

Was this helpful?

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