Your message dated Mon, 18 Feb 2019 04:07:48 -0500
with message-id <6107112.cK4TRFRr2V@kitterma-e6430>
and subject line Re: Bug#815694: postfix init scripts think it started even
though it did not
has caused the Debian Bug report #815694,
regarding postfix init scripts think it started even though it did not
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.)
--
815694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 3.0.3-1
Severity: important
Hey.
Well there are already bugs open that postfix is broken since 3.0,...
But another thing that apparently doesn't work:
When doing something like
systemctl start postfix.service
systemctl status postfix.service
the init scripts from postfix obviously think everything would be fine,
even though the daemon failed to start.
Cheers,
Chris.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
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 libicu55 55.1-7
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 python3 3.5.1-1
Versions of packages postfix suggests:
ii bsd-mailx [mail-reader] 8.1.2-0.20160123cvs-2
pn dovecot-common <none>
ii evolution [mail-reader] 3.18.3-1
ii icedove [mail-reader] 38.6.0-1
ii libsasl2-modules 2.1.26.dfsg1-14+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>
pn procmail <none>
ii resolvconf 1.78
pn sasl2-bin <none>
pn ufw <none>
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Tue, 10 Oct 2017 12:26:35 +0200 Tobias Senger <tob...@t-senger.de> wrote:
> On Mon, 11 Apr 2016 08:09:14 -0600 LaMont Jones wrote: > On Sat, Feb 20,
> 2016 at 10:28:07PM +0100, Christoph Anton Mitterer wrote: > > Package:
> postfix > > Version: 3.0.3-1 > > Severity: important > > > > Hey. > >
> Well there are already bugs open that postfix is broken since 3.0,... >
> > But another thing that apparently doesn't work: > > When doing something
like > > systemctl start postfix.service > > systemctl status postfix.service
> > the init scripts from postfix obviously think everything would be fine, >
> even though the daemon failed to start. > > I cannot reproduce this (with
3.0.4-5)... Can you provide more details? > For starters, what does mail.log
have to say about the situation? > > lamont > >
>
> Seems to be the same problem as described here:
> https://serverfault.com/questions/877626/postfix-only-starts-after-systemctl-daemon-reload/877749
>
>
> mail.log says:
>
> Oct 10 10:32:55 mail postfix/postfix-script[20398]: starting the Postfix
> mail system
> Oct 10 10:32:55 mail postfix/master[20400]: daemon started -- version
> 3.1.6, configuration /etc/postfix
>
> but no process is started.
Assuming your assessment is correct. The issues in question have, I believe,
all been resolved. If someone still has this on current stable, testing, or
unstable, please reopen the bug.
Scott K
--- End Message ---
