Summary: hyperkitty_import reports 'sqlite3.OperationalError: unable to open
database file' during attempt to migrate from Mailman 2 to Mailman 3.
I would be very pleased to receive suggestions on how to troubleshoot this
further.
Details:
Background: The first part of my migration plan on this Debian 11 system is:
1. Install mailman3
2. Create a test list under mailman3, make sure it works
3. Create a test list (tl2) under mailman2, make sure it works
4. Convert the mailman2 test list to mailman3.
re: 2. The mailman3 test list accepts messages and delivers them to all
members. The hyperkitty web interface displays messages and the archive can be
searched.
re: 3. The mailman2 test list (tl2) accepts messages and delivers them to all
members.
re: 4. mailman 'import21' appears to work:
$ mailman import21 t...@example.com /var/lib/mailman/lists/tl2/config.pck
r...@example.com is already imported with role MemberRole.owner
re: 4. 'hyperkitty_import' fails:
/usr/share/doc/python3-django-hyperkitty/examples$ python3 \
/usr/share/doc/python3-django-hyperkitty/examples/manage.py \
hyperkitty_import -l t...@example.com \
/var/lib/mailman/archives/private/tl2.mbox/tl2.mbox
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/django/db/backends/base/base.py", line
217, in ensure_connection
self.connect()
File "/usr/lib/python3/dist-packages/django/db/backends/base/base.py", line
195, in connect
self.connection = self.get_new_connection(conn_params)
File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py",
line 194, in get_new_connection
conn = Database.connect(**conn_params)
sqlite3.OperationalError: unable to open database file
I have looked for an sqlite3 file associated with the tl2 mailing list, but
have not found it.
cd /var
find . -name "*.db" -print
finds 52 files, but none appear in any way related to mailman.
Perhaps the hyperkitty_import process is looking for an sqlite3 database
associated with the mailman3 tl2 list. This would be unexpected, since the
[database] section in /etc/mailman3/mailman.cfg references postgres.
I would be pleased to receive suggestions on how to troubleshoot this further.
Thanks,
Ken
