tickets #95242
closed
- Category set to Mailing lists
- Private changed from Yes to No
It looks like the 'archive' runner crashed, I found this in the log:
Jul 05 00:11:33 2021 (9522) HyperKitty failure on http://localhost/archives/api/mailman/archive: <html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx/1.16.1</center>
</body>
</html>
(413)
Jul 05 00:11:33 2021 (9522) Exception in the HyperKitty archiver: <html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx/1.16.1</center>
</body>
</html>
Jul 05 00:11:33 2021 (9522) Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message
url = self._send_message(mlist, msg)
File "/usr/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message
raise ValueError(result.text)
ValueError: <html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx/1.16.1</center>
</body>
</html>
I restarted mailman - not sure if it has helped yet.
I restarted mailman - not sure if it has helped yet.
It looks like it is recovering, slowly.
- Status changed from New to Workable
- % Done changed from 0 to 50
Restarting mailman did get rid of the symptoms, but not the problem. The archive is working again, but why the 'archive' runner crashed and was not automatically restarted, who knows.
- Subject changed from mailing list web archives down to Mailman - the 'archive' runner crashed.
- % Done changed from 50 to 0
- Status changed from Workable to Resolved
- Assignee set to pjessen
- % Done changed from 0 to 100
Closing this one, nothing to do.
- Related to tickets #112928: mailman3 - when a runner dies, why isn't it just restarted? added
Also available in: Atom
PDF