On Wed, May 25, 2022 at 08:10:39AM -0700, Mark Sapiro wrote:
On 5/23/22 11:11, Darren Hart via Mailman-users wrote:
When attempting to visit the hyperkitty archives list overview for one of my two lists:
Https://lists.mydomain.com/hyperkitty/list/mylist@mydomain.com/
The area where the threads should appear shows the loading spinner (but the activity summary bar chart and most active posters post counts do eventually load).
The following appears in /var/log/mailman3/web/mailman-web.log:
ERROR 2022-05-23 17:50:50,201 1694 django.request Internal Server Error: /hyperkitty/list/mylist@mydomain.com/posted-to Traceback (most recent call last): ... File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get raise self.model.DoesNotExist( hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist.
Viewing “All Threads” or Threads by month (any month) work as expected, displaying the appropriate threads.
The archives for this list worked previously. There was an incident that resulted in DNS not working and the archiver failing for a few days. The mail that came in during that time does show up in the other views.
The hyper kitty archives for a second list on this Mailman3 instance is working correctly.
How can I fix this view of the archives? Or how can I get more information on what might be failing?
I'm not sure if this will help, but try running your django management command with arguments
runjob recent_threads_cache. Note that this will be run daily if you are running the Cron Jobs for Mailman Web. See https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=period...
Thank you Mark. These are in cron, but I ran this (and all the runjobs hourly,daily, etc. options), checking after each. The failure persisted until I restarted mailman3-web, and then it started working again. I'm not sure what combination of cron jobs and restarting resolved the issue, but it's running again. Thanks again.
-- Darren Hart Ampere Computing / OS and Kernel