Your message dated Tue, 23 Feb 2016 13:59:40 -0700
with message-id <20160223205940.ga32...@mix.mmjgroup.com>
and subject line Re: Bug#815047: postfix: Postfix fails to start after upgrade
has caused the Debian Bug report #815047,
regarding postfix: Does not start after upgrading to 3.0.3-1 - instance
conflicts
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
815047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 3.0.3-1
Severity: important
After upgrading to 3.0.3 postfix fails to start with the following
error:
Starting Postfix Mail Transport Agent: postfixpostmulti: fatal: instance
/etc/postfix, shlib_directory=/usr/lib/postfix conflicts with instance
/etc/postfix, daemon_directory=/usr/lib/postfix
Downgrading to 2.11.3-1+b1 fixes this issue (and the reportbug tool
generated its information from that version; I've manually corrected
the above Version: header).
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (990, 'unstable'), (200, 'testing')
Architecture: i386 (i686)
Kernel: Linux 4.4.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages postfix depends on:
ii adduser 3.113+nmu3
ii cpio 2.11+dfsg-5
ii debconf [debconf-2.0] 1.5.58
ii dpkg 1.18.4
ii libc6 2.21-9
ii libdb5.3 5.3.28-11
ii libsasl2-2 2.1.26.dfsg1-14+b1
ii libsqlite3-0 3.11.0-1
ii libssl1.0.2 1.0.2f-2
ii lsb-base 9.20160110
ii netbase 5.3
ii ssl-cert 1.0.37
Versions of packages postfix recommends:
ii python 2.7.11-1
Versions of packages postfix suggests:
ii bsd-mailx [mail-reader] 8.1.2-0.20160123cvs-2
pn dovecot-common <none>
ii icedove [mail-reader] 38.6.0-1
ii libsasl2-modules 2.1.26.dfsg1-14+b1
ii mailutils [mail-reader] 1:2.99.99-1
ii mutt [mail-reader] 1.5.24-1+b1
pn postfix-cdb <none>
ii postfix-doc 3.0.3-1
pn postfix-ldap <none>
pn postfix-mysql <none>
pn postfix-pcre <none>
pn postfix-pgsql <none>
ii procmail 3.22-25
ii resolvconf 1.78
ii s-nail [mail-reader] 14.8.6-1
pn sasl2-bin <none>
pn ufw <none>
-- debconf information:
[ Note: I've manually stripped some information in the following
lines, even though I'm pretty sure this does not hide anything]
postfix/rfc1035_violation: false
* postfix/sqlite_warning: true
* postfix/procmail: true
postfix/master_upgrade_warning:
* postfix/protocols: ipv4
postfix/transport_map_warning:
postfix/bad_recipient_delimiter:
* postfix/chattr: true
* postfix/mynetworks: 127.0.0.0/8, 192.[stripped]
postfix/nqmgr_upgrade_warning:
* postfix/mailbox_limit: 0
* postfix/root_address: robert
postfix/not_configured:
* postfix/mydomain_warning: true
* postfix/retry_upgrade_warning: true
postfix/tlsmgr_upgrade_warning:
postfix/dynamicmaps_upgrade_warning:
* postfix/destinations: vox.[stripped], localhost.[stripped], localhost, vox
* postfix/recipient_delim: +
postfix/relay_restrictions_warning:
* postfix/mailname: vox.[stripped]
postfix/db_upgrade_warning: true
postfix/kernel_version_warning:
* postfix/relayhost:
* postfix/main_mailer_type: Internet with smarthost
--- End Message ---
--- Begin Message ---
On Thu, Feb 18, 2016 at 07:56:02AM +0000, Russel Winder wrote:
> After this morning's upgrade of Postfix from 2.11.3-1+b1 to 3.0.3-1, postfix
> refuses to start saying:
>
> fatal: instance /etc/postfix, shlib_directory=/usr/lib/postfix conflicts with
> instance /etc/postfix, daemon_directory=/usr/lib/postfix
>
> It seems from email threads on the archives that haveing shlib_directory and
> daemon_directory refer to the
> same directory is now considered unacceptable. I have not set these variables
> explicitly in /etc/postfix/main.cf or/etc/postfix/
> master.cf.
Fixed in 3.0.4-1.
lamont
--- End Message ---
