On Wed, Jun 12, 2024 at 4:57 PM dgoldsmith--- via Mailman-users < mailman-users@mailman3.org> wrote:
We are running mailman 3.x in a venv setup using Postgresql. The mailman service hangs during startup and eventually fails with a timeout:
# systemctl status mailman3 × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) Active: failed (Result: timeout) since Wed 2024-06-12 13:35:23 UTC; 11s ago Process: 1205 ExecStart=/opt/mailman/venv/bin/mailman start (code=killed, signal=TERM) CPU: 1.019s
Jun 12 13:33:53 <hostname> systemd[1]: Starting GNU Mailing List Manager... Jun 12 13:35:23 <hostname>systemd[1]: mailman3.service: start operation timed out. Terminating. Jun 12 13:35:23 <hostname> systemd[1]: mailman3.service: Failed with result 'timeout'. Jun 12 13:35:23 <hostname> systemd[1]: Failed to start GNU Mailing List Manager. Jun 12 13:35:23 <hostname> systemd[1]: mailman3.service: Consumed 1.019s CPU time.
Searching I found some similar reports where it seemed to be an issue with a stale .lck lock file. But on our system:
You are talking of an OS update. My guess is that the OS update changed your Python version so what the virtualenv was using isn't there.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]