Bug#880047: postgrey: Regression - Postgrey doesn't start after installing new stable proposed-update
On Sat, Nov 10, 2018 at 01:37:20PM +, Roger Lynn wrote: > On 08/11/18 19:34, Adrian Bunk wrote: > > Tanks a lot for trying stretch-proposed-updates and reproting bugs you find! > > > > This is a regression that is also in 1.36-5 in unstable. > > > > The proposed 1.36-3+deb9u1 update has now been dropped from the upcoming > > stretch point release. > > Thank you for your work on this package. I think the reason my system was > badly affected by the new release is because I had used the example unix > socket location given in /usr/share/doc/postgrey/README.exim, which > conflicted with the new directory created in the init script (although to be > fair, the README does warn that the socket location might need to be > changed). I'd guess for stretch this just means that I'll prepare a 1.36-3+deb9u2 update that will revert to the situation 1.36-3 - I don't see any way to make this change in a safe way for stable then. > Regards, > > Roger Thanks again for reporting this issue Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#880047: postgrey: Regression - Postgrey doesn't start after installing new stable proposed-update
On 08/11/18 19:34, Adrian Bunk wrote: Tanks a lot for trying stretch-proposed-updates and reproting bugs you find! This is a regression that is also in 1.36-5 in unstable. The proposed 1.36-3+deb9u1 update has now been dropped from the upcoming stretch point release. Thank you for your work on this package. I think the reason my system was badly affected by the new release is because I had used the example unix socket location given in /usr/share/doc/postgrey/README.exim, which conflicted with the new directory created in the init script (although to be fair, the README does warn that the socket location might need to be changed). Regards, Roger
Processed: Re: Bug#880047: postgrey: Regression - Postgrey doesn't start after installing new stable proposed-update
Processing control commands:
> reopen -1
Bug #880047 {Done: Adrian Bunk } [postgrey] postgrey doesn't
start because it can't write its pid
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions postgrey/1.36-5.
> found -1 1.36-5
Bug #880047 [postgrey] postgrey doesn't start because it can't write its pid
Marked as found in versions postgrey/1.36-5.
--
880047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#880047: postgrey: Regression - Postgrey doesn't start after installing new stable proposed-update
Control: reopen -1 Control: found -1 1.36-5 On Mon, Nov 05, 2018 at 09:53:24PM +, Roger Lynn wrote: > Package: postgrey > Version: 1.36-3+deb9u1 > Followup-For: Bug #880047 > > On a Stable system installed about a year ago, Postgrey 1.36-3 has always run > fine. When installing 1.36-3+deb9u1 I get: > > Setting up postgrey (1.36-3+deb9u1) ... > Installing new version of config file /etc/init.d/postgrey ... > [] Starting postfix greylisting daemon: postgreymkdir: cannot create > directory ‘/var/run/postgrey/’: File exists > invoke-rc.d: initscript postgrey, action "start" failed. > > # /etc/init.d/postgrey stop > [] Stopping postfix greylisting daemon: postgreystart-stop-daemon: unable > to open pidfile /var/run/postgrey/postgrey.pid (Not a directory) > > # /etc/init.d/postgrey start > [] Starting postfix greylisting daemon: postgreymkdir: cannot create > directory ‘/var/run/postgrey/’: File exists > > $ ls -al /var/run/postgrey > srw-rw-rw- 1 postgrey postgrey 0 Oct 27 23:14 /var/run/postgrey > > After deleting /var/run/postgrey Postgrey will start, although subsequent > restarts give: > > # /etc/init.d/postgrey start > [] Starting postfix greylisting daemon: postgreyPid_file > "/var/run/postgrey/postgrey.pid" already exists. Overwriting! > . ok Tanks a lot for trying stretch-proposed-updates and reproting bugs you find! This is a regression that is also in 1.36-5 in unstable. The proposed 1.36-3+deb9u1 update has now been dropped from the upcoming stretch point release. > Thanks, > > Roger cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#880047: postgrey: Regression - Postgrey doesn't start after installing new stable proposed-update
Package: postgrey Version: 1.36-3+deb9u1 Followup-For: Bug #880047 On a Stable system installed about a year ago, Postgrey 1.36-3 has always run fine. When installing 1.36-3+deb9u1 I get: Setting up postgrey (1.36-3+deb9u1) ... Installing new version of config file /etc/init.d/postgrey ... [] Starting postfix greylisting daemon: postgreymkdir: cannot create directory ‘/var/run/postgrey/’: File exists invoke-rc.d: initscript postgrey, action "start" failed. # /etc/init.d/postgrey stop [] Stopping postfix greylisting daemon: postgreystart-stop-daemon: unable to open pidfile /var/run/postgrey/postgrey.pid (Not a directory) # /etc/init.d/postgrey start [] Starting postfix greylisting daemon: postgreymkdir: cannot create directory ‘/var/run/postgrey/’: File exists $ ls -al /var/run/postgrey srw-rw-rw- 1 postgrey postgrey 0 Oct 27 23:14 /var/run/postgrey After deleting /var/run/postgrey Postgrey will start, although subsequent restarts give: # /etc/init.d/postgrey start [] Starting postfix greylisting daemon: postgreyPid_file "/var/run/postgrey/postgrey.pid" already exists. Overwriting! . ok Thanks, Roger -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages postgrey depends on: ii adduser3.115 ii debconf [debconf-2.0] 1.5.61 ii libberkeleydb-perl 0.55-1+b2 ii libnet-dns-perl1.07-1 ii libnet-server-perl 2.008-3 ii libnetaddr-ip-perl 4.079+dfsg-1+b1 ii perl 5.24.1-3+deb9u4 ii ucf3.0036 Versions of packages postgrey recommends: ii exim4 4.89-2+deb9u3 ii libnet-rblclient-perl 0.5-3 ii libparse-syslog-perl 1.10-2 postgrey suggests no packages. -- debconf information: postgrey/1.32-3_changeport:
