mailman 3 adding extraneous /var/ to pid path?
I'm not sure if this is a bug, or if I've configured something I'm unable to find doing this. But when I'm attempting to stop my mailman3 process, I keep getting an extra /var/ appending into the pid path, so it never finds the PID to terminate.
Here are some examples, run at different times, some with different -C configs to launch, all worked successfully to start, this is only a problem on the stop.:
(venv3) [root@mailman3(on1) venv3]# mailman stop Shutting down Mailman's master runner PID unreadable in: /opt/mailman/venv3/var/master.pid [Errno 2] No such file or directory: '/opt/mailman/venv3/var/master.pid' Is the master even running?
(venv3) [root@mailman3(on1) var]# mailman stop Shutting down Mailman's master runner PID unreadable in: /opt/mailman/var/var/master.pid [Errno 2] No such file or directory: '/opt/mailman/var/var/master.pid'
(venv3) [root@mailman3(on1) var]# mailman stop Shutting down Mailman's master runner PID unreadable in: /opt/mailman/var/etc/var/var/master.pid [Errno 2] No such file or directory: '/opt/mailman/var/etc/var/var/master.pid'
I keep getting around this by creating symlinks to the pid file and then the stop works, but it's getting silly. It seems like mailman just assumes CWD + /var/ + master.pid must be the location. Once I realized this, I found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since it'd then add /var/master.pid). But that seems a little nonsensical.
Going to try my hand at using the environment variables MAILMAN_CONFIG_FILE and MAILMAN_VAR_DIR, maybe that will sort this out. But if anyone can explain further, it'd be appreciated.
Sincerely,
Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew@afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541
On 09/21/2017 01:29 PM, Andrew Hodder wrote:
I keep getting around this by creating symlinks to the pid file and then the stop works, but it's getting silly. It seems like mailman just assumes CWD + /var/ + master.pid must be the location. Once I realized this, I found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since it'd then add /var/master.pid). But that seems a little nonsensical.
That is the normal expected behavior if devmode is enabled. Check your configs for this.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Thu, Sep 21, 2017, at 02:42 PM, Mark Sapiro wrote:
On 09/21/2017 01:29 PM, Andrew Hodder wrote:
I keep getting around this by creating symlinks to the pid file and then the stop works, but it's getting silly. It seems like mailman just assumes CWD + /var/ + master.pid must be the location. Once I realized this, I found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since it'd then add /var/master.pid). But that seems a little nonsensical.
That is the normal expected behavior if devmode is enabled. Check your configs for this.
I don't think devmode has anything to do with this, it only disables
sending out emails by accident and routes all emails to a pre-defined
address. Haven't looked at the relevant portion of the source so I might
be wrong.
In the absence of any configuration file in pre-defined locations1,
Core will always generate a var/ directory under $CWD with basic
configuration and use it to track a running mailman instance (logs, db,
pid file etc).
Ideally, you should place your configuration file at one of the
locations that it looks and specify a [paths.custom] directive in
there to make sure it knows where to put everything. See 2 for more
details.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Abhilash Raj maxking@asynchronous.in
On Sep 21, 2017, at 18:35, Abhilash Raj <maxking@asynchronous.in> wrote:
On Thu, Sep 21, 2017, at 02:42 PM, Mark Sapiro wrote:
On 09/21/2017 01:29 PM, Andrew Hodder wrote:
I keep getting around this by creating symlinks to the pid file and then the stop works, but it's getting silly. It seems like mailman just assumes CWD + /var/ + master.pid must be the location. Once I realized this, I found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since it'd then add /var/master.pid). But that seems a little nonsensical.
That is the normal expected behavior if devmode is enabled. Check your configs for this.
I don't think
devmodehas anything to do with this, it only disables sending out emails by accident and routes all emails to a pre-defined address. Haven't looked at the relevant portion of the source so I might be wrong.
That’s correct.
The [paths.*] sections are what control the file system layout, and [mailman]layout is what defines which of the [paths.*] sections to use.
Cheers, -Barry
participants (4)
-
Abhilash Raj -
Andrew Hodder -
Barry Warsaw -
Mark Sapiro