Hipchat Server displays Fatal error: Call to a member function when accessing the Web Interface

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

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.

*Fisheye および 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.

問題

When accessing the Hipchat Server Web Interface a fatal error is thrown similar to:

  • Fatal error: Call to a member function get_group() on a non-object in /hipchat-scm/web/application/controllers/application.php on line 952

The following appears in the nginx.err.log:

2015-10-13T20:12:47.390040+00:00 hipchat nginx-error: 2015/10/13 20:12:43 [error] 7263#0: *81730 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Call to a member function get_group() on a non-object in /hipchat-scm/web/application/controllers/application.php on line 952" while reading response header from upstream, client: 192.168.0.10, server: , request: "GET /server_admin/setup_welcome HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "hipchat.yourdomain.com"

原因

This issue is caused when the setup wizard is not fully completed and a user drops connection.

ソリューション

The fix requires you to log into the console and reset the owner user account back to defaults (admin@example.com). You then will be able to set-up the correct owner account during the startup wizard.

  1. SSH into your Hipchat Server
  2. Issue the following command:

    hipchat service --reset-owner=EMAIL
  3. Navigate back to the Hipchat Server instance in a web browser and follow the startup wizard to set the new owner account.

(info) If using Hipchat Server v1.3.5 or older, please use  hipchat service --reset-login=EMAIL for step 2 above

最終更新日: 2018 年 1 月 19 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.