On 8/6/25 18:17, Mark Sapiro wrote:
On 8/6/25 09:03, Jérôme Charaoui wrote:
I'm running a (rather large) mailman3 instance on Debian 13 (trixie)
using the distribution packages.
To manage the mailman3 daemon, the package installs this systemd
service unit:
https://sources.debian.org/src/mailman3/3.3.10-2/debian/mailman3.service/
It has been working fine until recently: after a reboot, we noticed
the mailman3 unit consistently failing to start due to a timeout error.
I figured out that the timeout was related to the service unit type
(Type=forking) and the fact that the main/parent process was forking
subprocesses (and running normally), writing a PID file, but it wasn't
exiting, so systemd identifies this as an error and aborts the service.
The master is not supposed to exit. It continues to run and monitor the
child runner processes and will under some circumstances restart a
runner that dies.
Further, our recommended systemd configuration is at
https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman-automatically
and includes `Type=forking` and this is the first I've heard of an issue
with that.
--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/[email protected]/message/YWSD5ZEQYRNUKKFIV2JJC3NPU6RY66AX/
This message sent to [email protected]
