package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1607874 reported by Didi Dwi Novianto
76
This bug affects 15 people
Affects Status Importance Assigned to Milestone
sysvinit (Ubuntu)
High
Unassigned

Bug Description

ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sysv-rc.0.crash'

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sysv-rc 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
Uname: Linux 3.13.0-57-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Jul 29 23:52:04 2016
DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (833 days ago)
InstallationMedia:

PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.0.1ubuntu2.14
SourcePackage: sysvinit
Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

Revision history for this message
Didi Dwi Novianto (dididwinovianto) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sysvinit (Ubuntu):
status: New → Confirmed
Changed in sysvinit (Ubuntu):
importance: Undecided → High
Revision history for this message
Rudi Hansen (rsh-pobox) wrote :

I get this error when trying to do a release upgrade from 14.04.5 LTS to 16.04.3 LTS

Witch surprises me when i see this bug was reported almost one year ago.
Any chance this will be fixed?

Revision history for this message
selinuxium (selinuxium) wrote :

Just suffered this issue myself.

Winding back to previous state.

Revision history for this message
John Wilson (jowilhnson) wrote :

Same. Attempted upgrade from 14.04.5 LTS to 16.04.3 LTS

Revision history for this message
Greg Rundlett (greg.rundlett) wrote :

#metoo

Revision history for this message
somekool (somekool) wrote :

#metoo !

14.04 is about to go out of support, I think a lot of people will attempt to upgrade their base AMI from 14.04 to 16.04

at least, that's my case.

if this 3 years old bug still unassigned. does this mean this upgrade path from LTS to LTS is not possible ?!?

Revision history for this message
Randall Whitman (ubuntu-whizman) wrote :

"not possible" - In my experience with a handful of machines, upgrade to 16.04 was possible on all but one, but not smooth on any (as far as I remember). On the machine which encountered this specific error, it took some searching on the error message, then running the plausible relevant commands (I think apt-get and/or dpkg, but I do not remember offhand).

Revision history for this message
tuxayo (tuxayo) wrote :

Hi, I upgraded a Ubuntu 14.04 to 16.04 and got many failed packages configurations during the upgrade. It's likely due to this.

After the upgrade, *before rebooting*, I did

dpkg --configure --pending

remaining errors were on linux-* packages and initramsfs-tools, still not rebooted.

I removed old packages from kernel 3.13 that where still here and caused failures on microcode

dpkg --configure -a
issue with casper-memdisk

Removed it: https://askubuntu.com/questions/624519/upgrade-from-14-04-to-15-04-fails/635679#635679
sudo dpkg -P casper-memdisk

dpkg --configure -a
success

reboot, doesn't boot

grub => failsafe
in menu select => continue normal boot (actually that's not a normal boot, I guess things like nomodeset have been added)
boot success

To be continued: to be able to normally boot. But I hope that these details can help someone else. (disclaimer: I might have done something stupid ^^")

Revision history for this message
somekool (somekool) wrote :

I have succeed doing the upgrade of this important 14.04 machine to 16.04

I went through the long error logs
/var/crash/sysv-rc.0.crash and the longer one on do-release upgrade

 and I found this piece of info...

I had a custom init.d file that depend on rc.local
but rc.local depends on $all

there is a script that tries to convert init script into systemd
but could not figure out which comes first
my script depending on rc.local and rc.local depending on $all did not make sense.

I also deleted all packages that I could

and the upgrade succeeded

list of packages I have removed

```
libapt-inst1.4
libbind9-80
libboost-iostreams1.46.1
libcdt4
libcgraph5
libcolorhug1
libdconf0
libdns81
libdrm-nouveau1a
libgcj12
libgd2-noxpm
libgphoto2-port10
libgraph4
libgvc5
libgvpr1
libicu48
libisc83
libisccc80
libisccfg82
libkadm5clnt-mit8
libkdb5-6
liblcms1
libllvm3.0
liblwres80
libmagickcore4
libmagickwand4
libmpc2
libsystemd-daemon0
libtasn1-3
libtiff4
libtiffxx0c2
libudev0
linux-image-3.2.0-68-virtual
linux-image-3.2.0-69-virtual
linux-image-3.2.0-72-virtual
linux-image-3.2.0-77-virtual
linux-image-3.2.0-84-virtual
linux-image-3.2.0-86-virtual
linux-image-3.2.0-89-virtual
linux-image-3.2.0-97-virtual
linux-image-3.2.0-98-virtual
libcairo2:amd64
librsvg2-2:amd64
libcairo2-dev:amd64
libcairo-script-interpreter2:amd64
libcairo-gobject2:amd64
librsvg2-dev:amd64
libpangocairo-1.0-0:amd64
librsvg2-common:amd64
libpangoft2-1.0-0:amd64
libgdk-pixbuf2.0-dev
libmagickcore-6.q16-3-extra:amd64
gir1.2-rsvg-2.0:amd64
libmagickcore-6.q16-dev:amd64
python3-lib2to3
python3-distutils
libglib2.0-dev-bin
libmagickcore-dev
libglib2.0-dev:amd64
libmagickwand-dev
libmagickwand-6.q16-dev:amd64
```

Revision history for this message
somekool (somekool) wrote :

look for a file like this one .... /var/lib/insserv/run-*.log

 Setting up sysv-rc (2.88dsf-59.3ubuntu2) ...
 info: Reordering boot system, log to /var/lib/insserv/run-20190705T0527.log
 error: Something failed while migrating.

 error: Unable to migrate to dependency based boot sequencing.

 See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for
 more information about dependency based boot sequencing. To

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers