On 9/30/20 8:21 AM, gordon@dickens.com wrote:
The error has not re-occurred in the last 24 hours since I removed the lock file as Mark recommended. So, I am hopefull that the problem is solved.
As I suggested at
<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/7DD6MLQNRLNV7KWYDHVHY3WMODVPTULE/>,
I don't think the underlying issue was with the mailman digests --send
run by cron. I think any mailman command would have failed as long as
the dbcreate.db lock residue was in /var/lib/mailman3/locks/. The
question is what left that there in the first place. Did you manually
run any mailman commands that terminated abnormally or were killed in
the day before this started?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan