clarifying configuration
Hey Team, I'm new to Mailman and after some failed attempts to install from git on CentOS8, I have just installed it on Ubuntu 20.04 using mostly aptitude. But it's not quite working and I want to increase the log level to better understand the problem. I did see another post that suggested that I add to /etc/mailman3/mailman.cfg
[logging.template] level: debug
But that doesn't work for me. For example, after using that mailman conf doesn't list and debug values and as far as I can tell, the service, even after restarting, is not logging any more than it was. On the other hand, if I add
[logging.smtp] level: debug
Invoking mailman conf will reflect that new loglevel. This started me down the path of trying to figure out the configuration system of mailman in hope that that will save me time down the road. I have read
https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html but that doesn't seem to agree with what I'm seeing.
For an additional example, my mailman.cfg file has a "logging.debian" section, but I don't see that section listed in the mailman conf output. Why would that be?
I don't see in the documentation if mailman conf only sees values after the service is restarted. Nevertheless, restarting mailman hasn't helped.
What guidance can you give?
Context: mailman info produces:
GNU Mailman 3.2.2 (La Villa Strangiato) Python 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] config file: /etc/mailman3/mailman.cfg db url: sqlite:////var/lib/mailman3/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:KI5TuWE/v.....
On 6/30/20 11:29 AM, trewtus+200629maitr@gmail.com wrote:
Hey Team, I'm new to Mailman and after some failed attempts to install from git on CentOS8, I have just installed it on Ubuntu 20.04 using mostly aptitude. But it's not quite working and I want to increase the log level to better understand the problem. I did see another post that suggested that I add to /etc/mailman3/mailman.cfg
[logging.template] level: debug
But that doesn't work for me. For example, after using that
mailman confdoesn't list and debug values and as far as I can tell, the service, even after restarting, is not logging any more than it was. On the other hand, if I add[logging.smtp] level: debug
Invoking
mailman confwill reflect that new loglevel.
The settings in the logging.template section set defaults for the other
logging.* sections. In particular, the logging.debug section sets
level: info so setting
[logging.template] level: debug
will not affect the setting for logging.debug.
See mailman/config/schema.cfg which is augmented by mailman/config/mailman.cfg and by your own mailman.cfg.
This started me down the path of trying to figure out the configuration system of mailman in hope that that will save me time down the road. I have read https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html but that doesn't seem to agree with what I'm seeing.
For an additional example, my mailman.cfg file has a "logging.debian" section, but I don't see that section listed in the
mailman confoutput. Why would that be?
Because you have installed the Debian/Ubuntu package and that setting is
specific to that package and probably only defined in their local
mailman.cfg. The reason you don't see it in mailman conf, is it's
broken. Without a -s/--section argument, it only lists sections
defined in schema.cfg. See
<https://gitlab.com/mailman/mailman/-/issues/736>,
<https://gitlab.com/mailman/mailman/-/merge_requests/666> and
<https://pythonhosted.org/lazr.config/lazr/config/docs/usage.html>.
If you do mailman conf -s logging.debian you'll see it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
trewtus+200629maitr＠gmail.com