On Mon, Jun 26, 2023 at 9:29 AM Stephen J. Turnbull < turnbull.stephen.fw@u.tsukuba.ac.jp> wrote:
Ken Alker writes:
I see the below in my mailman.log, yet I installed uwsgi and NOT gunicorn. My mainmanweb.service file includes "ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" and not the gunicorn equivalent. Does this log entry make sense in my case?
[2023-06-22 12:44:36 -0700] [411132] [INFO] Starting gunicorn 20.1.0
Yes, it makes sense. Mailman 3 core is basically an application which manages a webserver that provides the REST API, a database of domains, users, and lists, an LMTP server for incoming posts and an SMTP client for outgoing distribution. Mailman uses gunicorn to provide the webserver.
Installation of gunicorn is handled as a package dependency, so you probably wouldn't notice unless you were watching the installation process very carefully.
It doesn't make sense, IMHO, because as the OP says,
his ExecStart is: ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" *and not* ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application.
He has not knowingly created any gunicorn.conf
Why would Gunicorn be Exec-ing itself? :-)
This being a virtualenv install, I find it very weird.
-- 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]