max.diener@hpi.de writes:
Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: for res in _socket.getaddrinfo(host, port, family, type, proto, flags): Aug 22 09:54:12 mailman3test mailman[55146]: socket.gaierror: [Errno -2] Name or service not known
This appears to be a DNS problem, probably for Mailman's host, since it occurs during startup.
The following three lines aren't relevant.
Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Aug 22 09:55:01 mailman3test CRON[55177]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session closed for user root
I'm not sure what timeout is referred to here.
Aug 22 09:55:34 mailman3test systemd[1]: mailman3.service: start operation timed out. Terminating. Aug 22 09:55:35 mailman3test systemd[1]: mailman3.service: Failed with result 'timeout'.
Anybody knows whats going on and what i am doing wrong?
Need more information about your configuration, but it sure looks like there's either a DNS problem or a problem binding to the LMTP port. Not sure what your Mailman is using but I think we normally use the submission port, 587, which is a port for restricted use. Perhaps there's a system security issue, eg, from SELinux. But I would check DNS twice first (unless you're definitely using enhanced security like SElinux).
Steve