package openvpn 2.3.10-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openvpn (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
During installation conflict with udev and installation was failed
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openvpn 2.3.10-1ubuntu2
ProcVersionSign
Uname: Linux 4.4.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
libpkcs11-helper1: Install
openvpn: Install
libpkcs11-helper1: Configure
openvpn: Configure
NULL: ConfigurePending
Architecture: amd64
Date: Wed Oct 19 17:33:04 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-03-17 (216 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.12~
SourcePackage: openvpn
Title: package openvpn 2.3.10-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-07-30 (81 days ago)
tags: | removed: need-duplicate-check |
Hi,
thank you for your time to report the bug and help making Ubuntu better.
From the log:
insserv: warning: script 'S65nifi' missing LSB tags and overrides
insserv: warning: script 'nifi' missing LSB tags and overrides
insserv: There is a loop between service nifi and urandom if started
insserv: loop involving service urandom at depth 4
insserv: loop involving service hwclock at depth 3
insserv: There is a loop between service plymouth and udev if started
insserv: loop involving service udev at depth 1
insserv: Starting nifi depends on plymouth and therefore on system facility `$all' which can not be true!
[...]
insserv: Max recursions depth 99 reached
[...]
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
Did you manually install a version of https:/ /nifi.apache. org/ that is conflicting with the systems init scripts?
If so removing its content might free you up to get back working.
At least remove the incompatible init scripts at
/etc/rc2.d/S65nifi
/etc/init.d/nifi
/etc/rc2.d/K65nifi