--On Sunday, June 25, 2023 1:14 PM -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 6/25/23 11:04 AM, Ken Alker wrote:
I've just taken on the project so I'm new to all of this, and one thing I noticed that caught my eye, and has left me curious, is that for the first a couple of seconds starting just after midnight every night (just after log rotation) mailman.log would have many (dozens, or hundreds) of lines entered in it just like this one:
Jun 19 00:00:04 2023 (2266) 127.0.0.1 - - "GET /3.0/users/old-user@domain.tld HTTP/1.1" 404 58
where "old-user@domain.tld" is the email address of a user who either had unsubscribed or changed their email address (I don't know which, I just know they are no longer a member/subscriber to the list). Each successive entry in the log would have a different "old username" in it. I don't understand why these entries would be in the log and what they mean. Can someone shed some light on this for me? This is merely a question of curiosity, and not one of import. (Since migrating from 3.2.2 to 3.3.8 this behavior has stopped, be that GOOD or BAD.)
This is the Django hyperkitty sync_mailman job which is one of the django admin jobs run daily. It goes through the HyperKitty 'sender' database table and tries to find the Mailman core user id for each sender address to add/update its mailman_id field with core's user_id.
The 404s are addresses im HyperKitty's sender table for whih there is no corresponding Mailman user. There are multiple possible reasons for this.
And that is OK, right?
If the behavior has stopped it's probably because the periodic Django jobs are not being run - this is bad.
I see this in the logs from just after midnight:
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:
Followed by a huge amount of HTML (strange).
I'm not sure if the first and last (third) lines in the log excerpt above are due to the same thing. I know why the public suffix list is not found; when I was migrating all my queues from the Debian layout to the "source install" layout, I could not figure out where it should go in the new world order. Can you tell me where it would normally be found on a fresh source install? I'll move it there.
Is there a way to kick it into re-running whatever it does at midnight so I can test this again after putting the public suffix list back? I assume I can just execute "mailman-web runjobs daily", but will this mess things up, or is it OK to run it mid-day without stopping anything first?
Is the last (third) log line excerpt simply a result of the first, or do I have something else messed up?
Thank you! Ken