Aaron Griffin wrote:
On Mon, Nov 24, 2008 at 7:29 PM, Paul Mattal <[EMAIL PROTECTED]> wrote:
Aaron Griffin wrote:
On Sun, Nov 23, 2008 at 3:39 PM, Eric Bélanger
<[EMAIL PROTECTED]> wrote:
On Mon, 24 Nov 2008, Jud wrote:
Just a quick note to ask if all the Arch Mailing List Archives are
working properly? The last archive was Nov 21.
They are not. It's a known issue: http://bugs.archlinux.org/task/12206
Yeah, I need to fix this. Mails are still saved, I just bungled
something - I think it may be a cron job or something... Paul, ideas?
Since the http user is now http, and mailman knows this (configured
--with-cgi-gid=http), might it be trying to generate its files running as
http and failing?
I think it's the mailmanctl that triggers the HTML generation, and that's
running.
The log suggests it's a permissions error that's got it bothered:
[EMAIL PROTECTED] logs]$ tail /home/mailman/logs/error
File "/home/mailman/Mailman/Archiver/Archiver.py", line 216, in ArchiveMail
h.processUnixMailbox(f)
File "/home/mailman/Mailman/Archiver/pipermail.py", line 580, in
processUnixMailbox
self.add_article(a)
File "/home/mailman/Mailman/Archiver/pipermail.py", line 621, in
add_article
filename))
File "/build/pkg/home/mailman/Mailman/Archiver/HyperArch.py", line 1117, in
write_article
IOError: [Errno 13] Permission denied:
'/home/mailman/archives/private/arch-commits/2008-November.txt'
Nov 24 19:55:29 2008 (883) SHUNTING:
1227574528.0539091+1d68829fb20ee10145eb849e4aad96c7d175b4a6
Good catch. I chown'd them to http to see if that helps. Re-running
bin/arch arch-general (as sudo, sadly) to see if this works out
Seems like when mailman creates new archive files, it is creating them
mailman:mailman 664. The current stuff is http:mailman 644, and so it
can't write to it when running as mailman:mailman.
Maybe try chowning mailman:mailman 664?
- P
