Librarian should log OOPS reports

[Andrew Bennetts]

Sometimes, when the client is uploading a file the Librarian has an unexpected problem and returns "500 Internal server error" to the client. At the moment we then have to look at the Librarian log file to find out what happened. Instead, the Librarian should generate an OOPS, and include the OOPS code in the error message given to the client.

[Stuart Bishop (stub)]

Dropping for now.

[Joey Stanford (joey)]

This happened again tonight and we ended up rebooting. It would be nice if we could reconsider doing this or something similar such that we can identify the errors and proactively fix them.

[Christian Reis (kiko)]

We can get pretty reliable failures when attempting to upload large files. Should this not be escalated?

[Diogo Matsubara (matsubara)]

Once we have the librarian reporting OOPSes, we'll want to have either a separate summary or a separate section.

[Robert Collins (lifeless)]

http://twistedmatrix.com/trac/ticket/3363 is the upstream bug for this - the specific bit is the 'nologrotation' patch (which henninge did!) - http://twistedmatrix.com/trac/ticket/3363#comment:7

[Robert Collins (lifeless)]

garh ETOOMANYTABS - sorry!

[Launchpad QA Bot (lpqabot)]

Fixed in stable r11228 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11228>.

[Diogo Matsubara (matsubara)]

Set oops-tools bugtask as invalid in favor of bug 616041

[Curtis Hovey (sinzui)]

Fixed released in launchpad-project 10.08.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r11522 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11522>.

[Ursula Junque (ursinha)]

This bug wrong tagged, one case of bug 638468. I'm removing the tag.