On Wed, Jun 26, 2019, at 2:46 AM, andrew.bernard@gmail.com wrote:
Hi Mark. Indeed, I am confused. I am not yet familiar with Hyperkiity internals and code, and I must say it is currently like fog to me. :-)
Indeed, rebuild_mailinglist_cache_for_month made me think this was a monthly job.
I had made some lists and deleted them shortly thereafter. I managed to add some lines likes raise Exception(locals()) in some of the code, which revealed that a deleted list was being referred to. I have no idea how to purge this. I looked everywhere in every table in the database to find references to the deleted table, to no avail. I deleted all the queued, jobs in Django, to no avail. I rebooted three times to no avail (highly unscientific), And now, for no obvious reason, the error has stopped appearing. it definitely did not stop after deleting Django queued jobs - although perhaps something takes time to propagate, or there is something stuck cached in RAM?
It's nice that it stopped but I feel a bit uncomfortable that creating a list and deleting it a couple of hours later can cause the log to fill up every minute with these tracebacks. The exception raised in the code simply says <MailingList matching query does not exist>. It would be great if the error could name the list. I think that would be helpful. It would make it clearer to people what is happening at least, a lot faster. Python tracebacks don't show the values of local variables, unfortunately.
The delete functionality isn't completely implemented yet and part of the problem lies in the way MailingList, Thread and Email objects are created in Hyperkitty.
What you need to know is that once a MailingList has been created, several (routine and event based) tasks are added up in a queue. If at the time those tasks are ready to be executed, the mailinglist has gone away, it prints those errors. IMO, it is mostly harmless, but I can see so much of errors in logs would be worrisome to users.
Right now, errors are logged unconditionally, but it is possible to
filter them to skip MailingList does not exist errors altogether.
Ofcourse, that is not the ideal solution, but I think it should at least stop the exceptions from being logged when us or the user can't do anything about it.
Andrew
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)