On Mon, 31 Oct 2022 09:38:37 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 10/31/22 00:17, Onyeibo Oku wrote:
It is not finding the logger file. The other django project on this machine is running fine. I can confirm that the logger plugin is installed. I must be missing something.
If you are following https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configur... take note of
# Make sure that this directory is created or Django will fail on start. LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log'
` [Reviving this thread].
I abandoned the hyperkitty setup for a while and returned to it again today. I made progress. It turns out that I needed the uwsgi-logger-file rpm package and It wasn't installed with the uwsgi server. I adapted the settings also, since I was using Emperor mode (recall that there are other Django projects on the box). Currently, mailman, uwsgi and nginx are all running. They all seem to be happy until I assess the mailman-web home URL (e.g. http://my.server.com).
The outcome: "502 Bad Gateway"
Nothing shows in the logs except at /var/log/nginx/error.log:
2022/12/08 15:35:10 [error] 5879#5879: *7 upstream prematurely closed connection while reading response header from upstream, client: 105.113.33.89, server: my.server.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8000/favicon.ico", host: "my.server.com", referrer: "https://my.server.com/".
Something seems to be wrong between uwsgi and mailman, but I don't know where to look.
Regards Onyeibo