Archiving has stopped working. No changes were made to the server. How can I diagnose and troubleshoot this please?
Are there instructions for how to update mailman3 somewhere? Is there a listing of bug fixes also?
Thank you!
On 2/18/21 1:00 PM, Christian Stalberg via Mailman-users wrote:
Archiving has stopped working. No changes were made to the server. How can I diagnose and troubleshoot this please?
Are there instructions for how to update mailman3 somewhere? Is there a listing of bug fixes also?
Thank you!
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/
If this is in regards to the server I install Mailman on, then here are the update instructions to use:
# cd /opt/mailman/mm # su mailman # source /opt/mailman/mm/venv/bin/activate # pip install --upgrade mailman hyperkitty postorius # pip install --upgrade django-mailman3 mailmanclient mailman-hyperkitty
You may need to update flufl.lock as well:
# pip install --upgrade flufl.lock # bin/mailman-post-update # deactivate # exit (this should take you back to root user) # systemctl restart mailman # systemctl restart qcluster # systemct restart gunicorn
-- Brian Carpenter Harmonylists.com Emwd.com
On 2/18/21 10:00 AM, Christian Stalberg via Mailman-users wrote:
Archiving has stopped working. No changes were made to the server. How can I diagnose and troubleshoot this please?
Start by looking at Mailman's logs and also see if there are messages to be archived in Mailman's var/archives/hyperkitty/spool/ directory.
Are there instructions for how to update mailman3 somewhere? Is there a listing of bug fixes also?
There are some instructions at <https://docs.mailman3.org/en/latest/upgrade-3.2.html>. Bug fixes are listed in each project's 'news', e.g., <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.h...> for Mailman core and <https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html> for HyperKitty.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I see two messages waiting to be archived. Below is excerpt from the logfile:
Feb 10 13:40:49 2021 (974) held message approved, message-id: <CAGrL7FsaX8EG9pMUZreJrQt1xkEyR3ySuw2-xn3m443O0N3j1A@mail.gmail.com> [10/Feb/2021:13:40:49 +0000] "POST /3.1/lists/ncpoa@lists.ccalternatives.org/held/5 HTTP/1.1" 204 0 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:49 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/held?count=0&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:49 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/held?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:50 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:50 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" Feb 10 13:40:55 2021 (846) HyperKitty failure on https://lists.ccalternatives.org/archives/api/mailman/archive: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M (413) Feb 10 13:40:55 2021 (846) Exception in the HyperKitty archiver: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M Feb 10 13:40:55 2021 (846) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M
Feb 10 13:40:56 2021 (846) HyperKitty failure on https://lists.ccalternatives.org/archives/api/mailman/archive: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M (413) Feb 10 13:40:56 2021 (846) Exception in the HyperKitty archiver: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M Feb 10 13:40:56 2021 (846) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M
[10/Feb/2021:13:41:38 +0000] "GET /3.1/domains HTTP/1.1" 200 321 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:38 +0000] "GET /3.1/domains/lists.ccalternatives.org HTTP/1.1" 200 216 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:38 +0000] "POST /3.1/lists/find HTTP/1.1" 200 1013 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/owner HTTP/1.1" 200 668 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/config HTTP/1.1" 200 3173 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/archivers HTTP/1.1" 200 100 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/archivers HTTP/1.1" 200 100 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:54 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/member/christian%40safecomputing.o rg HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:54 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:54 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:42:19 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:42:19 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/owner HTTP/1.1" 200 668 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:42:19 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1"
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Thursday, February 18, 2021 10:33 AM To: mailman-users@mailman3.org Subject: [MM3-users] Re: archiving problem & updates
On 2/18/21 10:00 AM, Christian Stalberg via Mailman-users wrote:
Archiving has stopped working. No changes were made to the server. How can I diagnose and troubleshoot this please?
Start by looking at Mailman's logs and also see if there are messages to be archived in Mailman's var/archives/hyperkitty/spool/ directory.
Are there instructions for how to update mailman3 somewhere? Is there a listing of bug fixes also?
There are some instructions at <https://docs.mailman3.org/en/latest/upgrade-3.2.html>. Bug fixes are listed in each project's 'news', e.g., <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS. html> for Mailman core and <https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html> for HyperKitty.
-- 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 2/19/21 7:19 AM, Christian Stalberg via Mailman-users wrote:
I see two messages waiting to be archived. Below is excerpt from the logfile:
Feb 10 13:40:49 2021 (974) held message approved, message-id: <CAGrL7FsaX8EG9pMUZreJrQt1xkEyR3ySuw2-xn3m443O0N3j1A@mail.gmail.com> [10/Feb/2021:13:40:49 +0000] "POST /3.1/lists/ncpoa@lists.ccalternatives.org/held/5 HTTP/1.1" 204 0 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:49 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/held?count=0&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:49 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/held?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:50 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:50 +0000] "GET /3.1/lists/ncpoa@lists.ccalternatives.org/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" Feb 10 13:40:55 2021 (846) HyperKitty failure on https://lists.ccalternatives.org/archives/api/mailman/archive: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M (413) Feb 10 13:40:55 2021 (846) Exception in the HyperKitty archiver: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M Feb 10 13:40:55 2021 (846) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M
The issue is that one of the messages in var/archives/hyperkitty/spool/ is throwing this exception and that effectively stops archiving of new messages.
I'm not sure what causes Request Entity Too Large, but I suspect it is a
very large message body. You can examine the messages in
var/archives/hyperkitty/spool/ with Mailman's bin/mailman qfile
command, but I suspect the problem is caused by the largest of the
files. You can just move it aside, and that should allow archiving to
resume.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2/19/21 1:13 PM, Mark Sapiro wrote:
I'm not sure what causes Request Entity Too Large, but I suspect it is a very large message body. You can examine the messages in var/archives/hyperkitty/spool/ with Mailman's
bin/mailman qfilecommand, but I suspect the problem is caused by the largest of the files. You can just move it aside, and that should allow archiving to resume.
I believe that is a NGINX error message. The following link has more information:
https://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-la...
-- Brian Carpenter Harmonylists.com Emwd.com
participants (3)
-
Brian Carpenter -
Christian Stalberg -
Mark Sapiro