It looks like when trying to remove the old package, it couldn't stop
the daemon
Preparing to replace pdns-recursor 3.1.7.2-1 (using
.../pdns-recursor_3.3-2~lucid1_i386.deb) ...
* Stopping PowerDNS recursor pdns-recursor
invoke-rc.d: initscript pdns-recursor, action "stop" failed.
dpkg: warning: old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
* Stopping PowerDNS recursor pdns-recursor
invoke-rc.d: initscript pdns-recursor, action "stop" failed.
dpkg: ... it looks like that went OK.
Unpacking replacement pdns-recursor ...
After installing the new package, it seems the recursor (or something)
was still running (as it couldn't stop it before), that's why the start
fails.
Installing new version of config file
/etc/logcheck/ignore.d.server/pdns-recursor ...
* Starting PowerDNS recursor pdns-recursor
Nov 17 08:41:54 Exception: Resolver binding to server socket on port 53 for
127.0.0.1: Address already in use
...fail!
invoke-rc.d: initscript pdns-recursor, action "start" failed.
dpkg: error processing pdns-recursor (--configure):
Did you have some custom configuration? Any reason why the old removal
script would have problems stopping the daemon?
I've tried to reproduce this problem on my Lucid, upgraded to 3.3-2 and
I didn't have this problem. Of course I had the default install with the
default configuration.
** Changed in: pdns-recursor (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891623
Title:
package pdns-recursor 3.3-2~lucid1 failed to install/upgrade:
subprocess installed post-installation script returned error exit
status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pdns-recursor/+bug/891623/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
