On 2/17/22 10:49, Sandor Dibuz wrote:
Great! So valuable info. Thank you, Mark. "earlier that the oldest message" you sure mean earlier then the oldest of already archived. Or since= any date of the mbox messages to be imported. Will check the hyperkitty_import for since= option format.
That was a typo. I meant "earlier than". I tend to use since=1970-1-1.
It doesn't matter how early as long as it's earlier than the oldest
message to be imported.
Yet another question. Is it supposed to stop minutely/hourly/etc. mailman3-web cron jobs during import to avoid any collisions? Or even mailman3-web completely but probably it needs to be running. I only ask because my last import attempt on a test maillist failed with
[ERROR/MainProcess] Failed indexing 1 - 2 (retry 5/5): (1712, 'Index hyperkitty_attachment is corrupted') (pid 5841): (1712, 'Index hyperkitty_attachment is corrupted')
Optimizing cured the hyperkitty_attachment InnoDB index corruption problem but scared the sh.. out of me for a moment...
I don't know what may have caused the index corruption. I don't bother to stop any crons or services while hyperkitty_import is running and I've never had an issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan