package nut-client 2.7.2-4ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nut (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Tried to upgrade from 14.04 to 16.04. Will try to see what works after the upgrade and update this report.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nut-client 2.7.2-4ubuntu1
ProcVersionSign
Uname: Linux 3.13.0-65-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Nov 4 16:29:15 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
KernelVersion: Linux azda.mooo.com 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.12~
SourcePackage: nut
Title: package nut-client 2.7.2-4ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
USBDevices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
UpgradeStatus: Upgraded to xenial on 2016-11-04 (0 days ago)
mtime.conffile.
tags: | removed: need-duplicate-check |
There is this all over the place in the log:
insserv: script nut-client: service nut-client already provided!
insserv: script nut-client: service upsmon already provided!
insserv: script nut-client: service ups-monitor already provided!
And finally giving up on:
Setting up nut-client (2.7.2-4ubuntu1) ...
insserv: script nut-client: service nut-client already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
Was there anything special in regard to your nut setup?
I see the conffile was modified, so maybe there was some tweaking to the init scripts as well?
I had no UPS around to try, but installed nut-client until it ran it with MINSUPPLIES 0 to get it running. Then I upgraded from Trusty to Xenial to see if the issue is reproducible.
But the upgrade worked and nut-client is still running fine after the upgrade.
Looking forward to your follow on update to the bug on your current status.