> and throwing this error in the mailman log "Exception in > the HyperKitty archiver: 413 Request Entity Too Large"
I think a similar issue was reported last week, and Mark is more familiar with it. I seem to remember that it's possible that the message in question is a spam and has non-ASCII characters in the header or body of the message, which violates the email RFCs. Maybe if you move the oldest message in $var_dir/queue/archive (or maybe $var_dir/archiver/hyperkitty/spool) to $var_dir/queue/bad for later inspection things will start running again. There is only 1 .pck file in $var_dir/archiver/hyperkitty/spool and it is only 3.5M - Is there a way I can see what this pck file is? Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Thu, Jan 30, 2025 at 12:09 PM Stephen J. Turnbull < turnb...@sk.tsukuba.ac.jp> wrote: > Arte Chambers via Mailman-users writes: > > > Hello I need help troubleshooting a problem with MM. The service is > > stopping > > If you mean the message quoted below, the Mailman daemons are not > stopping. You need to check the "Active", "Main PID", and "CGroup" > fields of "systemctl status mailman3.service", or run "mailman status" > directly to determine if Mailman is actually running properly or not. > > > and throwing this error in the mailman log "Exception in > > the HyperKitty archiver: 413 Request Entity Too Large" > > I think a similar issue was reported last week, and Mark is more > familiar with it. I seem to remember that it's possible that the > message in question is a spam and has non-ASCII characters in the > header or body of the message, which violates the email RFCs. Maybe > if you move the oldest message in $var_dir/queue/archive (or maybe > $var_dir/archiver/hyperkitty/spool) to $var_dir/queue/bad for later > inspection things will start running again. > > > System CTL has this message and i'm not sure if it's relevant to > > the issue. > > ``` > > sudo systemctl status mailman3.service > > systemd[1]: mailman3.service: Can't open PID file > > /opt/mailman/mm/var/master.pid (yet?) after start: No such file or > directory > > ``` > > This isn't relevant. The initial 'mailman' process spawns a 'master' > process then shuts down. 'master' takes enough time to get rolling > that systemd can't find its pid file when 'mailman' shuts down, and > systemd is too impatient to wait. That snippet is taken from the > systemd journal, and does not reflect current status. > > > The MM Service will run for a while then shuts down. > > This is probably normal, as explained above, unless you mean that > "systemctl status mailman3.service" or "mailman status" reports that > Mailman is not running. That should have some explanation in > $log_dir/mailman. > > Steve > _______________________________________________ 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/CXY3IUSNOJCGBKFAUF4GPZAJYBVMJTBN/ This message sent to arch...@mail-archive.com
