postfix-policyd init script doesn't behave
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| postfix-policyd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: postfix-policyd
Hi!
The following happens when an install failed, and i have to run dpkg --configure -a again:
root@ubuntu:~# dpkg --configure -a
Setting up postfix-policyd (1.80-2.1) ...
dbconfig-common: writing config to /etc/dbconfig-
Starting Postfix greylisting policy daemon: invoke-rc.d: initscript postfix-policyd, action "start" failed.
dpkg: error processing postfix-policyd (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
postfix-policyd
root@ubuntu:~# /etc/init.
Stopping Postfix greylisting policy daemon: postfix-policyd.
root@ubuntu:~# dpkg --configure -a
Setting up postfix-policyd (1.80-2.1) ...
dbconfig-common: writing config to /etc/dbconfig-
Starting Postfix greylisting policy daemon: postfix-policyd.
postfix-policyd errors out when you do a start when the program is already running.. Maybe implementing "status", or make start be more forgiving would fix this?
Thanks in advance!
Related branches
| Daniel Hahler (blueyed) wrote | #1 |
| Changed in postfix-policyd: | |
| status: | New → Confirmed |
| Daniel Hahler (blueyed) wrote | #2 |
| Daniel Hahler (blueyed) wrote | #3 |
| Changed in postfix-policyd: | |
| status: | Confirmed → Fix Released |
| Daniel Hahler (blueyed) wrote | #4 |
This seems also to be also the cause of the problem when upgrading postfix-policyd: dh_installinit gets used in debian/rules and adds a block to the postinst script to "start" (not restart!?) the service. This fails and therefor the upgrade fails!