So I got a shiny new instance of Mailman3 installed (thanks Brian!).
I recreated my lists and I am now importing large historical list archives from an mbox file (24GB).
It takes a couple of hours to run this import, so I killed the import task after about 20 minutes so I could restart it in a screen session.
Now when I restart the import, it finishes almost immediately:
(venv) mailman@mail:/opt/mailman/mm$ /opt/mailman/mm/bin/django-admin hyperkitty_import -l trackjunkies@pdc-racing.net trackjunkies.mbox Importing from mbox file trackjunkies.mbox to trackjunkies@pdc-racing.net Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list trackjunkies@pdc-racing.net’. (venv) mailman@mail:/opt/mailman/mm$
Which is clearly not correct.
Anyone have an idea on how to restart this import?
THanks!
- Mark
mark@pdc-racing.net | 408-348-2878
On Tue, Jul 7, 2020, at 3:05 PM, Mark Dadgar wrote:
So I got a shiny new instance of Mailman3 installed (thanks Brian!).
I recreated my lists and I am now importing large historical list archives from an mbox file (24GB).
It takes a couple of hours to run this import, so I killed the import task after about 20 minutes so I could restart it in a screen session.
Now when I restart the import, it finishes almost immediately:
(venv) mailman@mail:/opt/mailman/mm$ /opt/mailman/mm/bin/django-admin hyperkitty_import -l trackjunkies@pdc-racing.net trackjunkies.mbox Importing from mbox file trackjunkies.mbox to trackjunkies@pdc-racing.net Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list trackjunkies@pdc-racing.net’. (venv) mailman@mail:/opt/mailman/mm$
Which is clearly not correct.
Anyone have an idea on how to restart this import?
Try running with “—since DATE” option with the date of the oldest message in the mbox, any random date before the oldest message should work too.
THanks!
- Mark
mark@pdc-racing.net | 408-348-2878
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
On Jul 7, 2020, at 3:18 PM, Abhilash Raj <maxking@asynchronous.in> wrote:
Anyone have an idea on how to restart this import?
Try running with “—since DATE” option with the date of the oldest message in the mbox, any random date before the oldest message should work too.
That seems to be working. Thank you.
- Mark
mark@pdc-racing.net | 408-348-2878
participants (2)
-
Abhilash Raj
-
Mark Dadgar