Mailman 3 Service and Troubleshooting - Revision history

LeWikiAdmin: /* Something is stuck in the Hyperkitty spool */

2024-12-02T12:59:33Z

Something is stuck in the Hyperkitty spool

@@ Line 16: / Line 16: @@
   tail -f /home/mailman/we.lurk.org/web/logs/*
   tail -f /var/log/nginx/*log
 === Something is stuck in the Hyperkitty spool ===
 Sometimes Hyperkitty does not like an email and won't be able to store it in its database. If that's the case there will be errors showing up both on the mailman3 and mailmanweb sides, notably about the relevant table/column in the mailman_web mariadb database that's struggling. Until this is solved the email will keep on being re-queued at <code>/home/mailman/we.lurk.org/mm/var/archives/hyperkitty/spool</code> and and new attempts to store the problematic email will happen ''every time'' the archiver is called, for instance when a new email is received on a list that has to be archived. This will not block the queue, just that the problem email will keep being tried over and over again until the problem is solved which can become quite expensive from a computational POV.

320x200: /* Something is stuck in the Hyperkitty spool */

2024-01-01T14:52:22Z

Something is stuck in the Hyperkitty spool

← Older revision		Revision as of 14:52, 1 January 2024
Line 22:		Line 22:

	To inspect an item stuck in the queue you can do this:		To inspect an item stuck in the queue you can do this:
	su mailman		su mailman # ALWAYS
	cd /home/mailman/we.lurk.org/mm/var/archives/hyperkitty/spool		cd /home/mailman/we.lurk.org/mm/var/archives/hyperkitty/spool
	mailman qfile 1234567890.1234567890.pck \| less		mailman qfile 1234567890.1234567890.pck \| less

320x200: /* Something is stuck in the Hyperkitty spool */

2024-01-01T14:51:04Z

Something is stuck in the Hyperkitty spool

← Older revision		Revision as of 14:51, 1 January 2024
Line 17:		Line 17:
	tail -f /var/log/nginx/*log		tail -f /var/log/nginx/*log

	== Something is stuck in the Hyperkitty spool ==		=== Something is stuck in the Hyperkitty spool ===

	Sometimes Hyperkitty does not like an email and won't be able to store it in its database. If that's the case there will be errors showing up both on the mailman3 and mailmanweb sides, notably about the relevant table/column in the mailman_web mariadb database that's struggling. Until this is solved the email will keep on being re-queued at <code>/home/mailman/we.lurk.org/mm/var/archives/hyperkitty/spool</code> and and new attempts to store the problematic email will happen ''every time'' the archiver is called, for instance when a new email is received on a list that has to be archived. This will not block the queue, just that the problem email will keep being tried over and over again until the problem is solved which can become quite expensive from a computational POV.		Sometimes Hyperkitty does not like an email and won't be able to store it in its database. If that's the case there will be errors showing up both on the mailman3 and mailmanweb sides, notably about the relevant table/column in the mailman_web mariadb database that's struggling. Until this is solved the email will keep on being re-queued at <code>/home/mailman/we.lurk.org/mm/var/archives/hyperkitty/spool</code> and and new attempts to store the problematic email will happen ''every time'' the archiver is called, for instance when a new email is received on a list that has to be archived. This will not block the queue, just that the problem email will keep being tried over and over again until the problem is solved which can become quite expensive from a computational POV.

320x200 at 14:50, 1 January 2024

2024-01-01T14:50:47Z

← Older revision		Revision as of 14:50, 1 January 2024
Line 16:		Line 16:
	tail -f /home/mailman/we.lurk.org/web/logs/*		tail -f /home/mailman/we.lurk.org/web/logs/*
	tail -f /var/log/nginx/*log		tail -f /var/log/nginx/*log

			== Something is stuck in the Hyperkitty spool ==

			Sometimes Hyperkitty does not like an email and won't be able to store it in its database. If that's the case there will be errors showing up both on the mailman3 and mailmanweb sides, notably about the relevant table/column in the mailman_web mariadb database that's struggling. Until this is solved the email will keep on being re-queued at <code>/home/mailman/we.lurk.org/mm/var/archives/hyperkitty/spool</code> and and new attempts to store the problematic email will happen ''every time'' the archiver is called, for instance when a new email is received on a list that has to be archived. This will not block the queue, just that the problem email will keep being tried over and over again until the problem is solved which can become quite expensive from a computational POV.

			To inspect an item stuck in the queue you can do this:
			su mailman
			cd /home/mailman/we.lurk.org/mm/var/archives/hyperkitty/spool
			mailman qfile 1234567890.1234567890.pck \| less

	=== Running mailman standalone ===		=== Running mailman standalone ===

320x200: 320x200 moved page Mailman 3 Service to Mailman 3 Service and Troubleshooting

2024-01-01T14:38:32Z

320x200 moved page Mailman 3 Service to Mailman 3 Service and Troubleshooting

← Older revision	Revision as of 14:38, 1 January 2024
(No difference)

320x200 at 14:37, 1 January 2024

2024-01-01T14:37:26Z

@@ Line 5: / Line 5: @@
   systemctl status mailmanweb # AKA hyperkitty, postorius, uwsgi, django hell, needed for the web interface
-== Manual Start and Restart ==
+== Troubleshooting ==
 '''Only do this when manually troubleshooting otherwise this will conflict with <code>systemctl</code> initiated services.'''
 * Mailman 3 relies on its own mailman user to handle the processing of the emails.
   su mailman     # switch to the mailman user
@@ Line 19: / Line 28: @@
   mailman stop         # stop mailman
   mailman restart      # stop and start mailman shorcut

320x200: /* Manual Start and Restart */

2024-01-01T14:35:33Z

Manual Start and Restart

← Older revision		Revision as of 14:35, 1 January 2024
Line 7:		Line 7:
	== Manual Start and Restart ==		== Manual Start and Restart ==

	Only do this when manually troubleshooting otherwise this will conflict with <code>systemctl</code> initiated services.		'''Only do this when manually troubleshooting otherwise this will conflict with <code>systemctl</code> initiated services.'''

	=== Basics ===		=== Basics ===
	* Mailman 3 relies on its own mailman user to handle the processing of the emails.		* Mailman 3 relies on its own mailman user to handle the processing of the emails.

320x200: /* Trouble shooting */

2024-01-01T14:34:32Z

Trouble shooting

← Older revision		Revision as of 14:34, 1 January 2024
Line 19:		Line 19:
	mailman restart # stop and start mailman shorcut		mailman restart # stop and start mailman shorcut

	== ~~Trouble shooting~~ ==		== Troubleshooting ==

	Don't think you can start understand anything without at least doing the following:		Don't think you can start understand anything without at least doing the following:

320x200 at 14:33, 1 January 2024

2024-01-01T14:33:42Z

← Older revision		Revision as of 14:33, 1 January 2024
Line 18:		Line 18:
	mailman stop # stop mailman		mailman stop # stop mailman
	mailman restart # stop and start mailman shorcut		mailman restart # stop and start mailman shorcut

			== Trouble shooting ==

			Don't think you can start understand anything without at least doing the following:
			* mailman core
			tail -f /home/mailman/we.lurk.org/mm/var/logs/*
			tail -f /var/log/mail.err /var/log/mail.log /var/log/mail.warn
			journalctl --follow _SYSTEMD_UNIT=mailman3.service + _SYSTEMD_UNIT=mariadb.service
			* web stuff
			tail -f /home/mailman/we.lurk.org/web/logs/*
			tail -f /var/log/nginx/*log


	==



	[[Category: Email]]		[[Category: Email]]

320x200 at 14:24, 1 January 2024

2024-01-01T14:24:28Z

← Older revision		Revision as of 14:24, 1 January 2024
Line 1:		Line 1:
	== Service Configuration and Installation ==		== Service Configuration and Installation ==

			There are two services needed:
			systemctl status mailman3 # AKA mailman-core you only need this for lists to work
			systemctl status mailmanweb # AKA hyperkitty, postorius, uwsgi, django hell, needed for the web interface

	== Manual Start and Restart ==		== Manual Start and Restart ==