HyperKitty: discussions not updating, misreporting stats
These are a couple of HyperKitty issues that I have talked about in August 1. I’ve been doing a bit more experimentation in the last few days and am reporting my findings.
The two issues are:
— Missing messages: HyperKitty doesn’t show all of the messages in a discussion
- Misreporting of discussion statistics: HyperKitty doesn’t update the number of participants and comments in a discussionI’m using the latest Docker setup.
Neither of these issues are solved by updating or rebuilding indexes:
sudo docker exec mailman-web ./manage.py update_index
sudo docker exec mailman-web ./manage.py rebuild_indexHowever, if I stop and then restart the containers (sudo docker-compose down; sudo docker-compose up -d), the discussion statistics are updated and properly display the number of participants and comments in all discussions. This does not, however, solve the problem of missing messages.
I have discovered two methods of displaying the missing discussion messages:
add a new message to the thread in HyperKitty; I’m not convinced that this works *every* time, but it at least works *most* times
run the yearly cron job; this seems to work *every* time:
sudo docker exec mailman-web ./manage.py runjobs yearly https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/Z6FYFVDSMMA5DP34LDQJKXRQ4S7BWRGR/Cameron Smith
On Sun, Nov 12, 2017, at 04:24 PM, Cameron Smith wrote:
These are a couple of HyperKitty issues that I have talked about in August 1. I’ve been doing a bit more experimentation in the last few days and am reporting my findings.
The two issues are:
— Missing messages: HyperKitty doesn’t show all of the messages in a discussion
- Misreporting of discussion statistics: HyperKitty doesn’t update the number of participants and comments in a discussion
I’m using the latest Docker setup.
Neither of these issues are solved by updating or rebuilding indexes:
sudo docker exec mailman-web ./manage.py update_index sudo docker exec mailman-web ./manage.py rebuild_index
However, if I stop and then restart the containers (sudo docker-compose down; sudo docker-compose up -d), the discussion statistics are updated and properly display the number of participants and comments in all discussions. This does not, however, solve the problem of missing messages.
This sounds like there is something wrong with how django_q tasks are run inside container images. Either sum bug in uwsgi, or some configuration error.
I do remember Mark having an issue on lists.mailman3.org with django_q tasks not running properly, I wonder if it is the same issue here?
I have created an issue1 to track.
I have discovered two methods of displaying the missing discussion messages:
add a new message to the thread in HyperKitty; I’m not convinced that this works *every* time, but it at least works *most* times
run the yearly cron job; this seems to work *every* time:
sudo docker exec mailman-web ./manage.py runjobs yearly
I am not sure I have seen this before, but it is possible other MM3 admins might have.
Hyperkitty itself doesn't have any yearly jobs though, maybe some dependency does.
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/Z6FYFVDSMMA5DP34LDQJKXRQ4S7BWRGR/Cameron Smith
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Abhilash Raj maxking@asynchronous.in
participants (2)
-
Abhilash Raj -
Cameron Smith