CRAIG WILSON:
> Hi,
> I have recently "yum upgrade" my Centos Linux 7 Server. I had a fully working
> Postfix 2.10 system prior to that.
> My Postfix service won't start. This is the error:
> Jan 01 20:36:02 pbx.myrevtel.com<http://pbx.myrevtel.com/>systemd[1]:
> Starting Postfix Mail Transport Agent...
> Jan 01 20:36:02 pbx.myrevtel.com<http://pbx.myrevtel.com/>aliasesdb[28441]:
> /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
> compatibility_level=2
> Jan 01 20:36:02 pbx.myrevtel.com<http://pbx.myrevtel.com/>aliasesdb[28441]:
> /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
> meta_directory=/etc/postfix
> Jan 01 20:36:02 pbx.myrevtel.com<http://pbx.myrevtel.com/>aliasesdb[28441]:
> /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
> shlib_directory=no
> Jan 01 20:36:02 pbx.myrevtel.com<http://pbx.myrevtel.com/>postfix[28445]:
> /usr/lib/postfix/postfix-script: line 74: cd: HOME not set
> It appears related to the shlib_directory within the above postfix-script
> file.
> However, apparently the shlib_directory variable is only available in version
> 3.0+
> Could anyone advise please.
Why did you "upgrade" from Postfix3 to Postfix2?
You are now running Postfix2 binaries (no suppport for shlib_directory
or meta_directory) with your Postfix3 configuration (that specifies
shlib_directory and shlib_directory).
> Just to add: If I execute postconf -d | grep shlib_directory - I
> get shlib_directory = no on the previous version.
That was a Postfix3 system, which supports shlib_directory and
meta_directory.
> However, on my upgraded version the shlib_directory = no is not
> returned from the postconf -d command.
Because that is Postfix2, which does not support shlib_directory
or meta_directory.
Wietse
