Hipchat Server Web Interface Inaccessible and Shows a "Services Starting" Message

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

The Web Interface of the Hipchat Server is inaccessible. The  message "Services Starting" appears without further progress.

The following appears in the /var/log/redis-stats.log

Short read or OOM loading DB. Unrecoverable error, aborting now.

Diagnosis

Diagnostic Steps

  • Check if the server's disk is full.  Disk space can be checked from the server by logging into the server's command line terminal and running:

    df -h
  • A full disk from the command above will look similar to this:

    Filesystem      Size  Used Avail Use% Mounted on
    /dev/sda6       59G   59G   0G   100% /

Cause

If the disk gets full, the Redis persistence cache can become corrupted and the service is unable to start.

Resolution

  • Clear up or increase disk space.  Please see the following article for tips on how to proceed:
  • Once the disk space issue is resolved, stop the Redis service by gaining root and stopping the Redis service.  The following commands will accomplish this:

     

    sudo dont-blame-hipchat
    service redisserver stop
  • Still as the root user, backup and then remove the following files:

    /usr/local/var/lib/redis/dump-stats.rdb
    /file_store/redis/dump.rdb
  • Start the Redis and Redis Stats service:

    service redisserver start
    service redisstats start
  • Attempt to log back in to the Hipchat Server Web Interface. 

 

Last modified on Nov 2, 2018

Was this helpful?

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