On Tue, 25 Oct 2022 20:56:31 +0100 Onyeibo Oku <onyeibo@schemefusion.com> wrote:
On Tue, 25 Oct 2022 15:56:08 +0900 "Stephen J. Turnbull" <stephenjturnbull@gmail.com> wrote:
Onyeibo Oku writes:
This is tiring. At this moment I am left with the possibility that SELinux may be in the way. I cannot think of a way to prove this hypothesis.
How about the obvious, disable SELinux temporarily? To dynamically disable it before the reboot, run the following command: # setenforce 0
Thank you.
Sure enough Systemd succeeded when SELinux was in permissive mode (ignoring series of AVCs, of course). With SELinux in Enforcing mode, we are back to our previous mileage.
Conclusion: SELinux is in the way!
I am happy to inform you that Systemd now starts and stops Mailman without interruptions. After series of SELinux file context labeling, setting the nis boolean, and a few custom policies, it resolved. Thank you for the responses (and your patience).
Now at https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-wsg...
I have questions. I have a running instance of uwsgi serving a Django website on the target machine.
Will there be a conflict of resource (ports, threads, etc) running another instance?
Can one have multiple instances of uwsgi service? In whichcase, it doesn't hurt to follow the doc to its logical conclusion?
Regards Onyeibo