On 6/9/20 7:24 AM, Kareem Zidane wrote:
We're facing a similar symptom where emails to a particular list won't go out and seem to be stuck in the out queue. We also noticed that mailman is hitting /hyperkitty/api/mailman/urls infinitely. I've attached some of strace's output. Any idea what might be the problem?
Process 17171 attached ioctl(20, FIONBIO, [0]) = 0 sendto(20, "\272\10\0\0\3SELECT anon_1.member_id AS "..., 2238, 0, NULL, 0) = 2238 ioctl(20, FIONBIO, [0]) = 0 recvfrom(20, "\1\0\0\1\f5\0\0\2\3def\0\6anon_1\0\20anon_1_me"..., 8192, 0, NULL, NULL) = 937 ioctl(20, FIONBIO, [0]) = 0 ioctl(20, FIONBIO, [0]) = 0 ioctl(20, FIONBIO, [0]) = 0 ioctl(20, FIONBIO, [0]) = 0 ...
There is way too much noise in that strace for me to find anything useful without having more of a clue as to what I'm looking for. And what process is 17171?
As far as messages stuck in out, is Mailman's out runner running?
for example, $ ps -fwwA|grep [r]unner=out mailman 6318 6272 0 Jun08 ? 00:03:28 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=out:0:1
Look in Mailman's mailman.log for messages mentioning out runner and
for any error messages.
As for mailman is hitting /hyperkitty/api/mailman/urls infinitely look
for messages in mailman.log mentioning this.
Are there messages queued in /opt/mailman/var/archives/hyperkitty/spool?
if so, these are messages that failed archiving, probably because of an
incorrect value for base_url in mailman-hyperkitty.cfg or a mismatch
between api_key in mailman-hyperkitty.cfg and MAILMAN_ARCHIVER_KEY in
your Django settings.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan