Thanks Abhilash, I noticed that not only the "var" directory was created in the work directory but also the other directories.This even happened with a layout set in the config. Can a hotfix be expected for this bug, or will it take some time to get this fixed?This bug might cause problems when mailman needs to be restarted, or the server rebooted, I guess. At least I succeeded to get mailman 3 up and running on a Centos 8 VM, which was not easy, and intend to install it in the next few weeks on a production server in order to migrate the lists currently running with 2.1.x. https://docs.mailman3.org/en/latest/migration.html#id2 mentions that there is "a check_hk_import script in hyperkitty/contrib that can find and report messages" that can cause problems during import in hyperkitty. Is this still valid? I didn't find a check_hk_import script.
Best regards, Eric
On Wednesday, November 25, 2020, 04:15:11 AM GMT+1, Abhilash Raj <maxking@asynchronous.in> wrote: On Tue, Nov 24, 2020, at 7:26 AM, Eric Broens via Mailman-users wrote:
Hi, I am trying to install Mailman 3.3.2 in a python virtual environment, and don't understand why the following is happening.When executing "mailman info", it shows that "the config file is located in /etc/mailman3/mailman.cfg as is intended, hence "outside" the virtual environment. However, after having started mailman, and running "mailman info" again, the default (empty) config files seems to be created in the directory where mailman has been started:config file: /opt/mailman/mailman-suite/mailman-suite_project/var/etc/mailman.cfg This happens even when mailman is started with the option "-C /etc/mailman3/mailman.cfg".Does this mean that the config file needs to be located in a subdirectory of python's virtual environment?
It seems like a bug actually, I was able to reproduce this locally. I *think* we didn't notice it because we set a layout most of the times or simply rely on the default paths.here layout.
Although, it isn't related to inside or outside the virtualenv, it simply happens after two subsequent runs of mailman info commands with no changes between them. My guess is that first attempt create the var/ directory structure in the current working directory and in the next run, mailman creates the empty mailman.cfg inside that var/ directory instead of using the /etc/mailman3/mailman.cfg.
I've opened https://gitlab.com/mailman/mailman/-/issues/797 for this.
Abhilash
(venv) [root@test-vps mailman-suite_project]# mailman infoGNU Mailman 3.3.2 (Tom Sawyer)Python 3.6.8 (default, Apr 16 2020, 01:36:27)[GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]config file: /etc/mailman3/mailman.cfgdb url: mysql+pymysql://*****:*****@localhost/mailman?charset=utf8&use_unicode=1devmode: DISABLEDREST root url: http://localhost:8001/3.1/REST credentials: restadmin:restpass
(venv) [root@test-vps mailman-suite_project]# mailman startStarting Mailman's master runnerGenerating MTA alias maps
(venv) [root@test-vps mailman-suite_project]# mailman infoGNU Mailman 3.3.2 (Tom Sawyer)Python 3.6.8 (default, Apr 16 2020, 01:36:27)[GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]config file: /opt/mailman/mailman-suite/mailman-suite_project/var/etc/mailman.cfgdb url: sqlite:////opt/mailman/mailman-suite/mailman-suite_project/var/data/mailman.dbdevmode: DISABLEDREST root url: http://localhost:8001/3.1/REST credentials: restadmin:restpass Thanks,Eric
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/