package quagga 0.99.24.1-2ubuntu1.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Snehal Basawnathes]

package quagga 0.99.24.1-2ubuntu1.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: quagga 0.99.24.1-2ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Tue Apr 24 08:46:02 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-01-30 (448 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt 1.2.26
SourcePackage: quagga
Title: package quagga 0.99.24.1-2ubuntu1.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.quagga.daemons: 2017-09-01T23:15:17.682434

[Christian Ehrhardt  (paelzer)]

From your log:
*** As requested via Debconf, the Quagga daemon will not stop! ***
dpkg: warning: subprocess old pre-removal script returned error exit status 1

[Christian Ehrhardt  (paelzer)]

I also see the config is modified, but it will need to successfully restart the service to upgrade.
Could that be it?

Would you mind reverting to the default config for a try and upgrade it then.
Does that work?

[Christian Ehrhardt  (paelzer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

[Launchpad Janitor (janitor)]

[Expired for quagga (Ubuntu) because there has been no activity for 60 days.]