Your message dated Wed, 15 May 2019 08:10:11 +0000
with message-id <20190515081011.ga13...@sarek.noreply.org>
and subject line Re: Bug#880047: postgrey doesn't start because it can't write
its pid
has caused the Debian Bug report #880047,
regarding postgrey doesn't start because it can't write its pid
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.)
--
880047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgrey
Version: 1.36-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The default init script that comes with Postgrey on Debian 9 fails to start
after a reboot. The installer creates /var/run/postgrey and writes its pid
there but /var/run is a tmpfs file system and so on a reboot /var/run/postgrey
ceases to exist. The init script for Postgrey does not attempt to create
/var/run/postgrey and just fails to start when it can't write to
/var/run/postgrey. When postgrey fails to start then Postfix starts complaining
that it is misconfigured and begins bouncing emails. I was able to fix this by
adding these lines to the do_start function in the init script:
# Assure that /var/run/postgrey exists
[ -d /var/run/postgrey ] || mkdir -p /var/run/postgrey
if [ "$DAEMON_USER" != "root" ]; then
chown "$DAEMON_USER" /var/run/postgrey
fi
-- System Information:
Debian Release: 9.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages postgrey depends on:
ii adduser 3.115
ii debconf [debconf-2.0] 1.5.61
pn libberkeleydb-perl <none>
pn libnet-dns-perl <none>
pn libnet-server-perl <none>
pn libnetaddr-ip-perl <none>
ii perl 5.24.1-3+deb9u2
ii ucf 3.0036
Versions of packages postgrey recommends:
pn libnet-rblclient-perl <none>
pn libparse-syslog-perl <none>
ii postfix 3.1.6-0+deb9u1
postgrey suggests no packages.
--- End Message ---
--- Begin Message ---
On Sat, 28 Oct 2017, Paul Lockaby wrote:
> Dear Maintainer,
>
> The default init script that comes with Postgrey on Debian 9 fails to start
> after a reboot.
> The installer creates /var/run/postgrey and writes its pid there
It seems to me that the default init script that ships with Debian 9
does not use the directory /var/run/postgrey.
Thus closing this bug.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `- https://www.debian.org/
--- End Message ---
