On 12/26/25 08:02, dap1--- via Mailman-users wrote:
SELECT name FROM hyperkitty_mailinglist; +--------------------------+ | name | +--------------------------+ | lllllllll@ddddddddd.net | | lllllllll@gmail.com | +--------------------------+ 2 rows in set (0.00 sec)
It seems just deleting lllllllll@ddddddddd.net is non-trivial. Cannot delete or update a parent row: a foreign key constraint fails (
mailmanweb.hyperkitty_email, CONSTRAINThyperkitty_email_mailinglist_id_2c2b6f03_fk_hyperkittFOREIGN KEY (mailinglist_id) REFERENCEShyperki tty_mailinglist(id))
This is not a critical issue so you can just ignore it until you get the web UI working at which time a Django superuser or the list owner can delete the list in HyperKitty's web UI.
If you want to do it in the database, I think you can first do
DELETE FROM hyperkitty_attachment WHERE hyperkitty_attachment.email_id IN (SELECT id FROM hyperkitty_email WHERE hyperkitty_email.mailinglist_id IN (SELECT id FROM hyperkitty_mailinglist WHERE hyperkitty_mailinglist.name = 'lllllllll@ddddddddd.net'));
to delete attachments and then do
DELETE FROM hyperkitty_email WHERE hyperkitty_email.mailinglist_id IN (SELECT id FROM hyperkitty_mailinglist WHERE hyperkitty_mailinglist.name = 'lllllllll@ddddddddd.net');
to delete the emails and finally
DELETE FROM hyperkitty_mailinglist WHERE hyperkitty_mailinglist.name = 'lllllllll@ddddddddd.net';
But this may possibly run into other foreign key constraint issues. It's probably easier to get the web UI up and do it there.
netstat -lntp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 1103/systemd-resolv tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1407/mysqld tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1644/smbd tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1644/smbd tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 74794/python3 tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 74791/python3 tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 1103/systemd-resolv tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 74696/master tcp 0 0 0.0.0.0:26 0.0.0.0:* LISTEN 1/init tcp 0 0 127.0.0.1:33060 0.0.0.0:* LISTEN 1407/mysqld tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 160003/cupsd tcp6 0 0 :::443 :::* LISTEN 132763/apache2 tcp6 0 0 :::445 :::* LISTEN 1644/smbd tcp6 0 0 :::139 :::* LISTEN 1644/smbd tcp6 0 0 :::80 :::* LISTEN 132763/apache2 tcp6 0 0 :::25 :::* LISTEN 74696/master tcp6 0 0 :::26 :::* LISTEN 1/init tcp6 0 0 ::1:631 :::* LISTEN 160003/cupsd
I'm not using IPV6. Nothing is listening on 8000, just 8001 and 8024.
It appears that guicorn is not running if there is supposed to be a process by that name. There is also no such service.
See https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-st...
Particularly the part that says:
If using Gunicorn, the ExecStart line above becomes:
ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application
Do you have that and is the mailmanweb service running?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan