Comment 1 for bug 628510

I investigated this issue with Stefan, we found out a few things but still no
root cause:

- the librarian appinstance is creating those unreadable oops directories.

    <Chex> librarian@mizuho:/srv/launchpadlibrarian.net/production-logs/2010-09-29$ ls -la
    <Chex> total 216
    <Chex> drwx--S--- 2 librarian librarian 4096 Sep 29 09:14 .
    <Chex> drwxr-sr-x 6 librarian librarian 196608 Sep 30 20:37 ..
    <Chex> -rw------- 1 librarian librarian 4348 Sep 29 09:02 32568.LIBRARIANA1
    <Chex> -rw------- 1 librarian librarian 4348 Sep 29 09:14 33248.LIBRARIANA2

- the user running the librarian appinstance seems to have the correct
  permission to create new files.

    <Chex> librarian@mizuho:/tmp$ umask
    <Chex> 0022
    <Chex> so that looks OK

- there's no cronjob changing the permissions afeterwards.

    <Chex> I wonder if there is a cron changing the perms.. checking
    <Chex> no, there is a cron that deletes old librarian.log.* but thats it

- content of one of the oopses: https://pastebin.canonical.com/37969/

- If we find a reliable way of triggereing the oops above we could add some
  cowboy code to the librarian to log the permission at the time an oops is
  being generated. that way we would know if it's the appserver generating the
  content with the wrong permission or if it's some process later on changing
  it.

- Any other ideas to help find out the cause?