Comment 5 for bug 300320

I investigated this with spm's help. It's difficult to debug since we don't have evidence anymore and AFAICT, it's been a long time since it last happened.

While investigating, spm pointed out that bug 325962 was recently fixed. That bug could be causing some strange interaction since it was actually starting an additional app server.

I thought this permission problem could be caused by some race condition with the oops pruner. spm identified that the oops pruner script is not run on forster (or edge, fwiw), only on lpnet. spm filed RT 35400 to have the script enabled on all machines.

I think we could close this as invalid for now, until it happens again. If it happens again we shouldn't use the workaround and leave the evidence in place to help debug. I'll email the losas about this.