On 5/28/20 8:06 AM, brylon@oit.rutgers.edu wrote:
Yes, I've stopped/started Mailman (quite a few times).
Is there a particular order to undo Hyperkitty and re-do? Or perhaps add some debug lines to a particular file to get at the root cause?
I'm not certain, but I don't think your issue has anything to do with the installation of HyperKitty itself. From the OP, the issue occurs in REST upon a get of /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers which is probably coming from Postorius -> Settings -> Archiving.
The actual error occurs in Core trying to process that request, and while it clearly has to do with archiving configuration, I don't think the installation of Hyperkitty is the issue.
What happens if you set
[archiver.hyperkitty] enable: no
and restart Mailman?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan