671542 - Stack trace when trying to log karma action for first answer

Status: RESOLVED DUPLICATE of bug 761865

(support.mozilla.org :: Questions, task)

Description

[Ricky Rosario [:rrosario, :r1cky]]

Task questions.tasks.log_answer with id 0013fc93-6ead-4bb3-a3b7-393aad4ac450 raised exception:
"IndexError('list index out of range',)"


Task was called with args: (<Answer: whenever i try to go to most websites it redirects me to the search engine quest scan, how do i stop it from happening?: I had this problem too until I disconnected the ad>,) kwargs: {}.

The contents of the full traceback was:

Traceback (most recent call last):
  File "/data/www/support.mozilla.com/kitsune/vendor/src/celery/celery/execute/trace.py", line 34, in trace
    return cls(states.SUCCESS, retval=fun(*args, **kwargs))
  File "/data/www/support.mozilla.com/kitsune/vendor/src/celery/celery/task/base.py", line 227, in __call__
    return self.run(*args, **kwargs)
  File "/data/www/support.mozilla.com/kitsune/vendor/src/celery/celery/app/__init__.py", line 141, in run
    return fun(*args, **kwargs)
  File "/data/www/support.mozilla.com/kitsune/apps/questions/tasks.py", line 86, in log_answer
    if answer == answer.question.answers.order_by('created')[0]:
  File "/data/www/support.mozilla.com/kitsune/vendor/src/django/django/db/models/query.py", line 190, in __getitem__
    return list(qs)[0]
IndexError: list index out of range

Comment 1

[Ricky Rosario [:rrosario, :r1cky]]

This looks like replication lag. We may need to pin the task (or the one line) to master:
`if answer == answer.question.answers.order_by('created')[0]:`

Comment 2

[Ricky Rosario [:rrosario, :r1cky]]

oops, wrong month

Comment 3

[Ricky Rosario [:rrosario, :r1cky]]

Landed on master:
https://github.com/jsocol/kitsune/commit/6a8d2af5199c42c0cfbb7cb59041fb9944e1970b

And next:
https://github.com/jsocol/kitsune/commit/761bb15422d7275807a5ac5e6d9e6b112ca15256

I wasn't able to reproduce this on stage so we may need to wait until it goes to prod and see if stack traces stop getting emailed.

Comment 4

[Rebecca Billings [:rbillings]]

Should this be [qa-] or is there a way to check on prod or stage?

Comment 5

[Ricky Rosario [:rrosario, :r1cky]]

Marking as [qa-]. If we see another stack trace from prod after tomorrow's push I will reopen.

Comment 6

[Rebecca Billings [:rbillings]]

Closed as [qa-]

Comment 7

[Erik Rose [:erik][:erikrose]]

Hmm, that doesn't appear to have fixed it. Got 2 more stack traces after the push:
July 19, 2011 4:36:33 PM PDT
July 19, 2011 3:52:11 PM PDT

Comment 8

[Ricky Rosario [:rrosario, :r1cky]]

I saw 2-3 after push. They seem to be down in volume, will keep monitoring.

Comment 9

[Ricky Rosario [:rrosario, :r1cky]]

2 more have come in. The volume of these is way down compared to the previous week. Maybe an old celery process stayed around after last restart? Otherwise, I am out of ideas. Lets make sure all celery process restart cleanly during next push.

Comment 10

[Ricky Rosario [:rrosario, :r1cky]]

Still seems to happen about every other day. I was thinking of just logging these when they happen and moving on, but with arecibo we won't get emailed so maybe just WONTFIX it? It is a stack trace from a task so there is no user impact.

Comment 11

[Ricky Rosario [:rrosario, :r1cky]]

Cleaning up 2011Q4