--On Monday, June 26, 2023 5:03 PM -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 6/25/23 10:57 PM, Ken Alker wrote:
I have studied the output, looked at the code lines referenced in the Traceback, and I can't figure out the problem (I feel like the sad guy on the side of the street with his hood up staring into the engine bay with stream pouring out and not knowing what to do next). I did some analyses on the log file and determined that there are 71 messages it is having problems processing and there are 71 messages "stuck" in /opt/mailman/mm/var/archives/hyperkitty/spool/ (and that it has tried to process each message about 20 times).
Each time there is a new post, it retries all the messages in the spool/ directory.
Since upgrading to V3.3.8 I've not seen new messages get stuck like this (although it's only been running smoothly for 24 hours now and there hasn't been much activity). But I'm suspecting there was something awry between the conversion from V2 to V3 in February and me installing V3.3.8 that caused this (based on message time stamps). It is HIGHLY likely these messages are in the archiving spool as a result of me unshunting the shunt queue and that they are copies of the messages that got delivered to the subscribers when I did that... but are now hung up in the archiving process.
Are new messages being archived OK. If so, that is a real mystery. It says mailman-hyperkitty can talk to hyperkitty and archive new messages, but it can't talk to hyperkitty when attempting to process a queued message.
Ahhh! I had convinced myself that new messages were being archived, but now that you ask, they ARE NOT. I may have said they were at some point, and I apologize if I did. Now I feel less confused.
It appears that archiving stopped when I did the migration from "Debian package layout" to "source layout" and upgraded to V3.3.8. I'll bet I munged a config file or two. I was struggling with what to keep from Debian layout and what to bring over from the source install instructions and I haven't gone back through to clean them up. I had previously figured it could not be a configuration issue since some messages were making it into the archive and some were not, but now that I see NONE are making it, this makes the problem less daunting.
Following is an excerpt from mailman.log. Note that the "first section" (from DOCTYPE at top to 404 at bottom) is repeated four times (maybe not identical; but similar) (so I did not include it to save room) before the Traceback appears.
Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list found Jun 25 00:13:04 2023 (386086) ACCEPT: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a@west.net> Jun 25 00:13:04 2023 (386090) HyperKitty failure on https://lists.netlojix.com/hyperkitty/api/mailman/urls:
I just went to that URL and got a 404. This is a serious problem. https://lists.netlojix.com/hyperkitty/api/ also returns a 404. It should return some documentation of the API.
https://lists.netlojix.com/archives/api/ does work and returns the expected information.
Your urls.py file probably contains in its urlpatterns list
re_path(r'^mailman3/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')),The simplest fix is to add
re_path(r'^postorius/', include('postorius.urls')), re_path(r'^hyperkitty/', include('hyperkitty.urls')),to that list.
I see many ursl.py files all over the system, but none that appear to be where I'd expect them to be for processing by any executables. Is this a file I should have copied over and edited, or created from scratch and somehow missed? I don't see anything about it in the instructions at <https://docs.mailman3.org/en/latest/install/virtualenv.html> (although I do see a post from last July from someone stating it got missed in the instructions back then).
Another way to fix this is in your mailman-hyperkitty.cfg, you have
base_url: https://lists.netlojix.com/hyperkittyChange that to
base_url: https://lists.netlojix.com/archives
Done, and restarted both services, but I'm not seeing a difference when I go to <https://lists.netlojix.com/hyperkitty/api/> (I was getting a "Page not found", and still get that).
but it wouldn't hurt to add the
^postorius/and^hyperkitty/patterns to urls.py anyway.