Your message dated Sun, 4 Sep 2016 20:17:47 +0000
with message-id <20160904201747.oyojzx6czd5qw...@cherubino.dyne.org>
and subject line Re: Bug#836071: Info received (Bug#836071: postgrey: cannot be 
upgraded: initscript postgrey, action "stop" failed)
has caused the Debian Bug report #836071,
regarding postgrey: cannot be upgraded: initscript postgrey, action "stop" 
failed
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.)


-- 
836071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgrey
Version: 1.36-2
Severity: serious
Justification: Policy 3.9

The following packages will be upgraded:
  postgrey
1 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.
Need to get 0 B/57.2 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
apt-listchanges: Reading changelogs...
Preconfiguring packages ...
(Reading database ... 386473 files and directories currently installed.)
Preparing to unpack .../postgrey_1.36-3_all.deb ...
Stopping postfix greylisting daemon: postgreyinvoke-rc.d: initscript postgrey, 
action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Stopping postfix greylisting daemon: postgreyinvoke-rc.d: initscript postgrey, 
action "stop" failed.
dpkg: error processing archive /var/cache/apt/archives/postgrey_1.36-3_all.deb 
(--unpack):
 subprocess new pre-removal script returned error exit status 1
Starting postfix greylisting daemon: postgreycan't open 
/etc/postfix/whitelist_recipients: No such file or directory
Pid_file "/var/run/postgrey.pid" already exists.  Overwriting!
.
Errors were encountered while processing:
 /var/cache/apt/archives/postgrey_1.36-3_all.deb


When I manually sudo touch /etc/postfix/whitelist_recipients:

The following packages will be upgraded:
  postgrey
1 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.
Need to get 0 B/57.2 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
[master f9bb472] saving uncommitted changes in /etc prior to apt run
 2 files changed, 1 insertion(+)
 create mode 100644 postfix/whitelist_recipients
apt-listchanges: Reading changelogs...
Preconfiguring packages ...
(Reading database ... 386473 files and directories currently installed.)
Preparing to unpack .../postgrey_1.36-3_all.deb ...
Stopping postfix greylisting daemon: postgreyinvoke-rc.d: initscript postgrey, 
action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Stopping postfix greylisting daemon: postgreyinvoke-rc.d: initscript postgrey, 
action "stop" failed.
dpkg: error processing archive /var/cache/apt/archives/postgrey_1.36-3_all.deb 
(--unpack):
 subprocess new pre-removal script returned error exit status 1
Starting postfix greylisting daemon: postgreyPid_file "/var/run/postgrey.pid" 
already exists.  Overwriting!
.
Errors were encountered while processing:
 /var/cache/apt/archives/postgrey_1.36-3_all.deb


Manual stopping is also without success:

sudo start-stop-daemon --user postgrey --stop '--retry=TERM/30/KILL/5' 
--pidfile /var/run/postgrey.pid
No process in pidfile '/var/run/postgrey.pid' found running; none killed.

Working around that is also no success:

1|tglase@tglase:~ $ sudo rm /var/run/postgrey.pid
tglase@tglase:~ $ sudo service postgrey stop; echo = $?
Stopping postfix greylisting daemon: postgrey= 1
tglase@tglase:~ $ sudo service postgrey start; echo = $?
Starting postfix greylisting daemon: postgrey.
= 0
tglase@tglase:~ $ sudo service postgrey stop; echo = $?
Stopping postfix greylisting daemon: postgrey= 1
tglase@tglase:~ $ sudo cat /var/run/postgrey.pid
16585

The cause appears to be that starting it does not work:

tglase@tglase:~ $ ps ax | fgrep -e postgrey -e 16585
15476 pts/6    S+     0:00 /usr/bin/python /usr/bin/reportbug postgrey
15558 pts/6    S+     0:00 sh -c /usr/bin/jupp  
'/tmp/reportbug-postgrey-20160830-15476-tiR55w'
15559 pts/6    S+     0:00 /usr/bin/jupp 
/tmp/reportbug-postgrey-20160830-15476-tiR55w
16602 pts/5    S+     0:00 grep -F -e postgrey -e 16585

I find the following in syslog:

Aug 30 14:01:19 tglase postgrey[16585]: Process Backgrounded
Aug 30 14:01:19 tglase postgrey[16585]: 2016/08/30-14:01:19 postgrey (type 
Net::Server::Multiplex) starting! pid(16585)
Aug 30 14:01:19 tglase postgrey[16585]: Resolved [localhost]:10023 to 
[127.0.0.1]:10023, IPv4
Aug 30 14:01:19 tglase postgrey[16585]: Binding to TCP port 10023 on host 
127.0.0.1 with IPv4
Aug 30 14:01:19 tglase postgrey[16585]: Setting gid to "139 139"
Aug 30 14:01:19 tglase postgrey[16585]: Setting uid to "125"
Aug 30 14:01:19 tglase postgrey[16585]: FATAL: ERROR: can't open lock file: 
/var/spool/postfix/postgrey/postgrey.lock


And indeed:

ls: cannot access '/var/spool/postfix/postgrey': No such file or directory


-- System Information:
Debian Release: stretch/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages postgrey depends on:
ii  adduser                3.115
ii  debconf [debconf-2.0]  1.5.59
ii  libberkeleydb-perl     0.55-1+b1
ii  libnet-dns-perl        1.06-1
ii  libnet-server-perl     2.008-3
ii  libnetaddr-ip-perl     4.079+dfsg-1
ii  perl                   5.22.2-3
ii  ucf                    3.0036

Versions of packages postgrey recommends:
pn  libnet-rblclient-perl  <none>
pn  libparse-syslog-perl   <none>
ii  postfix                3.1.0-5+b1

postgrey suggests no packages.

-- debconf information:
  postgrey/1.32-3_changeport:

--- End Message ---
--- Begin Message ---
Closing this bug as it is fixed already, please reopen if it's not the case.
Thanks!

--- End Message ---

Reply via email to