
Hello,
since our last update from python 3.6 to python 3.9 our mailman server returns the following errors if we try to access the list via postorius.
[29/Oct/2022:13:25:25 +0200] "GET /3.1/lists/XXX.XXX.XX/archivers HTTP/1.1" 500 38 "-" "GNU Mailman REST client v3.3.4"
I tried to set the logging to a more verbose state but couldn't get a better message yet.
If somebody knows what went wrong, that would be great.
regards
Jacob

since our last update from python 3.6 to python 3.9 If somebody knows what went wrong, that would be great.
I don't know if it would have this symptom but between 3.7. and 3.8 Python moved the clock() function (IIRC) out of time, and recent Mailman now use time.time() in mailman/src/mailman/utilities/uid.py:TokenFactory._next_unpredictable_id instead of clock(). If your Mailman is old enough to expect time.clock() to exist, it's going to have problems.
I recommend upgrading Mailman, but if for some reason that's not realistic for you (or this turns out to be a false lead), maybe Mark or Abhilash have some ideas.
Steve

On 2022-10-29 13:49, Stephen J. Turnbull wrote:
since our last update from python 3.6 to python 3.9 If somebody knows what went wrong, that would be great.
I don't know if it would have this symptom but between 3.7. and 3.8 Python moved the clock() function (IIRC) out of time, and recent Mailman now use time.time() in mailman/src/mailman/utilities/uid.py:TokenFactory._next_unpredictable_id instead of clock(). If your Mailman is old enough to expect time.clock() to exist, it's going to have problems.
I recommend upgrading Mailman, but if for some reason that's not realistic for you (or this turns out to be a false lead), maybe Mark or Abhilash have some ideas. Hi Steve,
the error was really dumb on my side. I forgot to add in my ansible deployment command for the venv the package mailman-hyperkitty and because of that the commands where missing and it produced the error i described.
Today I read the documentation again and saw that i had missed that package somehow.
Thanks for your help and hard work on this project.
regards Jacob

Jacob Sievert via Mailman-users writes:
the error was really dumb on my side. I forgot to add in my ansible deployment command for the venv the package mailman-hyperkitty and because of that the commands where missing and it produced the error i described.
Thanks for the update. P.S. There are no dumb mistakes on this mailing list. Mistakes happen, but we just want to see them corrected. :-)
Steve
participants (2)
-
Jacob Sievert
-
Stephen J. Turnbull