This morning I upgraded the mailman3 installation of the less traffic server I have: a bunch of lists, with very slow traffic.
(see pip lists at the end)
I sent test mails to a pair of lists, but none were distributed or archived. postorius seemed working well. First I thought it was some I did wrong in the upgrade procedure, but then I realized the lmtp runner was not running.
I followed old messages about similar problem (many of them in this same mailman-users list), but I cannot see what is wrong. There is no error logged in mailman.log. the mailman.cfg of the lmtp is the default (and was working at least a pair of weeks ago)
*-*-*-*-*-*-*-*-* from mailman.cfg
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix
*-*-*-*-*-*-*-*-*
There is no one listening in port 8024. I tried changing the port (to 9024), with the same results.
postfix seems working well. I's just there is nothing listening on port 8024 because lmtp runner is not running :)
(from maillog):
connect to 127.0.0.1[127.0.0.1]:8024: Connection refused
(another simple test)
root@www:/usr/local/mailman3 # telnet localhost 8024 Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused
I'm running out of ideas. Any clue to somewhere to dig in?
*-*-*-*-*-*-*-*-*-*-* runners started
Apr 01 17:24:40 2023 (4681) out runner started. Apr 01 17:24:40 2023 (4680) virgin runner started. Apr 01 17:24:41 2023 (4679) command runner started. Apr 01 17:24:42 2023 (4688) retry runner started. Apr 01 17:24:43 2023 (4686) in runner started. Apr 01 17:24:44 2023 (4683) digest runner started. Apr 01 17:24:44 2023 (4684) nntp runner started. Apr 01 17:24:45 2023 (4682) archive runner started. Apr 01 17:24:46 2023 (4685) bounces runner started. Apr 01 17:24:47 2023 (4687) task runner started. Apr 01 17:24:47 2023 (4687) Task runner evicted 0 expired pendings Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned workflows Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned requests Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned messages Apr 01 17:24:47 2023 (4687) Task runner evicted expired cache entries Apr 01 17:24:48 2023 (4678) pipeline runner started. Apr 01 18:24:48 2023 (4687) Task runner evicted 0 expired pendings Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned workflows Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned requests Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned messages Apr 01 18:24:48 2023 (4687) Task runner evicted expired cache entries
*-*-*-*-*-*-*-*-*-* pip lists with versions installed
root@www:/usr/local/mailman3 # pip list | grep mailman django-mailman3 1.3.9 mailman 3.3.8 mailman-hyperkitty 1.2.1 mailmanclient 3.3.5
root@www:/usr/local/mailman3 # pip list | grep django django-allauth 0.51.0 django-appconf 1.0.5 django-compressor 4.0 django-extensions 3.2.0 django-gravatar2 1.4.4 django-haystack 3.2.1 django-mailman3 1.3.9 django-picklefield 3.1 django-q 1.3.9 djangorestframework 3.13.1
root@www:/usr/local/mailman3 # pip list | grep postorius postorius 1.3.8
--
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: firma-GHP-emails.png
Replaced multipart/alternative part with first alternative.
On Sat, Apr 1, 2023 at 7:55 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users@mailman3.org> wrote:
This morning I upgraded the mailman3 installation of the less traffic server I have: a bunch of lists, with very slow traffic.
(see pip lists at the end)
I sent test mails to a pair of lists, but none were distributed or archived. postorius seemed working well. First I thought it was some I did wrong in the upgrade procedure, but then I realized the lmtp runner was not running.
I followed old messages about similar problem (many of them in this same mailman-users list), but I cannot see what is wrong. There is no error logged in mailman.log. the mailman.cfg of the lmtp is the default (and was working at least a pair of weeks ago)
*-*-*-*-*-*-*-*-* from mailman.cfg
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix
*-*-*-*-*-*-*-*-*
There is no one listening in port 8024. I tried changing the port (to 9024), with the same results.
postfix seems working well. I's just there is nothing listening on port 8024 because lmtp runner is not running :)
(from maillog):
connect to 127.0.0.1[127.0.0.1]:8024: Connection refused
(another simple test)
root@www:/usr/local/mailman3 # telnet localhost 8024 Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused
I'm running out of ideas. Any clue to somewhere to dig in?
*-*-*-*-*-*-*-*-*-*-* runners started
Apr 01 17:24:40 2023 (4681) out runner started. Apr 01 17:24:40 2023 (4680) virgin runner started. Apr 01 17:24:41 2023 (4679) command runner started. Apr 01 17:24:42 2023 (4688) retry runner started. Apr 01 17:24:43 2023 (4686) in runner started. Apr 01 17:24:44 2023 (4683) digest runner started. Apr 01 17:24:44 2023 (4684) nntp runner started. Apr 01 17:24:45 2023 (4682) archive runner started. Apr 01 17:24:46 2023 (4685) bounces runner started. Apr 01 17:24:47 2023 (4687) task runner started. Apr 01 17:24:47 2023 (4687) Task runner evicted 0 expired pendings Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned workflows Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned requests Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned messages Apr 01 17:24:47 2023 (4687) Task runner evicted expired cache entries Apr 01 17:24:48 2023 (4678) pipeline runner started. Apr 01 18:24:48 2023 (4687) Task runner evicted 0 expired pendings Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned workflows Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned requests Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned messages Apr 01 18:24:48 2023 (4687) Task runner evicted expired cache entries
*-*-*-*-*-*-*-*-*-* pip lists with versions installed
root@www:/usr/local/mailman3 # pip list | grep mailman django-mailman3 1.3.9 mailman 3.3.8 mailman-hyperkitty 1.2.1 mailmanclient 3.3.5
root@www:/usr/local/mailman3 # pip list | grep django django-allauth 0.51.0 django-appconf 1.0.5 django-compressor 4.0 django-extensions 3.2.0 django-gravatar2 1.4.4 django-haystack 3.2.1 django-mailman3 1.3.9 django-picklefield 3.1 django-q 1.3.9 djangorestframework 3.13.1
root@www:/usr/local/mailman3 # pip list | grep postorius postorius 1.3.8
Bumping either mailman|lmtp loglevel to DEBUG might help find out.
[logging.lmtp] level: debug
And I think you can debug everything with (untested): [logging.here] level: debug
And restart mailman.
Maybe??
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
El 1/4/23 a las 20:05, Odhiambo Washington escribió:
Bumping either mailman|lmtp loglevel to DEBUG might help find out.
[logging.lmtp] level: debug
And I think you can debug everything with (untested): [logging.here] level: debug
And restart mailman.
Maybe??
Good shot. I'm gonna try it.
--
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: firma-GHP-emails.png
Replaced multipart/alternative part with first alternative.
On 4/1/23 09:55, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
postfix seems working well. I's just there is nothing listening on port 8024 because lmtp runner is not running :)
(from maillog):
connect to 127.0.0.1[127.0.0.1]:8024: Connection refused
(another simple test)
root@www:/usr/local/mailman3 # telnet localhost 8024 Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused
I'm running out of ideas. Any clue to somewhere to dig in?
*-*-*-*-*-*-*-*-*-*-* runners started
Apr 01 17:24:40 2023 (4681) out runner started. Apr 01 17:24:40 2023 (4680) virgin runner started. Apr 01 17:24:41 2023 (4679) command runner started. Apr 01 17:24:42 2023 (4688) retry runner started. Apr 01 17:24:43 2023 (4686) in runner started. Apr 01 17:24:44 2023 (4683) digest runner started. Apr 01 17:24:44 2023 (4684) nntp runner started. Apr 01 17:24:45 2023 (4682) archive runner started. Apr 01 17:24:46 2023 (4685) bounces runner started. Apr 01 17:24:47 2023 (4687) task runner started. Apr 01 17:24:47 2023 (4687) Task runner evicted 0 expired pendings Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned workflows Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned requests Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned messages Apr 01 17:24:47 2023 (4687) Task runner evicted expired cache entries Apr 01 17:24:48 2023 (4678) pipeline runner started. Apr 01 18:24:48 2023 (4687) Task runner evicted 0 expired pendings Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned workflows Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned requests Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned messages Apr 01 18:24:48 2023 (4687) Task runner evicted expired cache entries
lmtp runner did not start because at some point it had died and restarting Mailman won't restart a runner that died and was marked to not restart.
You need to stop Mailman and make sure when mailman is stopped that there are no files in mailman's var/locks/ directory (remove any that are there) and then start Mailman and lmtp runner should start.
As to why it died in the first place, there should be something in mailman.log from the time it died.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
El 1/4/23 a las 20:44, Mark Sapiro escribió:
... lmtp runner did not start because at some point it had died and restarting Mailman won't restart a runner that died and was marked to not restart.
You need to stop Mailman and make sure when mailman is stopped that there are no files in mailman's var/locks/ directory (remove any that are there) and then start Mailman and lmtp runner should start.
I stopped mailman and removed all that was in there (there were many locked registers). Restarted mailman, and it shows the same error that in my previous mail.
Now there is two new locked files, one (master.lck) which its content is the name of the other file. And the second one has the same content:
master.lck|www.proteccion-civil.eu|9389|7022761192045613065
will try deleting the content of var/locks and restarting the server
As to why it died in the first place, there should be something in mailman.log from the time it died.
--
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: firma-GHP-emails.png
Replaced multipart/alternative part with first alternative.
On 4/1/23 12:00, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
El 1/4/23 a las 20:44, Mark Sapiro escribió:
... lmtp runner did not start because at some point it had died and restarting Mailman won't restart a runner that died and was marked to not restart.
You need to stop Mailman and make sure when mailman is stopped that there are no files in mailman's var/locks/ directory (remove any that are there) and then start Mailman and lmtp runner should start.
I stopped mailman and removed all that was in there (there were many locked registers). Restarted mailman, and it shows the same error that in my previous mail.
Now there is two new locked files, one (master.lck) which its content is the name of the other file. And the second one has the same content:
master.lck|www.proteccion-civil.eu|9389|7022761192045613065
Those are the master lock that prevents Mailman core from starting when it is running. They should not be removed unless Mailman core is stopped.
will try deleting the content of var/locks and restarting the server
If you had completely stopped Mailman core and then started it, lmtp runner should have started. What are the complete log messages from mailman.log following the start?
What does mailman conf -s runner.lmtp show?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
El 1/4/23 a las 21:14, Mark Sapiro escribió:
On 4/1/23 12:00, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
El 1/4/23 a las 20:44, Mark Sapiro escribió:
... lmtp runner did not start because at some point it had died and restarting Mailman won't restart a runner that died and was marked to not restart.
You need to stop Mailman and make sure when mailman is stopped that there are no files in mailman's var/locks/ directory (remove any that are there) and then start Mailman and lmtp runner should start.
I stopped mailman and removed all that was in there (there were many locked registers). Restarted mailman, and it shows the same error that in my previous mail.
Now there is two new locked files, one (master.lck) which its content is the name of the other file. And the second one has the same content:
master.lck|www.proteccion-civil.eu|9389|7022761192045613065
Sorry, I sent my previous mail, and then received this
Those are the master lock that prevents Mailman core from starting when it is running. They should not be removed unless Mailman core is stopped.
Everytime I deleted that files I previously have stopped mailman, yes
will try deleting the content of var/locks and restarting the server
If you had completely stopped Mailman core and then started it, lmtp runner should have started. What are the complete log messages from mailman.log following the start?
I sent them before
What does
mailman conf -s runner.lmtpshow?
Here it is:
root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg conf -s runner.lmtp" [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner [runner.lmtp] instances: 1 [runner.lmtp] max_restarts: 10 [runner.lmtp] path: [runner.lmtp] sleep_time: 1s [runner.lmtp] start: yes
--
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: firma-GHP-emails.png
Replaced multipart/alternative part with first alternative.
On 4/1/23 12:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
El 1/4/23 a las 21:14, Mark Sapiro escribió:
If you had completely stopped Mailman core and then started it, lmtp runner should have started. What are the complete log messages from mailman.log following the start?
I sent them before
And there is no lmtp runner started message in the log, so it isn't
being started at all.
What does
mailman conf -s runner.lmtpshow?Here it is:
root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg conf -s runner.lmtp" [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner [runner.lmtp] instances: 1 [runner.lmtp] max_restarts: 10 [runner.lmtp] path: [runner.lmtp] sleep_time: 1s [runner.lmtp] start: yes
This says the runner should be started. That is the command that starts Mailman? is it
/usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg start"
or is it something that perhaps uses a different config.
What happens if you do
/usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp"
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
El 1/4/23 a las 21:38, Mark Sapiro escribió:
On 4/1/23 12:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
El 1/4/23 a las 21:14, Mark Sapiro escribió:
If you had completely stopped Mailman core and then started it, lmtp runner should have started. What are the complete log messages from mailman.log following the start?
I sent them before
And there is no
lmtp runner startedmessage in the log, so it isn't being started at all.What does
mailman conf -s runner.lmtpshow?Here it is:
root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg conf -s runner.lmtp" [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner [runner.lmtp] instances: 1 [runner.lmtp] max_restarts: 10 [runner.lmtp] path: [runner.lmtp] sleep_time: 1s [runner.lmtp] start: yes
This says the runner should be started. That is the command that starts Mailman? is it Yes, indeed.
/usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg start"
or is it something that perhaps uses a different config.
What happens if you do
/usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp"
I get the same error as before:
root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp" Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector Traceback (most recent call last): File "/usr/local/bin/runner", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', 'runner')()) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1128, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1053, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1395, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 754, in invoke return __callback(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 184, in main runner = make_runner(*runner_spec, once=once) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 70, in make_runner return runner_class(name, slice) File "/usr/local/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 295, in __init__ self.lmtp = LMTPController(LMTPHandler(), hostname=hostname, port=port) File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 417, in __init__ self._localhost = get_localhost() File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 66, in get_localhost with makesock(AF_INET6, SOCK_STREAM) as sock: File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported
--
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: firma-GHP-emails.png
Replaced multipart/alternative part with first alternative.
On 4/1/23 12:44, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I get the same error as before:
Did you post this traceback before? If so, I missed it.
root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp" Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector Traceback (most recent call last): File "/usr/local/bin/runner", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', 'runner')()) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1128, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1053, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1395, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 754, in invoke return __callback(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 184, in main runner = make_runner(*runner_spec, once=once) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 70, in make_runner return runner_class(name, slice) File "/usr/local/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 295, in __init__ self.lmtp = LMTPController(LMTPHandler(), hostname=hostname, port=port) File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 417, in __init__ self._localhost = get_localhost() File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 66, in get_localhost with makesock(AF_INET6, SOCK_STREAM) as sock: File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported
The issue is in aiosmtpd which is trying to determine if it can use IPv6 "::1" for localhost. It does this before it checks if we've provided a hostname which we have. The issue is in aiosmtp/controller.py in the get_localhost() function, but it's even deeper than that in socket which is raising the Protocol not supported error.
There is something strange on your server in that IPv6 seems to be only partially supported. I don't know for sure what the underlying issue is, but look at https://github.com/aio-libs/aiosmtpd/blob/master/aiosmtpd/controller.py#L49
Find aiosmtpd /controller.py in your venv/lib/python3.?/site-pacakages directory and change that
return has_ipv6line to
return Falseto work around the issue.
Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
El 1/4/23 a las 22:53, Mark Sapiro escribió:
On 4/1/23 12:44, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I get the same error as before:
Did you post this traceback before? If so, I missed it. Yes. I did. when I configured debug in mailman.cfg as Odhiambo sugested
... The issue is in aiosmtpd which is trying to determine if it can use IPv6 "::1" for localhost. It does this before it checks if we've provided a hostname which we have. The issue is in aiosmtp/controller.py in the get_localhost() function, but it's even deeper than that in socket which is raising the Protocol not supported error.
There is something strange on your server in that IPv6 seems to be only partially supported. I don't know for sure what the underlying issue is, but look at https://github.com/aio-libs/aiosmtpd/blob/master/aiosmtpd/controller.py#L49
Find aiosmtpd /controller.py in your venv/lib/python3.?/site-pacakages directory and change that
return has_ipv6
line to
return False
that did the trick
14477 - SJ 0:01.12 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=lmtp:0:1
And now the lists are working as should.
Thank you very very much. You are a saver.
to work around the issue.
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: firma-GHP-emails.png
Replaced multipart/alternative part with first alternative.
El 1/4/23 a las 23:13, Guillermo Hernandez (Oldno7) via Mailman-users escribió:
Thank you very very much. You are a saver. I meant savior. I'ts late here, sorry
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: firma-GHP-emails.png
Replaced multipart/alternative part with first alternative.
El 1/4/23 a las 21:00, Guillermo Hernandez (Oldno7) via Mailman-users escribió:
El 1/4/23 a las 20:44, Mark Sapiro escribió:
... lmtp runner did not start because at some point it had died and restarting Mailman won't restart a runner that died and was marked to not restart.
You need to stop Mailman and make sure when mailman is stopped that there are no files in mailman's var/locks/ directory (remove any that are there) and then start Mailman and lmtp runner should start.
I stopped mailman and removed all that was in there (there were many locked registers). Restarted mailman, and it shows the same error that in my previous mail.
Now there is two new locked files, one (master.lck) which its content is the name of the other file. And the second one has the same content:
master.lck|www.proteccion-civil.eu|9389|7022761192045613065
will try deleting the content of var/locks and restarting the server
same results lmtp runner is diying. Now I know thata part of the lock file is the pid of the master runner.
Apr 01 21:03:03 2023 (11548) Master started
Apr 01 21:03:11 2023 (11563) virgin runner started. Apr 01 21:03:13 2023 (11553) bounces runner started. Apr 01 21:03:14 2023 (11561) retry runner started. Apr 01 21:03:15 2023 (11560) rest runner started. [2023-04-01 21:03:15 +0200] [11560] [INFO] Starting gunicorn 20.1.0 [2023-04-01 21:03:15 +0200] [11560] [INFO] Listening at: http://10.0.1.42:8001 (11560) [2023-04-01 21:03:15 +0200] [11560] [INFO] Using worker: sync [2023-04-01 21:03:15 +0200] [11567] [INFO] Booting worker with pid: 11567 [2023-04-01 21:03:15 +0200] [11568] [INFO] Booting worker with pid: 11568 Apr 01 21:03:16 2023 (11564) digest runner started. Apr 01 21:03:17 2023 (11562) task runner started. Apr 01 21:03:17 2023 (11562) Task runner evicted 0 expired pendings Apr 01 21:03:17 2023 (11562) Task runner deleted 0 orphaned workflows Apr 01 21:03:17 2023 (11562) Task runner deleted 0 orphaned requests Apr 01 21:03:17 2023 (11562) Task runner deleted 0 orphaned messages Apr 01 21:03:17 2023 (11562) Task runner evicted expired cache entries Apr 01 21:03:18 2023 (11559) pipeline runner started. Apr 01 21:03:19 2023 (11555) in runner started. Apr 01 21:03:19 2023 (11554) command runner started. Apr 01 21:03:20 2023 (11558) out runner started. Apr 01 21:03:22 2023 (11557) nntp runner started. Apr 01 21:03:23 2023 (11552) archive runner started.
a ps ax output:
11548 - IsJ 0:01.92 /usr/local/bin/python3.9 /usr/local/bin/master --force -C /usr/local/mailman3/var/etc/mailman.cfg 11552 - SJ 0:01.97 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=archive:0:1 11553 - IJ 0:02.10 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=bounces:0:1 11554 - SJ 0:01.94 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=command:0:1 11555 - SJ 0:01.94 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=in:0:1 11556 - ZJ 0:02.21 <defunct> 11557 - SJ 0:01.95 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=nntp:0:1 11558 - SJ 0:01.93 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=out:0:1 11559 - SJ 0:01.94 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=pipeline:0:1 11560 - SJ 0:02.02 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=rest:0:1 11561 - IJ 0:01.94 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=retry:0:1 11562 - IJ 0:02.02 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=task:0:1 11563 - SJ 0:01.95 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=virgin:0:1 11564 - SJ 0:01.93 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=digest:0:1 11567 - IJ 0:00.01 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=rest:0:1 11568 - IJ 0:00.01 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=rest:0:1
As to why it died in the first place, there should be something in mailman.log from the time it died.
--
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: firma-GHP-emails.png
Replaced multipart/alternative part with first alternative.
participants (3)
-
Guillermo Hernandez (Oldno7) -
Mark Sapiro -
Odhiambo Washington