On 12/10/21 3:45 PM, dancab@caltech.edu wrote:
Thanks Mark. We're using https:// for the URLs. Mailman 3.3.5 is what we're running.
(mailmanve) mailman@14ea21f6d4b1:/var/www/mailman-www$ mailman conf |grep tasks [mailman] run_tasks_every: 1h
We're using two containers behind a load balancer for Mailman so I suspect this is where the lost cache comes into play.
Yes. The cache entry is stored in the database which presumably is shared, but the actual cached data may only be stored in the file system of the server that cached it so the other server will think it's lost. Are you sharing Mailman's var/ directory between the two servers? I think you need to do that.
Would it be safe to increase the task frequency to every 15 minutes via the setting below?
run_tasks_every: 15m
I don't think that will do what you hope. It won't hurt, but the task runner only evicts expired entries, and they have a life set by cache_life in the [mailman] section of mailman.cfg (not to be confused with cache_lifetime set in the [dmarc] section) with a default of 7 days.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan