troubleshooting hyperkitty
Working on a new installation -- lists seem to be working in terms of distributing postings.
But none of the postings are appearing in an archive yet.
I created a mailman-hyperkitty.cfg file in /opt/mailman/var/etc/.
It has a base_url for the "hyperkitty installation," and I'm not sure where that's supposed to be. The comment says "This address will be used by Mailman to forward incoming emails to Hyperkitty for archiving."
I set base_url to http://mailman.whiteoaks.com/hyperkitty (changing "localhost" from the example). It redirects to https:,
I set new secret keys here and in mailman.cfg.
No new posts appear, and nothing archive related shows up in mailman's log.
The mailman qcluster is running. The runner=archive job is running.
Can someone suggest a troubleshooting strategy?
Best regards, Mojo
Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>
Hi Morris, I struggled also with getting hyperkitty functioning. The url where mailman sends the REST requests to is <base_url>/hyperkitty, or whatever you defined in urls.py (url(r'^hyperkitty/', include('hyperkitty.urls'))).e.g. https://lists.example.com/hyperkitty You can get more logging if you add following section in mailman.cfg, at least if the archive REST requests are sent to the correct url.[logging.archiver]path: archiver.log Some error entries will appear in the log file if you access e.g. <base_url>/hyperkitty/api/mailman/urls from a browser, curl, wget, .... It is important to include add the hostname and/or ip addresses from where the requests are sent to the archiver into MAILMAN_ARCHIVER_FROMI had to add the public ip addresses of the server.If you have to make changes in settings.py or urls.py you will need to restart the webserver to in order to apply the changes. Best Regards,Eric
On Wednesday, December 9, 2020, 08:37:22 AM GMT+1, Morris Jones <mojo@whiteoaks.com> wrote: Working on a new installation -- lists seem to be working in terms of distributing postings.
But none of the postings are appearing in an archive yet.
I created a mailman-hyperkitty.cfg file in /opt/mailman/var/etc/.
It has a base_url for the "hyperkitty installation," and I'm not sure where that's supposed to be. The comment says "This address will be used by Mailman to forward incoming emails to Hyperkitty for archiving."
I set base_url to http://mailman.whiteoaks.com/hyperkitty (changing "localhost" from the example). It redirects to https:,
I set new secret keys here and in mailman.cfg.
No new posts appear, and nothing archive related shows up in mailman's log.
The mailman qcluster is running. The runner=archive job is running.
Can someone suggest a troubleshooting strategy?
Best regards, Mojo
Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>
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/8/20 11:37 PM, Morris Jones wrote:
I created a mailman-hyperkitty.cfg file in /opt/mailman/var/etc/.
You need to set
configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg
in the archiver.hyperkitty section of mailman.cfg.
It has a base_url for the "hyperkitty installation," and I'm not sure where that's supposed to be. The comment says "This address will be used by Mailman to forward incoming emails to Hyperkitty for archiving."
I set base_url to http://mailman.whiteoaks.com/hyperkitty (changing "localhost" from the example). It redirects to https:,
If it redirects to https, set it to https to avoid the redirect.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 12/9/2020 1:49 PM, Mark Sapiro wrote:
On 12/8/20 11:37 PM, Morris Jones wrote:
I created a mailman-hyperkitty.cfg file in /opt/mailman/var/etc/.
You need to set
configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg
did that ...
If it redirects to https, set it to https to avoid the redirect.
did that as well ...
base_url: https://mailman.whiteoaks.com/hyperkitty/
(Though the configuration comment on this suggests it should not be publicly accessible, I don't see any alternative endpoint that's private.)
I added both my public IP address and my domain name to MAILMAN_ARCHIVER_FROM.
So this part is all set, it would seem ...
[archive.hyperkitty]
class: mailman_hyperkitty.Archiver
enable: yes
configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg
[logging.archiver]
path: /opt/mailman/var/logs/archiver.log api_keyMy archiver log continues empty
The API keys match in settings_local.py MAILMAN_ARCHIVER_FROM and mailman-hyperkitty.cfg
Eric Broens suggested a curl to the endpoint to check for errors:
From that I get:
$ curl -i https://mailman.whiteoaks.com/hyperkitty/api/mailman/urls HTTP/1.1 401 Unauthorized Server: nginx Date: Thu, 10 Dec 2020 00:55:45 GMT Content-Type: text/html Content-Length: 226 Connection: keep-alive X-Content-Type-Options: nosniff X-Frame-Options: DENY Vary: Accept-Language, Cookie Content-Language: en
<html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html>
Presumably I didn't provide the key in the header.
archiver.log remains empty, and mailman.log has no references to the archiver.
The hyperkitty UI is presenting fine, but no messages are archived.
Best regards, Mojo
Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>
On 12/9/20 5:01 PM, Morris Jones wrote:
did that as well ...
base_url: https://mailman.whiteoaks.com/hyperkitty/
(Though the configuration comment on this suggests it should not be publicly accessible, I don't see any alternative endpoint that's private.)
The comments in mailman-hyperkitty/mailman-hyperkitty.cfg say in part
# ... It does not need to be publicly available, in fact it's # better if it is not.
but they add
# However, if your Mailman installation is accessed via HTTPS, the URL needs # to match your SSL certificate (e.g. https://lists.example.com/hyperkitty).
I added both my public IP address and my domain name to MAILMAN_ARCHIVER_FROM.
So this part is all set, it would seem ...
[archive.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg
[logging.archiver] path: /opt/mailman/var/logs/archiver.log api_key
What is api_key? Is your setting for api_key somehow garbled. Note it needs to be set in the general section of mailman-hyperkitty.cfg and not in mailman.cfg
My archiver log continues empty
The API keys match in settings_local.py MAILMAN_ARCHIVER_FROM and mailman-hyperkitty.cfg
The key in settings_local.py is MAILMAN_ARCHIVER_KEY, not MAILMAN_ARCHIVER_FROM, a typo in your mail or ??
Anyway, in settings_local.py the key is a python string and must be quoted, but the api_key setting in mailman-hyperkitty.cfg is not quoted.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 12/9/2020 9:11 PM, Mark Sapiro wrote:
path: /opt/mailman/var/logs/archiver.log api_key <--- ??
Ugh ... I must have garbled my email. The files look fine. I don't know where that stray "api_key" came from.
The key in settings_local.py is MAILMAN_ARCHIVER_KEY, not MAILMAN_ARCHIVER_FROM, a typo in your mail or ??
Yes, typo ... MAILMAN_ARCHIVER_KEY is 'properly_quoted' and unquoted in mailman-hyperkitty.cfg
I'm guessing the next thing I need to do is find a way to crank up the logging in mailman and look for occasions where it calls the hyperkitty endpoint and delivers the message.
I tried this but it may not be the right syntax:
[logging.archiver] level: debug path: /opt/mailman/var/logs/archiver.log
Mojo
Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>
On 12/9/20 9:39 PM, Morris Jones wrote:
I tried this but it may not be the right syntax:
[logging.archiver] level: debug path: /opt/mailman/var/logs/archiver.log
That is correct.
You should also be looking at mailman.log and your Django log (as configured in settings.py)
BTW, is archiving enabled for the list? See Postorius -> Settings -> Archiving.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 12/10/2020 8:21 AM, Mark Sapiro wrote:
BTW, is archiving enabled for the list? See Postorius -> Settings ->
Archiving.Good thought, it's set to "Public archives" But there's something ominous just below that setting, a headline that says "Active archivers" with no value beside it. Mojo
-- Morris Jones, Monrovia, CA [1]BridgeMojo [2]Old Town Sidewalk Astronomers [3]Mojo's Blog
References
On 12/10/20 8:49 AM, Morris Jones wrote:
But there's something ominous just below that setting, a headline that says "Active archivers" with no value beside it.
That's strange. It should be populated with things like
[] hyperkitty [] prototype
with a check box for each archiver for which enable is yes in the
corresponding archiver.xxx section in mailman.cfg.
What does bin/mailman conf -k enable show?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Morris Jones wrote:
So this part is all set, it would seem ... [archive.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg
That should be [archiver.hyperkitty], not [archive.hyperkitty]. Is that the issue or a typo in your email?
On 12/10/20 9:13 AM, Mark Sapiro wrote:
Morris Jones wrote:
So this part is all set, it would seem ... [archive.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg
That should be [archiver.hyperkitty], not [archive.hyperkitty]. Is that the issue or a typo in your email?
whew ... that was it.
After fixing the config typo, my first test message generated errors in archiver.log because I'd intentionally broken the key.
The second message worked, and the first one was delivered to the archive as well once the key was fixed.
So now I'll see if I can discover a way to make the setup less susceptible to that typo for those coming after me. I sure I probably induced the failure by typing the config instead of copying and pasting.
Thanks so much for the second pair of eyes.
Mojo
Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>
participants (3)
-
Eric Broens -
Mark Sapiro -
Morris Jones