Upgrade fails. /etc/init.d/nscd stop returns exit code 1 when not running

Upgrading from what version to what version, please?

Good question. Whatever I had previously to 2.3.6-0ubuntu20.

wasabi@kyoto:~$ sudo /etc/init.d/nscd stop || echo 1
Stopping Name Service Cache Daemon: nscd.
1

Do prerm and postrm get run during upgrades? Looks like the try to stop and fail on error.

Dapper -> Edgy upgrade still affected by this bug as of the date of this post.

I'm seeing the same problem in an upgrade from dapper to edgy using update-manager -c -d. It stops the install, leaving the upgrade half-finished.

The *very* hackish way around the problem is to modify (after copying originals) /var/lib/dpkg/info/nscd.prerm and /etc/init.d/nscd to force exit status of 0 on stop. I don't know if both of these are necessary. I then removed the package, finished the upgrade, and reinstalled afterward restarting.

I think the following may be a related symptom.

I notice that the error "/usr/sbin/nscd: option `--invalidate' requires an argument" appears every time I run "/etc/init.d/nscd restart". I took a look at the man page for nscd, but could not figure out what kind of argument it was expecting after the "--invalidate" argument in /etc/init.d/nscd, line 89. As a temporary fix, I edited that file to give it the "all" argument, and that made things continue smoothly.

This error has happened ever since I installed edgy 2 days ago, so I don't think it's due to upgrading.

the nscd start script uses correct --invalidate parameters in feisty.