Control: tag -1 + confirmed upstream Control: found -1 3.9.1-6 Control: postfix startup does not catch $data_directory lock issue
On Thu, 14 Apr 2011 16:41:36 +0200 "Raoul Bhatia [IPAX]" <r.bha...@ipax.at> wrote:
Package: postfix Version: 2.7.1-1 Severity: normal postfix check does not catch a possible startup error regarding wrong queue_directory permissions: /data/mail/conf essentially is a copy of /etc/postfix using different directories for spool, etc. (postconf output is attached.) i check the config via the postfix binary: > root@m01 ~ # postfix -c /data/mail/conf/ check; echo $? > postfix/postfix-script: warning: not owned by postfix: /data/mail/data//. > 0 everything looks fine. now i start postfix: > root@m01 ~ # postfix -c /data/mail/conf/ start; echo $? > postfix/postfix-script: warning: not owned by postfix: /data/mail/data//. > postfix/postfix-script: starting the Postfix mail system > 0 postfix tells me that it is starting. rc=0 suggest success. but postfix is not running: > root@m01 ~ # postfix -c /data/mail/conf/ status > postfix/postfix-script: the Postfix mail system is not running /var/log/mail.err shows: > # Apr 14 16:32:57 m01 postfix/master[18928]: fatal: open lock file /data/mail/data//master.lock: cannot create file exclusively: Permission denied
So this is $data_directory lock, not $queue_directory - ie, secondary lock. And this is indeed the case now in 2024 and postfix 3.9.1 /mjt
