[migration] to a another server - one year database apparently lacks fields for newer mailman3/django suite
As suggested by @Mark last week, I exported my databases mailman3, mailman2web of what was mailman 3.3.0 (or so) and imported these on my new working system.
Apparently, a database migration step is needed to run the new mailman3 with some older databases: because when I want to login to view my mailing lists, I got "An error occurred while processing your request." in the web.
Log files and error mail messages say inter alia:
Internal Server Error: /accounts/login/ OperationalError at /accounts/login/ (1054, "Unknown column 'socialaccount_socialapp.provider_id' in 'field list'"
and
Internal Server Error: /archives/ OperationalError at /archives/ (1054, "Unknown column 'hyperkitty_mailinglist.archive_rendering_mode' in 'field list'")
Please can you assist: How can I add the missing tables, is there an update script (running "python migrate.py" was not fixing this).
I also solved this issue. How?
By adding columns to two tables in the database mailman3web:
alter table hyperkitty_mailinglist add column archive_rendering_mode varchar(255) default null;
alter table socialaccount_socialapp add column provider_id varchar(200) NOT NULL;
alter table socialaccount_socialapp add column settings longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL CHECK (json_valid(settings));
On 10/20/23 14:04, Wikinaut wrote:
I also solved this issue. How?
By adding columns to two tables in the database mailman3web:
alter table hyperkitty_mailinglist add column archive_rendering_mode varchar(255) default null; alter table socialaccount_socialapp add column
provider_idvarchar(200) NOT NULL; alter table socialaccount_socialapp add columnsettingslongtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL CHECK (json_valid(settings));
The proper fix is just to run mailman-web migrate. See
https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mig...
You should also run that and mailman-web collectstatic mailman-web compress and mailman-web compilemessages any time you do any kind of
update. See
https://docs.mailman3.org/en/latest/install/virtualenv.html#collect-static-f...
et. seq.
Running mailman-web migrate at this point may fail because of the
changes you made manually.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Wikinaut