mailman not creating archives
Hi,
I have here a mailman installation on debian/stable. Everything works fine, beside mailman not creating archives, for none of the mailinglists. I am pretty sure it's just a form of PEBCAK and I forgot to set a flag somewhere, but I cannot find it.
The mailinglist config looks as follows:
## Archive options # # List traffic archival policies.
# Archive messages? # # legal values are: # 0 = "No" # 1 = "Yes" archive = True
# Is archive file source for public or private archival? # # legal values are: # 0 = "public" # 1 = "private" archive_private = 0
# How often should a new archive volume be started? # # legal values are: # 0 = "Yearly" # 1 = "Monthly" # 2 = "Quarterly" # 3 = "Weekly" # 4 = "Daily" archive_volume_frequency = 1
There is nothing in the logs and I checked that the permissions of the directories are as they should be (comparing to an other installation, also on debian/stable, where it works).
I kind of run out of places to check. So, I would appreciate any hint as to where to look.
Thanks in advance.
Attila Kinali-- It is upon moral qualities that a society is ultimately founded. All the prosperity and technological sophistication in the world is of no use without that foundation. -- Miss Matheson, The Diamond Age, Neil Stephenson
On 01/22/2018 05:12 AM, Attila Kinali wrote:
Hi,
I have here a mailman installation on debian/stable. Everything works fine, beside mailman not creating archives, for none of the mailinglists.
Have you set ARCHIVE_TO_MBOX in mm_cfg.py (or changed it in Defaults.py) or possibly set PUBLIC_EXTERNAL_ARCHIVER.
From Defaults.py:
# ARCHIVE_TO_MBOX #-1 - do not do any archiving # 0 - do not archive to mbox, use builtin mailman html archiving only # 1 - do not use builtin mailman html archiving, archive to mbox only # 2 - archive to both mbox and builtin mailman html archiving. # See the settings below for PUBLIC_EXTERNAL_ARCHIVER and # PRIVATE_EXTERNAL_ARCHIVER which can be used to replace mailman's # builtin html archiving with an external archiver. The flat mail # mbox file can be useful for searching, and is another way to # interface external archivers, etc. ARCHIVE_TO_MBOX = 2
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mon, 22 Jan 2018 09:00:15 -0800 Mark Sapiro <mark@msapiro.net> wrote:
Have you set ARCHIVE_TO_MBOX in mm_cfg.py (or changed it in Defaults.py) or possibly set PUBLIC_EXTERNAL_ARCHIVER.
No, the settings are the default as they come with the distro.
From my Defaults.py:
# Are archives on or off by default? DEFAULT_ARCHIVE = On
# Are archives public or private by default? # 0=public, 1=private DEFAULT_ARCHIVE_PRIVATE = 0
# ARCHIVE_TO_MBOX #-1 - do not do any archiving # 0 - do not archive to mbox, use builtin mailman html archiving only # 1 - do not use builtin mailman html archiving, archive to mbox only # 2 - archive to both mbox and builtin mailman html archiving. # See the settings below for PUBLIC_EXTERNAL_ARCHIVER and # PRIVATE_EXTERNAL_ARCHIVER which can be used to replace mailman's # builtin html archiving with an external archiver. The flat mail # mbox file can be useful for searching, and is another way to # interface external archivers, etc. ARCHIVE_TO_MBOX = 2
# 0 - yearly # 1 - monthly # 2 - quarterly # 3 - weekly # 4 - daily DEFAULT_ARCHIVE_VOLUME_FREQUENCY = 1
None of these are overwritten in mm_cfg.py.
Attila Kinali-- It is upon moral qualities that a society is ultimately founded. All the prosperity and technological sophistication in the world is of no use without that foundation. -- Miss Matheson, The Diamond Age, Neil Stephenson
On 01/23/2018 05:59 AM, Attila Kinali wrote:
On Mon, 22 Jan 2018 09:00:15 -0800 Mark Sapiro <mark@msapiro.net> wrote:
Have you set ARCHIVE_TO_MBOX in mm_cfg.py (or changed it in Defaults.py) or possibly set PUBLIC_EXTERNAL_ARCHIVER.
No, the settings are the default as they come with the distro.
I know your OP said there's nothing in the logs, but have you specifically looked at Mailman's 'error' and 'qrunner' logs.
I suspect the issue may be ArchRunner not running. If so, there will be a lot of files in /var/lib/mailman/qfiles/archive, there may be files in /var/lib/mailman/qfiles/shunt, and there should be messages in both Mailman's 'error' and 'qrunner' logs from the time ArchRunner died.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, 23 Jan 2018 08:47:56 -0800 Mark Sapiro <mark@msapiro.net> wrote:
I know your OP said there's nothing in the logs, but have you specifically looked at Mailman's 'error' and 'qrunner' logs.
Ok... this is embarrassing... There are permission errors there...
As I said... PEBCAK :-(
I suppose it should work now
Attila Kinali-- <JaberWorky> The bad part of Zurich is where the degenerates throw DARK chocolate at you.
participants (2)
-
Attila Kinali -
Mark Sapiro