Launchpad Librarian creates logfiles with overly restrictive permissions

[Michael Barnett]

When the librarian process creates new logfiles, they are created with ownership librarian:librarian and permissions of 600. This prevents us from being able to properly sync the logs to the dev server.

[Stuart Bishop (stub)]

Is this a launchpad issue, or is the umask just set incorrectly in the production environment?

[Tom Haddon (mthaddon)]

I believe twisted sets umask explicitly (I've come across this before with other twisted log files). If there's an option we can use to set the umask manually that'd be great. A file created as the user that's running the librarian is given 644 perms, fwiw.

[Steve McInerney (spm)]

fwiw. we only see this on 'librarian', not 'librarian2' which sets to 0644.

[Robert Collins (lifeless)]

Ok, so the same code runs librarian and librarian2.

Can you please attach - or review yourself :) - the init scripts and environment variables used to start librarian and librarian2 ?

I've diffed the production configs for the two librarians - no changes other than port prefix and directories.

[Tom Haddon (mthaddon)]

Here's the diff between the two initscripts - https://pastebin.canonical.com/35057/. No smoking gun there...