Hello! I just upgraded Debian 8 to Debian 9 with ISPConfig following this tutorial. All services are working after upgrade, except Postfix. It won't start because of its Backwards-Compatibility warnings. Found here a workaround/explanation of that. Running "postconf compatibility_level=2" and "postfix reload" turns off that backwards-compatibility. My question is: Is that safe to do on a production server ? Will that brake ISPConfig server ? Thanks
I do not know if it is safe to run with backwards compatibility turned on. I would only run that way until I figure out what changes to do to get Postfix to run without it. Perhaps compare Perfect Server guide for Stretch, and see what setting Postfix has there. I would say you have to go through that Guide anyway after the upgrade, so all setting for the installes softwares are made so they work on Stretch.
Well, I tested postfix for a couple of days on the upgraded server. The problem is that postfix si not starting after reboot and keeps stoping after a minute or so even when I start it manually with "systemctl start postfix", or "/etc/init.d./postfix start". I only can keep postfix up by starting it with "postfix start" . Any thoughts ? thanks
Hello! mail.log was clear except "postfix/master[14959]: terminating on signal 15" Postifx was receiving a sigterm 15. It was strange. Then I checked monit.log Code: [EEST Sep 20 09:37:53] error : 'master_bin' file doesn't exist [EEST Sep 20 09:37:53] info : 'master_bin' trying to restart [EEST Sep 20 09:37:53] info : 'postfix' stop: '/etc/init.d/postfix stop' [EEST Sep 20 09:38:23] error : 'postfix' failed to stop (exit status 0) -- '/etc/init.d/postfix stop': Stopping postfix (via systemctl): postfix.service. [EEST Sep 20 09:39:23] error : 'master_bin' file doesn't exist [EEST Sep 20 09:39:23] info : 'master_bin' trying to restart [EEST Sep 20 09:39:23] info : 'postfix' stop: '/etc/init.d/postfix stop' [EEST Sep 20 09:39:53] error : 'postfix' failed to stop (exit status 0) -- '/etc/init.d/postfix stop': Stopping postfix (via systemctl): postfix.service. [EEST Sep 20 09:40:53] error : 'master_bin' file doesn't exist [EEST Sep 20 09:40:53] info : 'master_bin' trying to restart [EEST Sep 20 09:40:53] info : 'postfix' stop: '/etc/init.d/postfix stop' [EEST Sep 20 09:41:23] error : 'postfix' failed to stop (exit status 0) -- '/etc/init.d/postfix stop': Stopping postfix (via systemctl): postfix.service. After the upgrade monit did not recognize the new binary of Postfix and tried to restart it. Thank you all for your help )
I'm seeing the same regular postfix-killing behaviour of "postfix/master[8604]: terminating on signal 15", and have also looked at the monit logs to find: [UTC Jul 8 16:26:19] error : 'master_bin' file doesn't exist [UTC Jul 8 16:26:19] info : 'master_bin' trying to restart [UTC Jul 8 16:26:19] error : 'master_bin' file doesn't exist [UTC Jul 8 16:26:19] error : 'postfix' failed to start -- could not start required services: 'master_bin'This seems to imply that monit is regularly killing postfix, because it can't find "master_bin", even though postfix is running. The current workaround is to stop monitoring postfix. I have postfix version 3.1.12 and monit version 5.20.0.
