Date: Mon, 12 Jan 2026 12:12:14 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 292185] mail/mailman3: service mailman restart doesn't truly restart Message-ID: <bug-292185-7788-xBFPacIl3W@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-292185-7788@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292185 --- Comment #2 from Einar Bjarni Halldórsson <einar@isnic.is> --- (In reply to takeda from comment #0) Hi Takeda, The rc.d script for mailman is very simple, in that it just runs `mailman CMD` for CMD=['start', 'restart', 'stop', 'status', 'info']. `service mailman restart` does restart the master daemon, which in turn restarts all child processes. From mailman log during restart: Jan 12 12:03:07 2026 (836) Master watcher caught SIGUSR1. Restarting. Jan 12 12:03:07 2026 (47163) task runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47166) pipeline runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47168) virgin runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47169) bounces runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47170) digest runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47171) retry runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47172) out runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47173) lmtp runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47174) command runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47175) archive runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47176) in runner caught SIGUSR1. Stopping. Jan 12 12:03:07 2026 (47163) task runner exiting. Jan 12 12:03:07 2026 (47166) pipeline runner exiting. Jan 12 12:03:07 2026 (47168) virgin runner exiting. Jan 12 12:03:07 2026 (47169) bounces runner exiting. Jan 12 12:03:07 2026 (47170) digest runner exiting. Jan 12 12:03:07 2026 (47171) retry runner exiting. Jan 12 12:03:07 2026 (47172) out runner exiting. Jan 12 12:03:07 2026 (47173) lmtp runner exiting. [2026-01-12 12:03:07 +0000] [885] [INFO] Handling signal: usr1 Jan 12 12:03:07 2026 (47174) command runner exiting. Jan 12 12:03:07 2026 (47175) archive runner exiting. Jan 12 12:03:07 2026 (47176) in runner exiting. Jan 12 12:03:19 2026 (47361) bounces runner started. Jan 12 12:03:19 2026 (47364) task runner started. Jan 12 12:03:19 2026 (47355) command runner started. Jan 12 12:03:19 2026 (47364) Task runner evicted 0 expired pendings Jan 12 12:03:19 2026 (47363) pipeline runner started. Jan 12 12:03:19 2026 (47364) Task runner deleted 0 orphaned workflows Jan 12 12:03:19 2026 (47354) lmtp runner started. Jan 12 12:03:19 2026 (47359) out runner started. Jan 12 12:03:19 2026 (47364) Task runner deleted 0 orphaned requests Jan 12 12:03:19 2026 (47364) Task runner deleted 0 orphaned messages Jan 12 12:03:19 2026 (47364) Task runner deleted 0 orphaned message files Jan 12 12:03:19 2026 (47362) virgin runner started. Jan 12 12:03:19 2026 (47364) Task runner evicted 0 expired bounce events Jan 12 12:03:19 2026 (47364) Task runner evicted expired cache entries Jan 12 12:03:19 2026 (47357) in runner started. Jan 12 12:03:19 2026 (47360) retry runner started. Jan 12 12:03:20 2026 (47356) digest runner started. Jan 12 12:03:20 2026 (47358) archive runner started. The ark.is.kit.ac.jp link you provided mentions > sometimes the changes do not take effect until I cpmpletely restart services such as uwsgi, apache, mailman, etc. So, if you're using apache + uwsgi to serve the http interface for mailman, you might have to restart *those* services as well. I don't there's anything to gain from completely stopping mailman and starting it up again. If there is, it's an upstream problem with the mailman restart command. I did notice one problem with the rc.d script I'm going to try to fix, which is that `mailman start` throws an error if it's alrady running. It should just exit, or at most alert that it's already running and then exit -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-292185-7788-xBFPacIl3W>