Importing config and archives only partially succeeded?
Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3. Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails. The imported members and other settings are correctly shown in the postorius page. Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails. Thanks in advance,Eric
On 12/12/20 2:33 PM, Eric Broens via Mailman-users wrote:
Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3. Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails. The imported members and other settings are correctly shown in the postorius page. Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails.
Did you specify --no-sync-mailman when you ran hyperkitty_import? If so did you run the django sync_mailman job when you finished importing?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks for your prompt reply.To import the config and archives I ran the commands as outlined in Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation :
mailman import21 foo-list@example.com /path/to/mailman2/foo-list/config.pck python manage.py hyperkitty_import -l foo-list@example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox After running these commands the archives became available for most of the mailinglists. I didn't run the Django admin command with arguments "update_index_one_list" to build the indices for each mailinglist seperately. After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. Best regards,Eric
On Sunday, December 13, 2020, 12:12:46 AM GMT+1, Mark Sapiro <mark@msapiro.net> wrote: On 12/12/20 2:33 PM, Eric Broens via Mailman-users wrote:
Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3. Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails. The imported members and other settings are correctly shown in the postorius page. Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails.
Did you specify --no-sync-mailman when you ran hyperkitty_import? If so did you run the django sync_mailman job when you finished importing?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/
On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote:
After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage.
I agree, that won't make the mails available on the webpage.
If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still.
What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro mark@msapiro.net wrote:
On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote:
After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage.
I agree, that won't make the mails available on the webpage.
If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still.
What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/
I just notice in the webserver logfile, the same request for the same mlist, msgid and key several times per second for about 3 hours now: "GET /archives/api/mailman/urls?mlist=....&msgid=...&key=... HTTP/1.1" 200 105 "-" "python-requests/2.25.0"
The request seems to originate from the server where the mailman suite is installed Best Regards,Eric On Sunday, December 13, 2020, 01:54:54 AM GMT+1, Eric Broens via Mailman-users mailman-users@mailman3.org wrote:
The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro mark@msapiro.net wrote:
On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote:
After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage.
I agree, that won't make the mails available on the webpage.
If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still.
What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/
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/
On 12/12/20 5:24 PM, Eric Broens via Mailman-users wrote:
I just notice in the webserver logfile, the same request for the same mlist, msgid and key several times per second for about 3 hours now: "GET /archives/api/mailman/urls?mlist=....&msgid=...&key=... HTTP/1.1" 200 105 "-" "python-requests/2.25.0"
Is there a message in Mailman's var/archives/hyperkitty/spool/ directory? If so, what's logged in mailman's mailman.log
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail. I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)." Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list. Also after clearing the browser cache, the above behavior is seen. Best Regards,Eric
On Sunday, December 13, 2020, 03:58:47 AM GMT+1, Mark Sapiro <mark@msapiro.net> wrote: On 12/12/20 5:24 PM, Eric Broens via Mailman-users wrote:
I just notice in the webserver logfile, the same request for the same mlist, msgid and key several times per second for about 3 hours now: "GET /archives/api/mailman/urls?mlist=....&msgid=...&key=... HTTP/1.1" 200 105 "-" "python-requests/2.25.0"
Is there a message in Mailman's var/archives/hyperkitty/spool/ directory? If so, what's logged in mailman's mailman.log
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/
On 12/12/20 7:40 PM, Eric Broens via Mailman-users wrote:
There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail.
I'm not sure what is causing the repeated access of /archives/api/mailman/urls... This call comes from Mailman core in order to request the URL at which a message will be archived. It is called from mailman/src/mailman/handlers/rfc_2369.py when adding the Archived-At: header and from mailman/src/mailman/handlers/decorate.py in order to get the hyperkitty_url replacement value.
I don't understand why it would be called repeatedly for the same message. Are there any clues in mailman.log.
I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)."
What if you look at "threads by month" and select the current month?
Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list.
I think the basic issue is when you see no messages, HyperKitty, for whatever reason thinks there are no current messages. I'm not sure, but if there are recent posts, are they all in threads started more than 30 days ago?
As far as all the participants/discussions counts being zero, I think one of the periodic jobs will fix that (possibly the daily recent_threads_cache job)
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark, 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. This is weird because other mails have been distributed. The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25
webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too).
2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there. 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings
Best Regards,Eric On Sunday, December 13, 2020, 06:29:19 AM GMT+1, Mark Sapiro mark@msapiro.net wrote:
On 12/12/20 7:40 PM, Eric Broens via Mailman-users wrote:
There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail.
I'm not sure what is causing the repeated access of /archives/api/mailman/urls... This call comes from Mailman core in order to request the URL at which a message will be archived. It is called from mailman/src/mailman/handlers/rfc_2369.py when adding the Archived-At: header and from mailman/src/mailman/handlers/decorate.py in order to get the hyperkitty_url replacement value.
I don't understand why it would be called repeatedly for the same message. Are there any clues in mailman.log.
I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)."
What if you look at "threads by month" and select the current month?
Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list.
I think the basic issue is when you see no messages, HyperKitty, for whatever reason thinks there are no current messages. I'm not sure, but if there are recent posts, are they all in threads started more than 30 days ago?
As far as all the participants/discussions counts being zero, I think one of the periodic jobs will fix that (possibly the daily recent_threads_cache job)
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/
On 12/13/20 7:11 AM, Eric Broens via Mailman-users wrote:
Hi Mark, 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. This is weird because other mails have been distributed. The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25
That message is in response to a socket.error exception in attempted delivery. It is logged only once until there is a successful delivery, but the message keeps being retried.
webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too).
Those GETs are part of normal message processing. As I said, they result from core handlers asking HyperKitty for the URL at which the message will be archived so they can add that URL to the Archived-At: header and maybe to a message header or footer.
Presumably the one that keeps repeating is the one message/message-id that is throwing the socket.error and being continuously retried.
I would stop Mailman and move that one .pck or .bak file out of
Mailman's var/queue/out/ directory and then start mailman. You can then
examine the queue entry with mailman qfile and maybe see what the
issue is.
2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there.
OK.
3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings
/opt/mailman/venv/bin/django-admin runjobs --list
will show you what the jobs are. The hourly jobs are new_lists_from_mailman, thread_starting_email and update_index. The one running long is almost certainly update_index. I would stop running the hourly jobs until you have successfully updated the search index for all lists.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
mailman qfile on the 5 pck files that were in the /out directory looked OK, although I am not sure if I should have looked at something specific.
The bak file disappeared as soon as I stopped mailman. When I started mailman again the name of the bak file had changed, and it changed every time I listed the directory.After stopping and starting mailman once more it didn't appear anymore. There are also 6 files in the shunt directory. I don't know what this directory is used for. For now I have disabled the hourly jobs.I will rebuild the search index for each mailinglist separately since the update_index was apparently killed before it finished. Best Regards,Eric On Sunday, December 13, 2020, 06:18:21 PM GMT+1, Mark Sapiro mark@msapiro.net wrote:
On 12/13/20 7:11 AM, Eric Broens via Mailman-users wrote:
Hi Mark, 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. This is weird because other mails have been distributed. The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25
That message is in response to a socket.error exception in attempted delivery. It is logged only once until there is a successful delivery, but the message keeps being retried.
webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too).
Those GETs are part of normal message processing. As I said, they result from core handlers asking HyperKitty for the URL at which the message will be archived so they can add that URL to the Archived-At: header and maybe to a message header or footer.
Presumably the one that keeps repeating is the one message/message-id that is throwing the socket.error and being continuously retried.
I would stop Mailman and move that one .pck or .bak file out of
Mailman's var/queue/out/ directory and then start mailman. You can then
examine the queue entry with mailman qfile and maybe see what the
issue is.
2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there.
OK.
3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings
/opt/mailman/venv/bin/django-admin runjobs --list
will show you what the jobs are. The hourly jobs are new_lists_from_mailman, thread_starting_email and update_index. The one running long is almost certainly update_index. I would stop running the hourly jobs until you have successfully updated the search index for all lists.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/
participants (2)
-
Eric Broens -
Mark Sapiro