Issues with Sentry installation on ubuntu12.04x86_64

219 views
Skip to first unread message

lvsl

unread,
Jul 10, 2012, 5:22:02 PM7/10/12
to disqus-o...@googlegroups.com
Hi!

This something like a feedback.

I followed this instruction:
  http://sentry.readthedocs.org/en/latest/quickstart/index.html

During the process of installation I found these issues:
requirements:
  python-dev, lievent-dev, libmysqlclient-dev


When running sentry start:
...
  File "/home/chin/Dev/test_sentry/t/local/lib/python2.7/site-packages/django_celery-2.5.5-py2.7.egg/djcelery/admin.py", line 19, in <module>
    from celery.utils import abbrtask
ImportError: cannot import name abbrtask
...
Solution: disable djcelery in INSTALLED_APPS

Traceback (most recent call last):
  File "/home/chin/Dev/test_sentry/t/local/lib/python2.7/site-packages/raven-2.0.0-py2.7.egg/raven/utils/serializer/manager.py", line 61, in transform
    return serializer.serialize(value)
  File "/home/chin/Dev/test_sentry/t/local/lib/python2.7/site-packages/raven-2.0.0-py2.7.egg/raven/contrib/django/serializers.py", line 24, in serialize
    value = getattr(value, '%s__func' % pre)(*getattr(value, '%s__args' % pre), **getattr(value, '%s__kw' % pre))
AttributeError: '__proxy__' object has no attribute '_proxy____func'
Soluton: disable raven.contrib.django in INSTALLED_APPS

  File "/home/chin/Dev/test_sentry/t/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/backends/__init__.py", line 136, in validate_thread_sharing
    % (self.alias, self._thread_ident, thread.get_ident()))
DatabaseError: DatabaseWrapper objects created in a thread can only be used in that same thread. The object with alias 'default' was created in thread id 140498938693376 and this is thread id 69853584.
Solution: patch validate_thread_sharing  to disable it :)



David Cramer

unread,
Jul 12, 2012, 12:50:52 PM7/12/12
to disqus-o...@googlegroups.com
Thanks for the list!

1. I'm updating the docs to address the system packages.

2. The djcelery stuff definitely isn't a requirement, but we try to make it easy. I think we addressed this problem by forcing a version
    of celery

3. I **believe** the problem here is Django 1.4. I might downgrade and require Django 1.3 again
Reply all
Reply to author
Forward
0 new messages