This bug was initially created as a copy of Bug #2028015 I am copying this bug because: Description of problem: If postfix is started from the command line rather than at boot, then when postfix is stopped (whether by postfix stop or by shutdown) the master.pid file doesn't get deleted, so then at next boot postfix doesn't start (but does delete the master.pid file). Version-Release number of selected component (if applicable): postfix 2:3.5.8-1.el8 How reproducible: Always Steps to Reproduce (as root): 1. If postfix is already running, execute postfix stop. 2. If the just-stopped postfix had been started at boot time, then there should be and is no /var/spool/postfix/pid/master.pid file existing. (If it had been started by postfix start from the command line, this file still exists even though the pid in it has stopped.) 3. Execute postfix start. 4. Note that /var/spool/postfix/pid/master.pid now contains the pid of the running postfix/master process. 5. Execute postfix stop. 6. Note that /var/spool/postfix/pid/master.pid still exists, even though the master process has been stopped. (Don't delete it yet though.) 7. Reboot the machine. 8. Note that postfix fails to start, leaving the message postfix/postfix-script[1959]: fatal: the Postfix mail system is already running in /var/log/maillog . 9. Note, however, that /var/spool/postfix/pid/master.pid has now been deleted. 10. Reboot the machine again - this time postfix starts normally. Actual results: As noted in point 6 above. Expected results: Whenever postfix is stopped, no matter how it has been started, the master.pid file should be deleted. Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (new packages: postfix), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:2598