Mailman3 crashes on restart
After restarting my mail server mailman3 does not start any more.
Mailman3 in on a debian 10.
I upgraded the django packets but no result.
This the syslog output.
Feb 17 17:00:24 posta mailman3[21303]: Traceback (most recent call last): Feb 17 17:00:24 posta mailman3[21303]: File "/usr/bin/mailman", line 11, in <module> Feb 17 17:00:24 posta mailman3[21303]: load_entry_point('mailman==3.2.1', 'console_scripts', 'mailman')() Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ Feb 17 17:00:24 posta mailman3[21303]: return self.main(*args, **kwargs) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main Feb 17 17:00:24 posta mailman3[21303]: rv = self.invoke(ctx) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 69, in invoke Feb 17 17:00:24 posta mailman3[21303]: return super().invoke(ctx) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke Feb 17 17:00:24 posta mailman3[21303]: return _process_result(sub_ctx.command.invoke(sub_ctx)) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke Feb 17 17:00:24 posta mailman3[21303]: return ctx.invoke(self.callback, **ctx.params) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke Feb 17 17:00:24 posta mailman3[21303]: return callback(*args, **kwargs) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/decorators.py", line 17, in new_func Feb 17 17:00:24 posta mailman3[21303]: return f(get_current_context(), *args, **kwargs) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 81, in start Feb 17 17:00:24 posta mailman3[21303]: status, lock = master_state() Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/mailman/bin/master.py", line 104, in master_state Feb 17 17:00:24 posta mailman3[21303]: os.kill(pid, 0) Feb 17 17:00:24 posta mailman3[21303]: PermissionError: [Errno 1] Operation not permitted Feb 17 17:00:24 posta systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Feb 17 17:00:24 posta systemd[1]: mailman3.service: Failed with result 'exit-code'.
Any idea? What have I to check?
Thanks
-- Gelpi ing. Andrea
I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli.
On 2/17/21 11:05 AM, Gelpi Andrea wrote:
Feb 17 17:00:24 posta mailman3[21303]: os.kill(pid, 0) Feb 17 17:00:24 posta mailman3[21303]:*PermissionError: [Errno 1] Operation not permitted* Feb 17 17:00:24 posta systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Feb 17 17:00:24 posta systemd[1]: mailman3.service: Failed with result 'exit-code'.
It is a permission issue I believe, not a Django. How are you starting Mailman 3 and under what user?
-- Brian Carpenter Harmonylists.com Emwd.com
Il 17/02/21 17:08, Brian Carpenter ha scritto:
On 2/17/21 11:05 AM, Gelpi Andrea wrote:
Feb 17 17:00:24 posta mailman3[21303]: os.kill(pid, 0) Feb 17 17:00:24 posta mailman3[21303]:*PermissionError: [Errno 1] Operation not permitted* Feb 17 17:00:24 posta systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Feb 17 17:00:24 posta systemd[1]: mailman3.service: Failed with result 'exit-code'.
It is a permission issue I believe, not a Django. How are you starting Mailman 3 and under what user?
Thank You for your quickly response. Mailman3 is started by the systems defaults
Systemctl mailman3 start
I don't know wich user. The default I suppose.
-- Gelpi ing. Andrea
I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli.
Il 17/02/21 17:17, Gelpi Andrea ha scritto:
Il 17/02/21 17:08, Brian Carpenter ha scritto:
On 2/17/21 11:05 AM, Gelpi Andrea wrote:
Feb 17 17:00:24 posta mailman3[21303]: os.kill(pid, 0) Feb 17 17:00:24 posta mailman3[21303]:*PermissionError: [Errno 1] Operation not permitted* Feb 17 17:00:24 posta systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Feb 17 17:00:24 posta systemd[1]: mailman3.service: Failed with result 'exit-code'.
It is a permission issue I believe, not a Django. How are you starting Mailman 3 and under what user?
Thank You for your quickly response. Mailman3 is started by the systems defaults
Systemctl mailman3 start
I don't know wich user. The default I suppose.
For some unknown reason in /var/lib/mailman3/lock there was a file master.lck.
I simply rename it and now mailman3 starts.
-- Gelpi ing. Andrea
I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli.
On 17/2/21 18:11, Gelpi Andrea wrote:
Il 17/02/21 17:17, Gelpi Andrea ha scritto:
Il 17/02/21 17:08, Brian Carpenter ha scritto:
On 2/17/21 11:05 AM, Gelpi Andrea wrote:
Feb 17 17:00:24 posta mailman3[21303]: os.kill(pid, 0) Feb 17 17:00:24 posta mailman3[21303]:*PermissionError: [Errno 1] Operation not permitted* Feb 17 17:00:24 posta systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Feb 17 17:00:24 posta systemd[1]: mailman3.service: Failed with result 'exit-code'. It is a permission issue I believe, not a Django. How are you starting Mailman 3 and under what user?
Thank You for your quickly response. Mailman3 is started by the systems defaults
Systemctl mailman3 start
I don't know wich user. The default I suppose.
For some unknown reason in /var/lib/mailman3/lock there was a file master.lck.
I simply rename it and now mailman3 starts.
It happens when mailman doesn't close cleanly. You can use the --force param to start it and avoid the lock.
Guillermo Hernandez (Oldno7) via Mailman-users writes:
On 17/2/21 18:11, Gelpi Andrea wrote:
For some unknown reason in /var/lib/mailman3/lock there was a file master.lck.
I simply rename it and now mailman3 starts.
It happens when mailman doesn't close cleanly. You can use the --force param to start it and avoid the lock.
Thanks, Guillermo!
Notes: The lockfile should be an invisible implementation detail, but it isn't for historical reasons. I think simply removing the lock is safe for Mailman currently, but when a "--force" (better name would be "--override-locks") option is available, please use it. And if you don't know, check. The option, being built in to the application, will try to avoid any pitfalls of the brute-force approach.
Steve
participants (4)
-
Brian Carpenter -
Gelpi Andrea -
Guillermo Hernandez (Oldno7) -
Stephen J. Turnbull