No oopses recorded for upload processor
Bug #499423 reported by
Michael Nelson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Michael Nelson |
Bug Description
This could be pebkec, but while trying to help a person with an upload issue, I could not find any associated OOPSes which makes it very difficult to see the cause of problems.
The log showing the oops being generated: http://
But on devpad we only have oopses recorded up until 2009-12-03 in germanium/lp_queue
Changed in soyuz: | |
status: | Triaged → In Progress |
assignee: | nobody → Michael Nelson (michael.nelson) |
Changed in soyuz: | |
milestone: | none → 10.01 |
Changed in soyuz: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
<noodles> mthaddon: sorry, where do I find the oopses for the upload processor? they seem to be in devpad: /srv/launchpad. net-logs/ production/ germanium/ lp_queue but only up until 2009-12-03, and it's not found on the lpoops page. (OOPS-1452PPA1) pastebin. ubuntu. com/344612/ der.uploadproce ssor.py directly. process- upload. py on a cron (or did I misunderstand something)
<mthaddon> noodles: there aren't any more oopses on the server itself after then
<noodles> mthaddon: could it be that the oopses for the process upload have been moved somewhere else recently? You can see the oops on line 5:http://
<mthaddon> noodles: is it possible the OOPS is being created somewhere else (xmlrpc server, etc.)?
<noodles> mthaddon: no, I don't think so. The exception itself is raised in lp.archiveuploa
<mthaddon> noodles: so this is being raised by poppy?
<mthaddon> noodles: there isn't anywhere else the OOPSes could be, so I'm not sure what's going on...
<noodles> mthaddon: no, I assume you've got scripts/
<noodles> hrm, thanks for checking.