On Wednesday 15 December 2010 11:28:21 Stuart Bishop wrote: > On Wed, Dec 15, 2010 at 6:06 PM, Danilo Šegan <[email protected]> wrote: > > Hi Ursula, Diogo, > > > > There seems to be a very weird issue with OOPS-tools: some OOPSes that > > should be timeout OOPSes are something entirely different. > > > > A good example is a timeout OOPS Julian has recently hit: > > > > https://bugs.launchpad.net/soyuz/+bug/690568 > > https://lp-oops.canonical.com/oops.py/?oopsid=1810C878 > > > > I remember seeing something like this yesterday when I was going through > > translations OOPSes as well, so with the second occurrence, I think it's > > worth investigating. > > That is an OOPS from a script, not an appserver. I suspect the > appserver config and the scripts config share a common OOPS prefix and > this is just a collision.
Good call - now I remember this was happening on Soyuz machines until I sorted the prefixes out. _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
