On 11/28/24 9:17 AM, Alain D D Williams wrote:
/var/lib/mailman3/queue/out/ contains 4 .pck files and one .bak file. There are
being continually read & replaced by other files of similar names - like
1732809409.1069376+eb3354a0fc1f0a9bfa95ff7e15e2430ab7c2b885.pck
The process doing this is a 'qrunner'
The .bak file is the one currently being processed by the `out` runner.
The others are waiting to be sent.
I don't know why they are continually being dequeued and requeued I
suggest you stop Mailman core and then examine these files with `mailman
qfile` to see if there is some issue with one or more of them, but this
seems unlikely. More likely is some issue with the `out` runner itself,
but I have no idea what that would be except that issues like this can
be caused by files in Mailman's var/templates/ directory that aren't
readable by the Mailman user (often caused by running `mailman import21`
as root).
I am getting ~50 lines/second appended to /var/log/mailman3/web/mailman-web.log
[pid: 1348330|app: 0|req: 4366/4366] ::1 () {54 vars in 1065 bytes} [Thu Nov 28
17:02:18 2024] GET
/mailman3/hyperkitty/api/mailman/urls?mlist=chat%40bray.phcomp.co.uk&msgid=Z0iJAoTHHrzK2ypO%40phcomp.co.uk
=> generated 126 bytes in 3 msecs (HTTP/1.1 200) 7 headers in 220 bytes (1
switches on core 1)
This looks like some kind of DOS attack. Look at the GET requests in the
web server log.
/var/lib/mailman3/queue/shunt/ contains 4 .pck files.
For each of these, there should be an entry in mailman.log indicating
the exception with a traceback. Look for entries in the log ending with
a `SHUNTING` message.
--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/[email protected]/message/FJNT7KLD6XK65IYVEVAOS7FK5FNJRJF3/
This message sent to [email protected]
