Thank you Mark. This solution worked fine for me.
On Sun, Mar 27, 2022 at 9:58 AM Mark Sapiro <mark@msapiro.net> wrote:
On 3/26/22 21:01, Shashikanth Komandoor wrote:
But the below trace back is observed during mailman service stopping:
This doesn't say much ...
...> Mar 27 09:01:22 2022 (5864) Uncaught runner exception:
Mar 27 09:01:22 2022 (5864) Traceback (most recent call last): File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 173, in _one_iteration ... File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 114, in signal_handler raise RunnerInterrupt mailman.interfaces.runner.RunnerInterrupt Mar 27 09:01:22 2022 (5864) SHUNTING: 1648351882.6693938+ c2e6ed709646a7680c73059b52d2f0451836e591 Mar 27 09:01:22 2022 (5864) digest runner exiting.
Above, digest runner was interrupted in processing and shunted the message it was working on.
and below, pipeline runner was interrupted in processing and shunted the message it was working on.
Mar 27 09:01:22 2022 (5860) Uncaught runner exception: Mar 27 09:01:22 2022 (5860) Traceback (most recent call last): File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/var/lib/mailman/venv/lib64/python3.6/site-packages/ mailman/handlers/member_recipients.py", line 84, in process for member in mlist.regular_members.members File "/var/lib/mailman/venv/lib64/python3.6/site-packages/ mailman/handlers/member_recipients.py", line 83, in <genexpr> recipients = set(member.address.email File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/roster.py", line 239, in members yield from self._get_members(DeliveryMode.regular) File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/roster.py", line 226, in _get_members if member.delivery_mode in delivery_modes: File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/member.py", line 205, in delivery_mode return self._lookup('delivery_mode') File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/member.py", line 167, in _lookup pref = getattr(self.address.preferences, preference) File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", line 287, in __get__ return self.impl.get(instance_state(instance), dict_) File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", line 723, in get value = self.callable_(state, passive) File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", line 760, in _load_for_state session, state, primary_key_identity, passive File "<string>", line 1, in <lambda> File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", line 850, in _emit_lazyload session.query(self.mapper), primary_key_identity File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/ext/baked.py", line 603, in _load_on_pk_identity setup, tuple(elem is None for elem in primary_key_identity)
The above says the runner was doing a database lookup. This may be a coincidence or there may be some database locking issue that underlies the issue with the pipeline runner.
File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 114, in signal_handler raise RunnerInterrupt mailman.interfaces.runner.RunnerInterrupt Mar 27 09:01:22 2022 (5860) SHUNTING: 1648351882.8537986+ 9bf59cb23a71a4bae65536bfdbec0abb261adaa0 Mar 27 09:01:22 2022 (5860) pipeline runner exiting.
I suggest doing the following assuming your Mailman database is not sqlite3 (if it is, just do step 2):
- Stop mailman core and maybe other mailman services too.
- Assuming the two shunted messages are still in Mailman's shunt queue, run
mailman unshuntto unshunt them. If there are more shunted messages, inspect them withmailman qfileto see if you want them, They may be spam.- Restart your database server.
- Start Mailman core and any other stopped services.
Also, look in the database server logs for any issues.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Thanks & Regards, Shashi Kanth.K 9052671936