Notifications fail due to missing curler service

お困りですか?

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

コミュニティに質問

プラットフォームについて: 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.

問題

After a server upgrade, mail notifications stop working.

/var/log/chef.log に次のメッセージが出力される。

================================================================================
Error executing action `enable` on resource 'service[curler]'
================================================================================


Chef::Exceptions::Exec
----------------------
/usr/sbin/update-rc.d curler defaults returned 1, expected 0


Resource Declaration:
---------------------
# In /hipchat-scm/chef-repo/cookbooks/curler/recipes/default.rb

23: service 'curler' do
24: action [:enable, :start]
25: supports :status => true, :start => true, :stop => true, :restart => true
26: end
27:



Compiled Resource:
------------------
# Declared in /hipchat-scm/chef-repo/cookbooks/curler/recipes/default.rb:23:in `from_file'

service("curler") do
action [:enable, :start]
supports {:status=>true, :start=>true, :stop=>true, :restart=>true}
retries 0
retry_delay 2
service_name "curler"
pattern "curler"
startup_type :automatic
cookbook_name :curler
recipe_name "default"
end







[2017-05-05T01:55:43+00:00] ERROR: Running exception handlers
[2017-05-05T01:55:43+00:00] ERROR: Exception handlers complete
[2017-05-05T01:55:43+00:00] FATAL: Stacktrace dumped to /usr/local/src/chef-stacktrace.out
[2017-05-05T01:55:43+00:00] ERROR: service[curler] (curler::default line 23) had an error: Chef::Exceptions::Exec: /usr/sbin/update-rc.d curler defaults returned 1, expected 0
[2017-05-05T01:55:09+00:00] INFO: Forking chef instance to converge...
[2017-05-05T01:55:43+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
[2017-05-05T01:55:43+00:00] INFO: Allow custom /etc files
[2017-05-05T01:55:43+00:00] INFO: Re-enabling monitoring
* Starting daemon monitor monit
...done.
Recording last chef run finished at 1493949343
[2017-05-05T01:55:43+00:00] ERROR: Error: Configuration failure
[2017-05-05T01:55:43+00:00] INFO: Releasing chef lock
[2017-05-05T01:55:44+00:00] INFO: Cleaning up consul session 664eab8c-fc3f-e884-1e0e-274b37113a14
curler: unrecognized service
=========

curler does not seem to exist in the system

環境

  • Hipchat Server upgraded to version 1.4.x or higher. 

診断

  • Check if the correct hc-curler package version is installed in Hipchat Server  by executing - dpkg -l | grep hc-curler

  • Check if the curler service/process is running by executing - ps aux | grep curler.  Below is an example of a running curler service/process:

    $ ps aux | grep curler
    
    admin     9058  0.0  0.0  10460   932 pts/0    S+   06:27   0:00 grep --color=auto curler
    
    hipchat  26850  0.0  0.4 133288 18556 ?        Sl   May09   0:00 /hipchat-scm/curler/vendor/virtualenv/bin/python /hipchat/curler/current/vendor/virtualenv/bin/twistd -r epoll --umask=022 --pidfile=/var/run/hipchat/curler.pid --syslog --prefix=curler --facility=168 curler --base-urls=http://localhost:8080/_jobs --job-queue=curler --gearmand-server=localhost:4730 --num-workers=5

原因

Somehow hc-curler package was not properly installed during the upgrade process, which prevented the service from starting up.

ソリューション

Remove and purge existing hc-curler package (if any) on the Hipchat Server and re-install it.

  1. SSH into Hipchat Server's terminal/command-line

  2. Gain root access:

    sudo dont-blame-hipchat
  3. To remove and purge existing hc-curler package (if any), run this command from the server's terminal:

    dpkg --purge hc-curler
    
  4. To re-install the hc-curler package, run this command from the server's terminal:

    dpkg -i /file_store/archive/pool/main/h/hc-curler/hc-curler_2017.02.27.212247-774360f_all.deb 
    
  5. Restart Hipchat services:

    hipchat service --restart
    
  6. Verify that curler is running:

    ps aux | grep curler
    

 

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

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

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