Bug 1302466 - HTTP 500 error, calamari cannot write to cthulhu.log
HTTP 500 error, calamari cannot write to cthulhu.log
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Calamari (Show other bugs)
Unspecified Unspecified
unspecified Severity urgent
: rc
: 1.3.2
Assigned To: Gregory Meno
Depends On:
  Show dependency treegraph
Reported: 2016-01-27 19:07 EST by Ken Dreyer (Red Hat)
Modified: 2016-02-29 09:45 EST (History)
4 users (show)

See Also:
Fixed In Version: RHEL: calamari-server-1.3.3-1.el7cp Ubuntu: calamari_1.3.3-2redhat1trusty
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-29 09:45:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
calamari.log (3.31 MB, text/plain)
2016-01-28 04:01 EST, Tanay Ganguly
no flags Details

  None (edit)
Description Ken Dreyer (Red Hat) 2016-01-27 19:07:34 EST
Description of problem:
The calamari web application tries to write to cthulhu.log. This file is owned by root, but the web application is running as an unprivileged Apache UID.

Version-Release number of selected component (if applicable):
Calamari 1.3.2 (Ubuntu and RHEL)

How reproducible:

Steps to Reproduce:
1. Install calamari and set up according to instructions
2. Check the web server (http://calamari-node/)

Actual results:
The server returns an HTTP 500 error, and calamari.log indicates that the issue is a permissions problem writing to cthulhu.log.

Expected results:
The web application comes up as expected, and the user can log in

Workaround for RHEL:
sudo chown apache:apache /var/log/calamari/cthulhu.log

Workaround for Ubuntu:
sudo chown www-data:www-data /var/log/calamari/cthulhu.log

After running the chown command, the web app functions as expected.
Comment 1 Tanay Ganguly 2016-01-28 04:00:24 EST
I am hitting the same issue.
But even applying the workaround, i am unable to see the Calamari web server.

sudo chown apache:apache /var/log/calamari/cthulhu.log

My setup is being upgraded from 1.3.1 Async to 1.3.2 (26th Build)

[ceph@cephqe4 ceph-config]$ rpm -qa |grep ceph
[ceph@cephqe4 ceph-config]$ rpm -qa |grep calama

I am seeing the below Error

2016-01-28 08:11:27,692 - ERROR - django.request Internal Server Error: /dashboard/
Traceback (most recent call last):
  File "/opt/calamari/venv/lib/python2.7/site-packages/django/core/handlers/base.py", line 115, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
  File "/opt/calamari/venv/lib/python2.7/site-packages/django/contrib/auth/decorators.py", line 25, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/opt/calamari/venv/lib/python2.7/site-packages/calamari_web-0.1-py2.7.egg/calamari_web/views.py", line 38, in dashboard
    clusters = client.list_clusters()
  File "/opt/calamari/venv/lib/python2.7/site-packages/zerorpc/core.py", line 260, in <lambda>
    return lambda *args, **kargs: self(method, *args, **kargs)
  File "/opt/calamari/venv/lib/python2.7/site-packages/zerorpc/core.py", line 245, in __call__
    return self._process_response(request_event, bufchan, timeout)
  File "/opt/calamari/venv/lib/python2.7/site-packages/zerorpc/core.py", line 217, in _process_response
    reply_event = bufchan.recv(timeout)
  File "/opt/calamari/venv/lib/python2.7/site-packages/zerorpc/channel.py", line 267, in recv
    event = self._input_queue.get(timeout=timeout)
  File "/opt/calamari/venv/lib/python2.7/site-packages/gevent/queue.py", line 200, in get
    result = waiter.get()
  File "/opt/calamari/venv/lib/python2.7/site-packages/gevent/hub.py", line 568, in get
    return self.hub.switch()
  File "/opt/calamari/venv/lib/python2.7/site-packages/gevent/hub.py", line 331, in switch
    return greenlet.switch(self)
LostRemote: Lost remote after 10s heartbeat
Comment 2 Tanay Ganguly 2016-01-28 04:01 EST
Created attachment 1119074 [details]
Comment 4 Ken Dreyer (Red Hat) 2016-02-04 17:45:48 EST
Fixed in v1.3.3 upstream
Comment 9 errata-xmlrpc 2016-02-29 09:45:19 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.