Hi, I just ran into the same thing; my first thought was the same as Eloy's (IPv4/IPv6 problem).
However, the real problem is quite different: the init.d script does this to stop spamd: start-stop-daemon --stop --pidfile /var/run/spamd.pid --exec /usr/bin/perl --oknodo However, perl had been upgraded earlier, hence the perl binary running spamd is NOT the current /usr/bin/perl which results in start-stop-daemon reporting: No /usr/bin/perl found running; none killed. Hence the supposed restart fails because the old spamd is still listening to the spamd ports. I don't quite understand the reasoning behind supplying "--exec /usr/bin/perl" to start-stop-daemon, except perhaps to be extra safe to prevent killing the wrong process in case of a stale pid file. I recommend simply removing "--exec /usr/bin/perl" from the start-stop-daemon invocation. Another note: dpkg --configure --pending did run the postinst script, but that only tries to start the new daemon, assuming the daemon was already stopped, so even after I had removed the --exec part configuration still failed; I needed to manually stop spamassassin first. Perhaps do a restart instead of start in postinst? Paul -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
