On Sat, Jan 27, 2024 at 8:17 AM Mark <imark@posteo.net> wrote:
"/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/connection.py",
line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR 2024-01-24 05:41:46,333 51799 django.request Internal Server Error: /postorius/lists/testing.example.com/
Try running all the system initializations with "mailman info" and "mailman conf". This often will elicit errors if the system is messed up. More likely to get this error would be "mailman withlist $LIST" (maybe you need an '-l' option to specify the list, I forget). If that doesn't elicit the error, then check that Mailman's runners are running with ps. Since it's Debian, I guess they should be running as the 'list' user. Are Mailman's files and directories owned by 'list' or sometimes 'www-data' for log files?
Debian yes, but venv/pip installation so running as "mailman".
The log is saying that when Postorius tried to look up that list, it tried to call out to Mailman core via HTTP to the API to get the information and that access failed with HTTP status 500. I think the actual error is likely to be reported in mailman.log (or it might be in error.log, "grep '05:41:46' *.log" in Mailman's log directory will probably find it). I'm pretty sure there will be relevant log entries, probably a matching traceback.
Hi,
Thank you Steve, Mark, Odhiambo for your responses.
After working my way through your suggestions with no joy I discovered to my embarrassment that I hadn't created the "mailman-hyperkitty.cfg" file. Once created all was well.
This was of course after I had begun the installation process again from scratch. My apologies for the waste of bandwidth and your time.
Regarding my installation, (following the docs at https://docs.mailman3.org/en/latest/install/virtualenv.html) I found a couple of issues that others might also stumble over:
- Installing Xapian needed clang. It didn't like gcc
- Being a fresh Debian 12 OS, I needed to also install make, build-essential
- For the user "mailman" to access the databases I needed to change the owner to mailman (even though all privileges has been granted) ...
postgres=# create database mailman;
CREATE DATABASE postgres=# create database mailmanweb; CREATE DATABASE postgres=# create user mailman with encrypted password '<PASSWORD>'; CREATE ROLE postgres=# grant all privileges on database mailman to mailman; GRANT postgres=# grant all privileges on database mailmanweb to mailman; GRANT
psql -d mailman -U mailman -W $ psql -d mailman -U mailman -W Password:
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: Peer authentication failed for user "mailman"
sudo -u postgres psql ALTER DATABASE mailman OWNER TO mailman; \q
$ psql -h localhost -d mailman -U mailman -W Password:
psql (15.5 (Debian 15.5-0+deb12u1)) SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off) Type "help" for help.
... and same for mailmanweb
So far, so good.
Thanks and apologies once again, Mark
The issue you're dealing with in that case is this change in PostgreSQL-15 discussed in this blog: https://www.cybertec-postgresql.com/en/error-permission-denied-schema-public...
I have never needed to do psql -d mailman -U mailman -W.
I used the steps documented above to enable mailman user to write to the
database.
postgres=# \c mailmanweb postgres You are now connected to database "mailmanweb" as user "postgres". mailmanweb=# GRANT ALL ON SCHEMA public TO mailman; GRANT mailmanweb=# \c mailman postgres You are now connected to database "mailman" as user "postgres". mailmanweb=# GRANT ALL ON SCHEMA public TO mailman; GRANT
TBH, I am not sure which method is the best although I think this option is :)
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]