Errors When Updating from Ubuntu Server 14.04 to 14.10
-
@scottalanmiller said:
Did you do a full...
apt-get update && apt-get upgrade
Before doing the version update?
Yup. Several times in fact.
-
And they were successful?
-
-
This is the result of the apt-get autoremove
root@thanksaj:/home/aj# apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
gir1.2-javascriptcoregtk-3.0 gir1.2-soup-2.4 gir1.2-webkit-3.0 libgeoclue0
libharfbuzz-icu0 libice6 libjavascriptcoregtk-3.0-0 libpng12-0:i386
libsecret-1-0 libsecret-common libsm6 libwebkitgtk-3.0-0
libwebkitgtk-3.0-common libxt6
0 upgraded, 0 newly installed, 14 to remove and 805 not upgraded.
8 not fully installed or removed.
After this operation, 43.0 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 148542 files and directories currently installed.)
Removing gir1.2-webkit-3.0 (2.4.4-1~ubuntu1) ...
Removing gir1.2-javascriptcoregtk-3.0 (2.4.4-1~ubuntu1) ...
Removing gir1.2-soup-2.4 (2.44.2-1ubuntu2) ...
Removing libwebkitgtk-3.0-0:amd64 (2.4.4-1~ubuntu1) ...
Removing libgeoclue0:amd64 (0.12.99-3ubuntu1) ...
Removing libharfbuzz-icu0:amd64 (0.9.27-1ubuntu1) ...
Removing libxt6:amd64 (1:1.1.4-1) ...
Removing libsm6:amd64 (2:1.2.1-2) ...
Removing libice6:amd64 (2:1.0.8-2) ...
Removing libjavascriptcoregtk-3.0-0:amd64 (2.4.4-1~ubuntu1) ...
Removing libpng12-0:i386 (1.2.50-1ubuntu2) ...
Removing libsecret-1-0:amd64 (0.16-0ubuntu1) ...
Removing libsecret-common (0.16-0ubuntu1) ...
Removing libwebkitgtk-3.0-common (2.4.4-1~ubuntu1) ...
Processing triggers for libc-bin (2.19-10ubuntu2) ...
Setting up initscripts (2.88dsf-41ubuntu18) ...
insserv: warning: script 'S99notify_fs_event' missing LSB tags and overrides
insserv: warning: script 'notify_fs_event' missing LSB tags and overrides
insserv: warning: script 'cron' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for scriptcron' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script
cron'
insserv: warning: script 'watchdog' missing LSB tags and overrides
insserv: Starting notify_fs_event depends on grub-common and therefore on system facility$all' which can not be true! insserv: Starting notify_fs_event depends on grub-common and therefore on system facility
$all' which can not be true!
insserv: Starting notify_fs_event depends on grub-common and therefore on system facility$all' which can not be true! insserv: Starting notify_fs_event depends on grub-common and therefore on system facility
$all' which can not be true!
insserv: Starting notify_fs_event depends on grub-common and therefore on system facility$all' which can not be true! insserv: Starting notify_fs_event depends on grub-common and therefore on system facility
$all' which can not be true!
insserv: Starting notify_fs_event depends on grub-common and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service notify_fs_event and grub-common if started
insserv: loop involving service grub-common at depth 9
insserv: loop involving service notify_fs_event at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package initscripts (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of upstart-bin:
upstart-bin depends on initscripts; however:
Package initscripts is not configured yet.dpkg: error processing package upstart-bin (--configure):
dependency problems - leaving unconfigured
Setting up grub-common (2.02~beta2-15) ...
No apport report written because the error message indicates its a followup error from a previous failure.
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
insserv: warning: script 'S99notify_fs_event' missing LSB tags and overrides
insserv: warning: script 'notify_fs_event' missing LSB tags and overrides
insserv: warning: script 'cron' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for scriptcron' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script
cron'
insserv: warning: script 'watchdog' missing LSB tags and overrides
insserv: Starting notify_fs_event depends on grub-common and therefore on system facility$all' which can not be true! insserv: Starting notify_fs_event depends on grub-common and therefore on system facility
$all' which can not be true!
insserv: Starting notify_fs_event depends on grub-common and therefore on system facility$all' which can not be true! insserv: Starting notify_fs_event depends on grub-common and therefore on system facility
$all' which can not be true!
insserv: Starting notify_fs_event depends on grub-common and therefore on system facility$all' which can not be true! insserv: Starting notify_fs_event depends on grub-common and therefore on system facility
$all' which can not be true!
insserv: Starting notify_fs_event depends on grub-common and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service notify_fs_event and grub-common if started
insserv: loop involving service grub-common at depth 9
insserv: loop involving service notify_fs_event at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package grub-common (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of upstart:
upstart depends on upstart-bin (= 1.13.2-0ubuntu2); however:
Package upstart-bin is not configured yet.
upstart depends on initscripts; however:
Package initscripts is not configured yet.dpkg: error processing package upstart (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of friendly-recovery:
friendly-recovery depends on upstart | systemd-sysv; however:
Package upstart is not configured yet.
Package systemd-sysv is not installed.dpkg: error processing package friendly-recovery (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of grub2-common:
grub2-common depends on grub-common (= 2.02~beta2-15); however:
Package grub-common is not configured yet.dpkg: error processing package grub2-common (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of grub-pc-bin:
grub-pc-bin depends on grub-common (= 2.02~beta2-15); however:
Package grub-common is not configured yet.dpkg: error processing package grub-pc-bin (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of grub-pc:
grub-pc depends on grub-common (= 2.02~beta2-15); however:
Package grub-common is not configured yet.
grub-pc depends on grub2-common (= 2.02~beta2-15); however:
Package grub2-common is not configured yet.
grub-pc depends on grub-pc-bin (= 2.02~beta2-15); however:
Package grub-pc-bin is not configured yet.dpkg: error processing package grub-pc (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
Errors were encountered while processing:
initscripts
upstart-bin
grub-common
upstart
friendly-recovery
grub2-common
grub-pc-bin
grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1) -
From what I can tell (I really dislike apt-get) these are the bits that really matter:
update-rc.d: error: insserv rejected the script header dpkg: error processing package initscripts (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initscripts
-
@scottalanmiller said:
From what I can tell (I really dislike apt-get) these are the bits that really matter:
update-rc.d: error: insserv rejected the script header dpkg: error processing package initscripts (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initscripts
Ok, so what do I do with them?
-
What has been done to the machine outside of letting the package manager handle everything?
-
@scottalanmiller said:
What has been done to the machine outside of letting the package manager handle everything?
I just put Pertino on today, or tried to again. Working with them on it now because it's installed and running but the pertino0 interface doesn't exist...
-
@scottalanmiller said:
scottalanmiller
From what I can tell (I really dislike apt-get) these are the bits that really matter:update-rc.d: error: insserv rejected the script header
It's not working for me on Fedora either.
-
Ok, so dpkg seems to be the issue, specifically when it tries to run a dpkg --configure on some packages. I am trying updating again but via aptitude now. I don't know if it will make any difference, but here is the link I found:
http://www.linuxquestions.org/questions/linux-newbie-8/ubuntu-'dpkg-configure-a'-e-dpkg-was-interrupted-error-695895/"sudo aptitude safe-upgrade" is the command I'm running, which appears to do the same as apt-get upgrade. We'll see if it works. I'll keep you posted, but I am basically unable to install, update or remove any packages at this point via apt-get.
-
This is what I'm getting, as the packages with issues.
dpkg: error processing package friendly-recovery (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: pertino-client initscripts upstart-bin upstart friendly-recovery
-
Try removing Pertino before updating.
-
@scottalanmiller said:
Try removing Pertino before updating.
I can't remove anything. I tried doing an
apt-get purge initscripts upstart-bin upstart friendly-recovery
I figured if things were hosed on those items, I'd rip and reinstall. As the text started flying, I noticed it removing things like mysql-server and the like. All I could think was "oh shit!" because now my Wordpress is hosed, and I can't take a backup of my MySQL databases because running
mysql -u root -p
generates an error and so I am stuck in limbo with my MySQL. I checked my backups on my UEB and I have good backups so I'm restoring from the 19th and hopefully that'll roll back all these changes and I can get a fresh slate.
-
Used my Unitrends UEB to do a restore from last Thursday, the day before all this madness started, and rebooted. Running an
apt-get upgrade
now and it's going through. Going to run
apt-get dist-upgrade
now and that should upgrade me to 14.10.
-
So package management is working again.
Following the CLI tutorial found here:
http://www.noobslab.com/2014/10/how-to-upgrade-from-any-ubuntu-version.htmlIt's going through the upgrade now.
-
Any idea what broke?
-
@scottalanmiller said:
Any idea what broke?
Yup, because the issue just happened again. Something about updating to 14.10 breaks it...
root@thanksaj:/home/aj# do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [198 B]
Get:2 Upgrade tool [1,147 kB]
Fetched 1,148 kB in 0s (0 B/s)
authenticate 'utopic.tar.gz' against 'utopic.tar.gz.gpg'
extracting 'utopic.tar.gz'dpkg: error processing package friendly-recovery (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.19-10ubuntu2) ...
Processing triggers for initramfs-tools (0.103ubuntu8) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-37-generic
Processing triggers for ureadahead (0.100.0-16) ...
Errors were encountered while processing:
grub-common
grub-pc-bin
initscripts
grub-pc
grub2-common
upstart-bin
upstart
friendly-recoveryUpgrade complete
The upgrade has completed but there were errors during the upgrade
process.Just got that...
-
Going to restore back to Thursday again. I can't seem to update to 14.10 without stuff breaking...
-
Ubuntu is not the most stable of platforms, sadly. I would only recommend it when you have a very specific need and never "just because."
-
Did you remember to do....
apt-get update && apt-get upgrade && reboot
Before trying the distro update?