Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question
As an aside, for anyone else who is trying to do the same (and to give some background into my procedures so far), I have been following these references:
<https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-virtualenv>
My goal is to create the least change to file locations and configuration files as possible (I may move things into more "source-installed centric" locations once I have things working again), thus, many files are still in the original Debian package-allocated directories.
That said, I was forced to move mailman3web.db to /opt/mailman/web as sqlite (and, hence, mailman-web) simply could not open the database as user mailman from my virtual environment (even with mailman3web.db file permissions set to 777 and owner.group set to mailman.mailman).
So far I've gotten mailman running properly and handling the mailing lists, however, I have not gotten the web interface working again.
I have just migrated from a mailman 3.2.2 Debian package installation to a mailman 3.3.8 source install (in a Python virtual environment as mailman user) on an Ubuntu 20.04.6 LTS system.
I am not very familiar with the Python environment and this is my first experience administering mailman.
Something is broken in the Nginx/wsgi/Django path as I can't serve up any web pages. Depending on how I alter my .conf files I either get a "502 Bad Gateway" or "too many redirects". Thing were working before I did the migration.
There are several things that don't look right in my mailman-web.log file, as follows:
- !!! no internal routing support, rebuild with pcre support !!!
- failed to open python file wsgi.py
- unable to load app 0 (mountpoint='') (callable not found or import error)
- python3: can't open file 'manage.py': [Errno 2] No such file or directory
The last one looks the most concerning, and is looping.
Can anyone give me some guidance as to what I may have done wrong and which of these message are critical?
Here is my mailman-web.log:
*** Starting uWSGI 2.0.21 (64bit) on [Fri Jun 23 21:54:30 2023] *** compiled with version: 9.4.0 on 22 June 2023 20:37:17 os: Linux-5.4.0-152-generic #169-Ubuntu SMP Tue Jun 6 22:23:09 UTC 2023 nodename: speedy machine: x86_64 clock source: unix detected number of CPU cores: 8 current working directory: / detected binary path: /opt/mailman/venv/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! chdir() to /usr/share/mailman3-web your processes number limit is 257123 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to UNIX address /run/mailman3-web/uwsgi.sock fd 3 Python version: 3.8.10 (default, May 26 2023, 14:05:08) [GCC 9.4.0] Python main interpreter initialized at 0x560f27eb0bb0 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 166752 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** failed to open python file wsgi.py unable to load app 0 (mountpoint='') (callable not found or import error) *** no app loaded. going in full dynamic mode *** *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 161531) spawned uWSGI worker 1 (pid: 161536, cores: 2) [uwsgi-daemons] spawning "python3 manage.py qcluster" (uid: 2005 gid: 2005) python3: can't open file 'manage.py': [Errno 2] No such file or directory [uwsgi-daemons] throttling "python3 manage.py qcluster" for 1 seconds [uwsgi-daemons] respawning "python3 manage.py qcluster" (uid: 2005 gid: 2005) python3: can't open file 'manage.py': [Errno 2] No such file or directory
On 6/23/23 10:44 PM, Ken Alker wrote:
- python3: can't open file 'manage.py': [Errno 2] No such file or directory
The last one looks the most concerning, and is looping.
If you installed the mailman-web package from PyPI, the django admin command is bin/mailman-web in your venv, not manage.py.
On 6/24/23 8:25 AM, Ken Alker wrote:
That said, I was forced to move mailman3web.db to /opt/mailman/web as sqlite (and, hence, mailman-web) simply could not open the database as user mailman from my virtual environment (even with mailman3web.db file permissions set to 777 and owner.group set to mailman.mailman).
That's probably an aparmor issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
--On Saturday, June 24, 2023 2:09 PM -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 6/23/23 10:44 PM, Ken Alker wrote:
- python3: can't open file 'manage.py': [Errno 2] No such file or directory
The last one looks the most concerning, and is looping.
If you installed the mailman-web package from PyPI, the django admin command is bin/mailman-web in your venv, not manage.py.
I found that in /etc/mailman3/uwsgi.ini and changed it and it solved the problem. Thank you!
I sent a reply to my original email this morning but when I view it in the web archives, it see that it didn't get threaded with my original email. I hope this one does. I wonder why the original did not.
Ken
On 6/24/23 8:09 PM, Ken Alker wrote:
I sent a reply to my original email this morning but when I view it in the web archives, it see that it didn't get threaded with my original email. I hope this one does. I wonder why the original did not.
This one was properly threaded. I too noticed that the thread was split, but I didn't examine the headers of the reply as I received it, so I can't say why, but threading is done by In-Reply-To: headers. Possibly the header in the reply was missing or didn't reference the Message-ID: of the original.
All I can say is the database has an empty in_reply_to value for the message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
In any case I have joined the split thread.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
How did you join the split thread?
The order of the first two emails is flipped; the original email from 6/23 is showing after the second email on 6/24. Do you know how that happened? Do you have a way to fix that too?
This is a good learning experience for my new adminstering responsibilities.
On 6/24/23 9:44 PM, Ken Alker wrote:
How did you join the split thread?
using HyperKitty's "Reattach this thread".
The order of the first two emails is flipped; the original email from 6/23 is showing after the second email on 6/24. Do you know how that happened? Do you have a way to fix that too?
That was my mistake. There were two choices. I could open the reply thread containing only https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... and reattach it to the original message thread now containing several messages or vice versa. I did the latter, i.e. with the result you see with the reply out of sequence at the top. Had I done the former the reply would have been out of sequence at the bottom. This would have been better, but it's now too late to change it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Ken Alker -
Mark Sapiro