No oopses recorded for upload processor

[Michael Nelson]

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://pastebin.ubuntu.com/344612/ - OOPS-1452PPA1

But on devpad we only have oopses recorded up until 2009-12-03 in germanium/lp_queue

[Michael Nelson (michael.nelson)]

<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)
<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://pastebin.ubuntu.com/344612/
<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.archiveuploader.uploadprocessor.py directly.
<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/process-upload.py on a cron (or did I misunderstand something)
<noodles> hrm, thanks for checking.

[Michael Nelson (michael.nelson)]

Fixed in r60 of the production configs.