Mailman3 migration and/or archiving problem
I have installed a mailman3 server following this documentation: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-insta...
After a few hiccups I got mailman and postorius working and migrated one list according to this documentation: https://docs.mailman3.org/en/latest/migration.html
It seemed to work and also hyperkitty_import was run without errors (or at least none shown up). Running update_index command said that there were 0 threads copied but I kjnow that the archive isn't empty. But now when I tried to open the list info page from lists view it dies with 500 error.
After diving into the different log files I found an error message that it cannot find /etc/mailman3/mailman-hyperkitty.cfg. Great. Only that the cfg file exists and seems to my (unexpert) eyes correct.
After that problem I tried to create a new list. Creation seemed to go all right but also with it, trying to open the list info page it shows 500 error.
When googling for a solution I landed on a message stating that there might be double entries for the same list in listarchiver table but when I checked ot turns out that the table is empty!
I am a bit confused how to figure out the base cause of the problem and would very much appreciate any pointers.
wbr hank
On Fri, Sep 6, 2024 at 11:43 AM <hnpilot@phnet.fi> wrote:
I have installed a mailman3 server following this documentation: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-insta...
After a few hiccups I got mailman and postorius working and migrated one list according to this documentation: https://docs.mailman3.org/en/latest/migration.html
It seemed to work and also hyperkitty_import was run without errors (or at least none shown up). Running update_index command said that there were 0 threads copied but I kjnow that the archive isn't empty. But now when I tried to open the list info page from lists view it dies with 500 error.
After diving into the different log files I found an error message that it cannot find /etc/mailman3/mailman-hyperkitty.cfg. Great. Only that the cfg file exists and seems to my (unexpert) eyes correct.
After that problem I tried to create a new list. Creation seemed to go all right but also with it, trying to open the list info page it shows 500 error.
When googling for a solution I landed on a message stating that there might be double entries for the same list in listarchiver table but when I checked ot turns out that the table is empty!
I am a bit confused how to figure out the base cause of the problem and would very much appreciate any pointers.
The documentation you followed is quite okay and reasonably detailed. Just wipe out your virtualenv and start over again. Practice it till you get it working. I suspect you missed a step - or did not understand well. You just need to seek clarification on that. Looking at the mailman-web logfile mentioned in that documentation might also help you.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
I have now re-installed venv and the symptoms are exactly the same.
I have now tried to analyze better the log files and theoretically I have found out the culprit, only...
The log file has a error stack like this:
File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/rest/lists.py", line 424, in on_get archiver_set = IListArchiverSet(self._mlist) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/zope/component/_api.py", line 167, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/zope/interface/registry.py", line 363, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/database/transaction.py", line 106, in wrapper return function(args[0], config.db.store, *args[1:], **kws) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/model/mailinglist.py", line 647, in __init__ for archiver in config.archivers: File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/config/config.py", line 284, in archivers archiver = call_name(class_path) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/modules.py", line 70, in call_name return named_callable(*args, **kws) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 60, in __init__ self._load_conf() File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 80, in _load_conf archiver_config = external_configuration( ^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/config/config.py", line 412, in external_configuration raise MissingConfigurationFileError(path) mailman.interfaces.configuration.MissingConfigurationFileError: /etc/mailman3/mailman-hyperkitty.cfg
And it looks like the mailman-hyperkitty.cfg file is missing. Only, it isn't.
cat /etc/mailman3/mailman-hyperkitty.cfg
[general] base_url: http://127.0.0.1:8000/archives/ api_key: The realAPIkeyisDiff3r3nt
So, this really makes me feel dumb or even dumber...
Any ideas what might cause this?
wbr hank
Now it started to work. It seems that it is required that mailman user owns the /etc/mailman3/mailman-hyperkitty.cfg though mailmn.cfg doesn't seem to require it...
On Wed, Sep 25, 2024 at 1:19 PM <hnpilot@phnet.fi> wrote:
Now it started to work. It seems that it is required that mailman user owns the /etc/mailman3/mailman-hyperkitty.cfg though mailmn.cfg doesn't seem to require it...
The mailman user needs READ access to the files in /etc/mailman3/. Not ownership per se, as the user doesn't write to these files. If that was the real issue, then the error wasn't quite succinct about it.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
participants (2)
-
hnpilot＠phnet.fi -
Odhiambo Washington