On 9/28/20 12:58 AM, r.woithe@callassoftware.com wrote:
Hello, i set the necessary config params like descriped at https://wiki.list.org/x/17892072 with timeout = 9000. But we still get the nigthly email.
If you are still using Mailman core 3.2.2, those settings have no effect because the REST server doesn't use gunicorn prior to 3.3.0.
See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
I guess the best way would to upgrade to mailman-core 3.3.3 to avoid this error. Unfortunatly i can not use the ubuntu package-manager... Or is there a second way to avoid this error?
I don't know if upgrading Mailman core would avoid the error or not. As I indicated, it's almost certainly not a REST timeout after all.
We need to understand what causes the error. As I've said, the sync_mailman goes through the message senders and tries to set the senders mailman_id.
If you apply the attached patch to hyperkitty/models/sender.py, it will log the error and ignore it. Then, we'll get a bit more info from the log message.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan