Occasional MultipleObjectsReturned errors about sentry HOT 10 CLOSED

I've also started seeing duplicate message_id errors like this, using v1.7.5

from sentry.

We're running into this too. Ever figure out the cause?

from sentry.

It looks like a race condition + a missing constraint. I haven't gotten around to a fix but it should be pretty straight forward

from sentry.

I might need to look into adding that constraint as it's reproducing quite frequently here. We're using mySQL here - are people seeing this on other databases?

from sentry.

I am seeing this on Postgres. Again, it is while we are developing.

from sentry.

I'm not sure if migrations are missing for this (havent had a chance to look), but definitely add a constraint on (logger, view, checksum) if it's missing.

from sentry.

Yep, I'm seeing this too. I noticed an unapplied Sentry migration in the project and applied it, but no joy. (Postgres). Happening in development and staging (where there's a lot less traffic at the mo)

from sentry.

I've been experiencing this with v1.6.0 using a sqlite backend. I don't know if it makes a difference, but the exception that got inserted twice is a

DatabaseError: database is locked

which is happening due to heavy HTTP load.

from sentry.

On 30/12/11 09:55, KennyMonster wrote:

I've been experiencing this with v1.6.0 using a sqlite backend. I
don't know if it makes a difference, but the exception that got
inserted twice is a

DatabaseError: database is locked

That's not at all unexpected when using SQLite. It tends to bail with
that error if someone is writing when you try to read.

If you are using SQLite 3.7+ you might want to switch it to WAL
journaling, which allows concurrent reads and writes.

http://www.sqlite.org/draft/wal.html

Curtis

from sentry.

I'm seeing this quite frequently with Sentry 3.7.1 and MySQL:

Unable to process log entry: get() returned more than one Group -- it returned 2! Lookup parameters were {'project': <Project: #3 u'MyProject'>, 'checksum': 'a23f9e0f025f21f10eac88eeace61856', 'logger': 'myproject.lib.activity.template', 'culprit': None}
Traceback (most recent call last):
File "/opt/sentry/lib/python2.6/site-packages/sentry-3.7.1-py2.6.egg/sentry/manager.py", line 478, in from_kwargs
group, is_new, is_sample = self._create_group(event, **group_kwargs)
File "/opt/sentry/lib/python2.6/site-packages/sentry-3.7.1-py2.6.egg/sentry/manager.py", line 533, in _create_group
defaults=kwargs
File "/opt/sentry/lib/python2.6/site-packages/django/db/models/manager.py", line 135, in get_or_create
return self.get_query_set().get_or_create(**kwargs)
File "/opt/sentry/lib/python2.6/site-packages/django/db/models/query.py", line 378, in get_or_create
return self.get(**lookup), False
File "/opt/sentry/lib/python2.6/site-packages/django/db/models/query.py", line 351, in get
% (self.model._meta.object_name, num, kwargs))
MultipleObjectsReturned: get() returned more than one Group -- it returned 2! Lookup parameters were {'project': <Project: #3 u'MyProject'>, 'checksum': 'a23f9e0f025f21f10eac88eeace61856', 'logger': myproject.lib.activity.template', 'culprit': None}

Interesting that it only seems to happen when the logger is "myproject.lib.activity.template"

from sentry.