insserv & udev errors during upgrade

Ibilata_Bingbingbing · 02-01-2017, 10:04 AM

Hi all,

I'm trying to do a general upgrade using apt and the thing craps out every time, apparently because of an error with udev. The only thing I've done recently is try to install a newer version of cups, which didn't work (hence the insserv error, I assume). Can anyone help me get rid of these two errors? I have absolutely no idea where to start...

Thanks!

Code:

The following packages will be upgraded:
  bunsen-common bunsen-configs bunsen-faenza-icon-theme bunsen-images
  bunsen-meta-java bunsen-meta-libreoffice bunsen-os-release bunsen-pipemenus
  bunsen-python-apt-template bunsen-utilities bunsen-welcome ca-certificates dbus
  dbus-x11 file firefox-esr google-chrome-stable iceweasel intel-microcode jq
  libcomerr2 libgnutls-deb0-28 libgnutls-openssl27 libgudev-1.0-0 libhogweed2
  liblcms2-2 libmagic1 libmpg123-0 libmysqlclient18 libnettle4 libobrender29
  libobt2 libopenjp2-7 libpam-modules libpam-modules-bin libpam-runtime
  libpam-systemd libpam0g libqt5concurrent5 libqt5core5a libqt5dbus5 libqt5gui5
  libqt5network5 libqt5opengl5 libqt5printsupport5 libqt5sql5 libqt5sql5-sqlite
  libqt5widgets5 libss2 libssl1.0.0 libsystemd0 libtiff5 libwmf0.2-7 libxpm4
  linux-compiler-gcc-4.8-x86 linux-headers-3.16.0-4-amd64
  linux-headers-3.16.0-4-common linux-image-3.16.0-4-amd64 locales
  multiarch-support mysql-common openbox openssl python-crypto suckless-tools
  systemd systemd-sysv virtualbox-5.1 w3m wireless-regdb
70 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/224 MB of archives.
After this operation, 521 kB disk space will be freed.
Do you want to continue? [Y/n] y
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up udev (215-17+deb8u6) ...
addgroup: The group `input' already exists as a system group. Exiting.
update-initramfs: deferring update (trigger activated)
insserv: warning: script 'K36cups' missing LSB tags and overrides
insserv: warning: script 'cups' missing LSB tags and overrides
insserv: There is a loop at service rc.local if started
insserv: There is a loop between service rc.local and mountnfs if started
insserv:  loop involving service mountnfs at depth 8
insserv:  loop involving service networking at depth 7
insserv: There is a loop between service cups and mountall if started
insserv:  loop involving service mountall at depth 5
insserv:  loop involving service checkroot-bootclean at depth 4
insserv:  loop involving service urandom at depth 7
insserv: There is a loop between service rc.local and mountdevsubfs if started
insserv:  loop involving service mountdevsubfs at depth 2
insserv:  loop involving service udev at depth 1
insserv: There is a loop at service cups if started
insserv:  loop involving service mountnfs-bootclean at depth 7
insserv: There is a loop between service cups and mountall-bootclean if started
insserv:  loop involving service mountall-bootclean at depth 1
insserv:  loop involving service hwclock at depth 4
insserv:  loop involving service rc.local at depth 2
insserv:  loop involving service cups at depth 1
insserv: There is a loop between service rc.local and mountnfs-bootclean if started
insserv:  loop involving service rsyslog at depth 1
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting cups depends on rc.local 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
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools (0.120+deb8u2) ...
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
Errors were encountered while processing:
 udev
E: Sub-process /usr/bin/dpkg returned an error code (1)

hydrurga · 02-02-2017, 02:54 AM

I think that the important line here may be:

Code:

1 not fully installed or removed.

Can you run apt check and paste the output here please. Also please let us know which distro and version you are running, and where you got the newer version of cups.

Ibilata_Bingbingbing · 02-02-2017, 04:15 AM

Of course, yes, sorry. I'm running Bunsenlabs 8.6 Debian Jessie. For CUPS I downloaded the official source for 2.2.1 from https://github.com/apple/cups/releases.

*apt check* came up with

Code:

E: Invalid operation check

and *apt-get check -v* returned

Code:

apt 1.0.9.8.4 for amd64 compiled on Dec 11 2016 09:48:19
Supported modules:
*Ver: Standard .deb
 Pkg:  Debian APT solver interface (Priority -1000)
*Pkg:  Debian dpkg interface (Priority 30)
 S.L: 'deb' Standard Debian binary tree
 S.L: 'deb-src' Standard Debian source tree
 Idx: EDSP scenario file
 Idx: Debian Source Index
 Idx: Debian Package Index
 Idx: Debian Translation Index
 Idx: Debian dpkg status file

Doesn't look particularly informative to me...

hydrurga · 02-02-2017, 04:35 AM

Quote:

Originally Posted by Ibilata_Bingbingbing

Of course, yes, sorry. I'm running Bunsenlabs 8.6 Debian Jessie. For CUPS I downloaded the official source for 2.2.1 from https://github.com/apple/cups/releases.

*apt check* came up with

Code:

E: Invalid operation check

and *apt-get check -v* returned

Code:

apt 1.0.9.8.4 for amd64 compiled on Dec 11 2016 09:48:19
Supported modules:
*Ver: Standard .deb
 Pkg:  Debian APT solver interface (Priority -1000)
*Pkg:  Debian dpkg interface (Priority 30)
 S.L: 'deb' Standard Debian binary tree
 S.L: 'deb-src' Standard Debian source tree
 Idx: EDSP scenario file
 Idx: Debian Source Index
 Idx: Debian Package Index
 Idx: Debian Translation Index
 Idx: Debian dpkg status file

Doesn't look particularly informative to me...

Neither to me! :-)

I was hoping that you had an up-to-date version of apt that supported apt check, sorry about that.

You were right to try apt-get check, but not with the -v flag which takes priority and prints the version info, no matter the apt-get command specified.

Can you try apt-get check on its own?

Ibilata_Bingbingbing · 02-02-2017, 05:01 AM

That's the reason I did -v

Code:

sudo apt-get check
Reading package lists... Done
Building dependency tree       
Reading state information... Done

Doesn't -v mean verbose?

From what I can tell, something isn't installed properly, but the system thinks everything's hunky-dory...

Would everything go boom if I just uninstalled udev?

Ibilata_Bingbingbing · 02-02-2017, 05:10 AM

So, I did some spellunking and found the dpkg command to list incomplete installations. It returned this:

Code:

sudo dpkg -C
The following packages are only half configured, probably due to problems
configuring them the first time.  The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
 udev                 /dev/ and hotplug management daemon

I tried --configure but the error seems to be IN the udev configuration process!

So confus.

Here's the info on udev:

Code:

Package: udev
Status: install ok half-configured
Priority: important
Section: admin
Installed-Size: 6048
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Architecture: amd64
Multi-Arch: foreign
Source: systemd
Version: 215-17+deb8u6
Config-Version: 215-17+deb8u5
Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.17), libkmod2 (>= 5~), libselinux1 (>= 2.0.65), libudev1 (= 215-17+deb8u6), adduser, lsb-base (>= 3.0-6), util-linux (>= 2.16), procps
Pre-Depends: debconf (>= 1.4.69) | debconf-2.0
Breaks: consolekit (<< 0.4.6-1), kmod (<< 14), plymouth (<< 0.9.0-7), systemd (<< 215-1)
Conffiles:
 /etc/init.d/udev 988e81a81706a99e7f4b83988b386b00
 /etc/init.d/udev-finish fd3ce194c134bcd790681ea487b19126
 /etc/init/udev-fallback-graphics.conf b8bfe7164e10cd0e53494b243c5728b1
 /etc/init/udev-finish.conf 089140a32d519840674be9a274da1a42
 /etc/init/udev.conf 41c0081f3a830e0902aaff76a53edf98
 /etc/init/udevmonitor.conf b541dfb5aa4958e9a5336ecaec00ca15
 /etc/init/udevtrigger.conf 651ff2421dde80be7ce7ccbf7fa8cf18
 /etc/modprobe.d/fbdev-blacklist.conf 0b9c466830040ec52986cc3ea117bef5
 /etc/udev/udev.conf ae415f84e2967eff580089fb08aa0a61
Description: /dev/ and hotplug management daemon
 udev is a daemon which dynamically creates and removes device nodes from
 /dev/, handles hotplug events and loads drivers at boot time.
Homepage: http://www.freedesktop.org/wiki/Software/systemd

hydrurga · 02-02-2017, 05:34 AM

Quote:

Originally Posted by Ibilata_Bingbingbing

That's the reason I did -v

Code:

sudo apt-get check
Reading package lists... Done
Building dependency tree       
Reading state information... Done

Doesn't -v mean verbose?

From what I can tell, something isn't installed properly, but the system thinks everything's hunky-dory...

Would everything go boom if I just uninstalled udev?

No, -v shows the program version, although -V shows some verbosity as regards displaying full package versions.

Yes, boom or simper...

You could try re-installing udev:

sudo apt-get install --reinstall udev

No guarantees though.

Ibilata_Bingbingbing · 02-02-2017, 05:44 AM

Yeah, no dice.

Is there a way to exclude a specific package from an upgrade, or to change the install order?

hydrurga · 02-02-2017, 05:50 AM

Quote:

Originally Posted by Ibilata_Bingbingbing

Yeah, no dice.

Is there a way to exclude a specific package from an upgrade, or to change the install order?

Yup, you should be able to hold it. I'm not sure how that will affect a half-configured package though.

sudo apt-mark hold udev

Ibilata_Bingbingbing · 02-02-2017, 06:32 AM

Nope!

Looks like it's reformat time again.

Thanks for the help though!

hydrurga · 02-02-2017, 06:42 AM

Quote:

Originally Posted by Ibilata_Bingbingbing

Nope!

Looks like it's reformat time again.

Thanks for the help though!

Do you not take system backups/images? Worth a consideration. Saved me on various occasions.

Ibilata_Bingbingbing · 02-02-2017, 07:49 AM

I'm thinking you might be onto something there... I seem to have a knack for splatting my system.

Do you have a preferred utility?

hydrurga · 02-02-2017, 10:18 AM

Quote:

Originally Posted by Ibilata_Bingbingbing

I'm thinking you might be onto something there... I seem to have a knack for splatting my system.

Do you have a preferred utility?

Some would say that you can't get to know your system properly without splatting it. ;-)

I'm not the one to ask about backups/images as I have my own idiosyncratic method - I take online backups of /home with FreeFileSync and offline system snapshots of my /, /home and /home/data partitions with Macrium Reflect.

Have a search though, including on LQ, as there are many different packages and methods available.

A thought as I was out walking: have you checked the apt logs to see if you can spot what went awry with your system? if you can figure out at which point things started ravelling, perhaps they can be unravelled. In particular, look for failed installs and updates to system components (udev, systemd etc.).

/var/log/apt/history.log and term.log