Django error - External IP
I am seeing this error frequently:
Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/list/jackrail@list.jackrail.org/message/new
Internal Server Error: /archives/list/jackrail@list.jackrail.org/message/new
Error at /archives/list/jackrail@list.jackrail.org/message/new error 14 from memcached_get(:2:User:11:subscriptions)
Request Method: GET Request URL: https://list.jackrail.org/archives/list/jackrail@list.jackrail.org/message/n...
... followed by many many pages of settings information, none of which is informative to me.
What does this signify? I am trying to bring my list to a go live state, but this does not bode well.
I can send the full diagnostic (long) if need be.
Andrew
OK. I deleted the hyperkitty archive and started again. Now what I see is this:
6:58:48 [Q] INFO Process-1:1 processing [rebuild_thread_cache_votes] 06:58:48 [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. : Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_q-1.0.1-py3.7.egg/django_q/cluster.py", line 377, in worker res = f(*task['args'], **task['kwargs']) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.2.3-py3.7.egg/hyperkitty/tasks.py", line 189, in _rebuild_thread_cache_votes thread = Thread.objects.get(id=thread_id) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-2.1.9-py3.7.egg/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-2.1.9-py3.7.egg/django/db/models/query.py", line 399, in get self.model._meta.object_name hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist.
Any ideas?
On Thu, Jun 20, 2019, at 12:01 AM, andrew.bernard@gmail.com wrote:
OK. I deleted the hyperkitty archive and started again. Now what I see is this:
6:58:48 [Q] INFO Process-1:1 processing [rebuild_thread_cache_votes] 06:58:48 [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. : Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_q-1.0.1-py3.7.egg/django_q/cluster.py", line 377, in worker res = f(*task['args'], **task['kwargs']) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.2.3-py3.7.egg/hyperkitty/tasks.py", line 189, in _rebuild_thread_cache_votes thread = Thread.objects.get(id=thread_id) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-2.1.9-py3.7.egg/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-2.1.9-py3.7.egg/django/db/models/query.py", line 399, in get self.model._meta.object_name hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist.
Any ideas?
These seem to be queued jobs which came up after you cleared and restarted your instance. Since the threads don't exist anymore those queued jobs would fail with this error.
I would say this would be a pretty harmless error. I would need to look more on how to clean up the queue when cleared the archives.
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)
participants (2)
-
Abhilash Raj -
andrew.bernard＠gmail.com