Hey all,
so far we could not find the reason behind the problem. However while
reviewing the installation process one one our team mentioned that he
read the installation instructions for Hyperkitty different then the
rest of the team.
Are Mailman3/Postorius and Hyperkitty supposed to run in separated
databases, or are they supposed to use the same database?
Thanks in advance for clarification!
Tobias
On 06.11.24 08:18, Tobias Diekershoff wrote:
Hey all,
last week we caught some AI bots causing high LOAD on our mailman3
servers archive, that we blocked with nginx rules.
I'm not sure if it is related to this incident, but we noticed this
when analyzing the log files at the time. In the mailman.log
hyperkitty is listed 10k times and more to archive a single mail over
the time of 2h, seemingly all with the same process ID
> (1186) HyperKitty archived message [...]
The mailman3-web.log has matching log entries that the mail was archived
> hyperkitty.views.mailman Archived message
every 0.5 seconds.
In the web interface to the archive, the mail is only listed once though.
My suspicion is, that these archiving processes are now overloading
the system, preventing a timely catching up work of the queued
messages. I could not find anything in the Mailman3 nor Hyperkitty
documentation to better distribute the system resources to the Mailman
runner or prevent Hyperkitty to restart archiving a mail over and over
again.
Any hint about where to look for the reason of this is highly
appreciated.
Best,
Tobias
--
Tobias Diekershoff >>> System Hacker
Free Software Foundation Europe
Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290
Registered at Amtsgericht Hamburg, VR 17030 | fsfe.org/support
OpenPGP-Key ID ... 0x25FE376FF17694A1
Fingerprint ...... 23EE F484 FDF8 291C BA09
A406 25FE 376F F176 94A1
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/GO63BBTGHFVIJZW53BNTN5CQFORG43PX/
This message sent to arch...@mail-archive.com
