Closed Bug 628348 Opened 13 years ago Closed 10 years ago

PHX processors quit with 'relation "priority_jobs_nnn" does not exist'

Categories

(Socorro :: General, task)

x86_64
Linux
task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: lars)

Details

We have only seen this since moving to 1.7.6/PHX:

2011-01-24 12:11:44,836 ERROR - MainThread - Caught Error: <class 'psycopg2.ProgrammingError'>
2011-01-24 12:11:44,837 ERROR - MainThread - relation "priority_jobs_805" does not exist
LINE 7: ...                                jobs j right join priority_j...
                                                             ^

2011-01-24 12:11:44,837 ERROR - MainThread - trace back follows:
2011-01-24 12:11:44,838 ERROR - MainThread - Traceback (most recent call last):
2011-01-24 12:11:44,839 ERROR - MainThread - File "/data/socorro/application/scripts/startProcessor.py", line 34, in <module>
    p.start()
2011-01-24 12:11:44,839 ERROR - MainThread - File "/data/socorro/application/socorro/processor/processor.py", line 488, in start
    for aJobTuple in self.incomingJobStream(databaseCursor):
2011-01-24 12:11:44,840 ERROR - MainThread - File "/data/socorro/application/socorro/processor/processor.py", line 456, in incomingJobStream
    aJobTuple = priorityJobIter.next()
2011-01-24 12:11:44,840 ERROR - MainThread - File "/data/socorro/application/socorro/processor/processor.py", line 391, in newPriorityJobsIter
    jobs j right join %s pj on j.uuid = pj.uuid""" % self.priorityJobsTableName)
2011-01-24 12:11:44,841 ERROR - MainThread - ProgrammingError: relation "priority_jobs_805" does not exist
LINE 7: ...                                jobs j right join priority_j...
                                                             ^
2011-01-24 12:11:44,841 INFO - MainThread - done.
Component: Socorro → General
Product: Webtools → Socorro
long ago resolved with the modern processor and retiring of the monitor
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.