On Wed, Apr 17, 2019, at 8:18 AM, Mark Sapiro wrote:
On 4/17/19 8:10 AM, Abhilash Raj wrote:
On Wed, Apr 17, 2019, at 8:06 AM, Ben Harris wrote:
April 17, 2019 11:03 AM, "Abhilash Raj" firstname.lastname@example.org wrote: >
Which version of Hyperkitty are you using?
Did you upgrade the version of Hyperkitty when you migrated to the new host?
I'm using the mailman3-full package in ubuntu (i'm aware it's behind a couple releases), so it's hyperkitty 1.1.4.
I didn't upgrade anything with the move.
I am not sure where does Debian packaged version store it's fulltext index, but I am assuming the move somehow makes Hyperkitty not be able to read the index.
I think this is a known incompatibility between the Python 2.7 and Python 3 versions of Whoosh.
I think 1.1.x releases were based on Python 2.7, so that part looks right to me.
From the tracebacks, the current HyperKitty is running under Python 2.7. If the prior server was running HyperKitty with Python 3, that would explain this.
Given that 1.1.x supports only 2.7 and Ubuntu doesn't have 1.2 release, it is unlikely Python 3 was used.
Can you try
removing and re-building the entire index? I don't know again
the right command for Django there, but the hyperkitty command you want
to run is called
rebuild_index. For source package, something like:
$ python manage.py rebuild_index
Do note that this will take a lot of time if you have a big archive.
If this is the incompatibility, rebuilding the index will fix it.
-- Mark Sapiro email@example.com The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)