paulrubin37@gmail.com writes:
I went the through the rest of the install got the login screen and after logging in I get this:
Forbidden (403) CSRF verification failed. Request aborted.
This is a webserver vulnerability mitigation, and I'm seeing the same HTTP statis on mailman3.org when I go to moderate these lists. I suspect a Django bug (or barely possible, change in Django's configuration that we need to update to). But I don't know for sure what's going on there. Pretty sure it's nothing you did wrong though.
Looking at the PostgreSQL db, the user table has certainly been emptied the only user is mailman.
Is that 'user' table in the 'mailman' database? Or is that Postgres's own user table? If the latter, mailman is probably the only user authenticated by Postgres (for other users including the 'postgres' database superuser, Postgres delegates to Unix login authentication).
Since you can't get to Django for the moment, if you activate the venv and type "mailman lists", do you see all your lists? If you then type "mailman members LIST" for some list, do you see all the members?
The UID, address and mailing list tables seem to contain many records. I am not sure how much to restore of the original DB? Short of doing a diff on two backup file do you have any insight?
Why do you think that your database has been corrupted? Does Postgres complain about inconsistencies? You would hope that you lost only transactions in progress at the time of the crash, and the database is internally consistent. If it has been corrupted, you probably should restore the whole thing from the backup, but that would lose any changes committed to the database between the backup and the crash.
If any of the mailman information commands above seem to give wrong information, or worse errors, then you probably need to restore the whole thing. But I suspect the database is intact.