hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header
I worke up to 959 such entries in my mailmanweb.log:
ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:49:57,784 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:05,746 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,022 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,183 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,273 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,353 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,435 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.
What might have been the cause of this?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
On 12/27/22 22:00, Odhiambo Washington wrote:
I worke up to 959 such entries in my mailmanweb.log:
ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ...
What might have been the cause of this?
Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= 1.3.5 requires mailman-hyperkitty>=1.2.0.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Dec 28, 2022 at 8:35 PM Mark Sapiro <mark@msapiro.net> wrote:
On 12/27/22 22:00, Odhiambo Washington wrote:
I worke up to 959 such entries in my mailmanweb.log:
ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ...
What might have been the cause of this?
Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= 1.3.5 requires mailman-hyperkitty>=1.2.0.
(venv) [mailman@gw ~/mm]$ pip list | grep itty HyperKitty 1.3.6 mailman-hyperkitty 1.2.0
Which I think is fine, no?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
On 12/28/22 12:22, Odhiambo Washington wrote:
On Wed, Dec 28, 2022 at 8:35 PM Mark Sapiro <mark@msapiro.net> wrote:
On 12/27/22 22:00, Odhiambo Washington wrote:
I worke up to 959 such entries in my mailmanweb.log:
ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ...
What might have been the cause of this?
Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= 1.3.5 requires mailman-hyperkitty>=1.2.0.
Actually, HyperKitty>=1.3.5 with mailman-hyperkitty<1.2.0 produces a different message so that isn't it.
There is an issue with Apache. If you search the archives of this list for the log message you'd find it, but see the last two posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/W...
But why these messages all of a sudden? Did you just change something?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Thu, Dec 29, 2022 at 2:54 AM Mark Sapiro <mark@msapiro.net> wrote:
On 12/28/22 12:22, Odhiambo Washington wrote:
On Wed, Dec 28, 2022 at 8:35 PM Mark Sapiro <mark@msapiro.net> wrote:
On 12/27/22 22:00, Odhiambo Washington wrote:
I worke up to 959 such entries in my mailmanweb.log:
ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ...
What might have been the cause of this?
Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= 1.3.5 requires mailman-hyperkitty>=1.2.0.
Actually, HyperKitty>=1.3.5 with mailman-hyperkitty<1.2.0 produces a different message so that isn't it.
There is an issue with Apache. If you search the archives of this list for the log message you'd find it, but see the last two posts in the thread at
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/W...
But why these messages all of a sudden? Did you just change something?
I found a mismatch!
MAILMAN_ARCHIVER_KEY != api_key A single quote character had sneaked in while copying the key over to the next file.
I will watch what happens when the archiver is run next and whether I really need the ' WSGIPassAuthorization On'.
Thank you very much as always.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
participants (2)
-
Mark Sapiro -
Odhiambo Washington