On Sun, Dec 24, 2023 at 12:21 PM Wikinaut <mail@tgries.de> wrote:
I made for a repeated time (after system update and/or system reboot) the experience,that my mailman3 installation fails to start because of permission error to write the log file.
For some unknown reason, an empty file /var/og/mailman/mailman.log was apparently owned by list:list. I deleted that file and mailman3 core could now be started. The start problem i solved.
I asked myself and you, how can this happen for many times? Has anyone an idea what the reason could be?
It can only mean that there is a process, running as list:list that created the file.
There is still a user list from a previous mailman3 installation, where I assigned the (former user for mailman2), but I suppose the problem is a different problem than a simple user definition.
In a virtualenv type of installation, such an issue does not arise as everything in the virtualenv is owned by mailman:mailman. So maybe you can consider migrating to a virtualenv install?
Check if you have something withing logrorate config that creates the file.It's a guess.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]