On 2023-10-11 04:38, Mark Sapiro wrote:
Steve has addressed your issues with multiple Django admin commands, some of which apparently don't reference the correct settings.
The format of my final line is different to yours ...
It is not a clue as to the problem. The format of that
representationchanged in HyperKitty 1.3.5. What is your version?
HyperKitty version 1.3.4
What happens if you do, with the appropriate Django admin and list name,
python3 manage.py update_index_one_list thepost@example.com
Thank you Mark and Steve,
That worked a treat!
python3 manage.py update_index_one_list thepost@example.com
Running that command returned the message "Indexing 12 emails", then returned to the shell prompt when done. It successfully indexed the messages in the archive, and I could then do a search on the existing messages.
On 2023-10-11 00:54, Stephen J. Turnbull wrote:
The process of search index construction is both CPU and wall-clock time intensive. For this reason, the cron jobs that do regular index updating (I think once an hour?) are separate from the utility that constructs the index in the first place when you have existing archives (either migrated from another MLM such as Mailman 2, or if you're upgrading to better archive software).
The messages in the archive came directly from the list (ie. they weren't imported). It looks as though running that command flushed out a cobweb, as the hourly indexing is now happening.
Some time after I had run that indexing command, a new message was posted to the list, and appeared in the archive. I searched (a)immediately, (b) 15 mins after, and (c)an hour and a bit after.
As Steve said, the newer messages are automatically indexed hourly. So it wasn't until after that hourly index that the search terms in the newer messages were showing up in the search results.
I can't say I understand the inner workings of the process yet, but we have a working archive search and I'm very happy about that.
Thank you again, Mark