Mit apt-get kann aufgrund von insserv nichts installiert werden


18

Immer wenn ich versuche, etwas mit zu installieren, apt-geterhalte ich die Fehlermeldung insserv. Ich habe versucht, viele verschiedene Pakete zu installieren, aber alle geben den gleichen Fehler aus. Und anscheinend hat das CUPS-Paket etwas getan, weil jede Fehlermeldung dies mit sich bringt. Folgendes sind die Fehler, die beim Ausführen angezeigt wurden sudo apt-get install wine1.8 winetricks:

After this operation, 716 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up util-linux (2.27.1-6ubuntu3.1) ...
insserv: warning: script 'K01cups-browsed' missing LSB tags and overrides
insserv: warning: script 'cups-browsed' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv:  loop involving service speech-dispatcher at depth 1
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service cups-browsed and hwclock if started
insserv:  loop involving service hwclock at depth 1
insserv: There is a loop at service cups-browsed if started
insserv:  loop involving service networking at depth 4
insserv: There is a loop between service plymouth and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service mountdevsubfs at depth 2
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service cups-browsed and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package util-linux (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 util-linux
E: Sub-process /usr/bin/dpkg returned an error code (1)

Die Inhalte von /etc/insserv.conf lauten wie folgt:

#
# All local filesystems are mounted (done during boot phase)
#
$local_fs   +umountfs

#
# Low level networking (ethernet card)
#
$network    +networking

#
# Named is operational
#
$named      +named +dnsmasq +lwresd +bind9 +unbound $network

#
# All remote filesystems are mounted (note in some cases /usr may
# be remote. Most applications that care will probably require
# both $local_fs and $remote_fs)
#
$remote_fs  $local_fs +umountnfs +sendsigs

#
# System logger is operational
#
$syslog     +rsyslog +sysklogd +syslog-ng +dsyslog +inetutils-syslogd

#
# The system time has been set correctly
#
$time       +hwclock

#
# Services which need to be interactive
#
<interactive>   glibc udev console-screen keymap keyboard-setup console-setup cryptdisks cryptdisks-early checkfs-loop

Ausgabe für $ apt-cache policy cups-browsed plymouth dns-clean

cups-browsed:
  Installed: 1.8.3-2ubuntu3
  Candidate: 1.8.3-2ubuntu3
  Version table:
 *** 1.8.3-2ubuntu3 500
        500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status
plymouth:
  Installed: 0.9.2-3ubuntu13
  Candidate: 0.9.2-3ubuntu13.1
  Version table:
     0.9.2-3ubuntu13.1 500
        500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 0.9.2-3ubuntu13 500
        500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status
N: Unable to locate package dns-clean

Ich kenne keine anderen relevanten Informationen, die für die Lösung dieses Problems wichtig sein könnten. Deshalb habe ich sie nicht veröffentlicht. Wenn Sie weitere Informationen wünschen, wenden Sie sich bitte an.


Stellen Sie sicher, dass Sie in der Konfiguration von insserv keine Fehler haben, insbesondere /etc/insserv.conf und /etc/insserv.conf.d/*. Wenn Sie sich nicht sicher sind, fügen Sie der Frage den Inhalt dieser Dateien hinzu.
einen Lebenslauf vom

@ MichaelKjörling Ich habe den Inhalt von/etc/insserv.conf
Pranjal

Welche Version von Ubuntu? Haben Sie Software hinzugefügt, die kein Paket aus den "Standard" -Repositorys ist? Was ist mit der letzten Bearbeitung von Systemdateien?
Roaima

1
Sie müssen sich die Dateien in ansehen /etc/insserv.conf.d. Stellen Sie den Inhalt einer Datei , deren Name enthält dns, plymouthoder cups. Oder vielleicht andere Dateien, ist das Problem nicht mit einer einzigen Datei , sondern mit ihnen in Verbindung, schaffen sie eine Schleife , in der A muss gestartet werden , bevor B gestartet werden muss , bevor C sein muss ... muss gestartet werden , bevor A.
Gilles ‚SO- hör auf böse zu sein '

1
@ Gilles Es gibt keine Dateien in/etc/insserv.conf.d
Pranjal

Antworten:


21

Zunächst einmal besteht das Problem darin, dass Sie bei der Startsequenzierung nicht weiterkommen.


Die Startreihenfolge wird bei der Installation oder bei Upgrades festgelegt. Wenn die durch die LSB-Header aller installierten init.dSkripten deklarierten Abhängigkeiten keine Schleifen aufweisen und keine veralteten Skripten vorhanden sind , wird das System in eine abhängigkeitsbasierte Startsequenz konvertiert.


Wir müssen nachsehen

  1. Schleife in Abhängigkeiten : Tritt auf, wenn>

    • In einigen Skripten fehlen LSB-Tags oder in LSB-Tags fehlen Fehler wie "missing" Required-Start:oder " Required-Stop:tags"
    • Einige Skripte hängen von anderen Skripten ab, die von der Systemeinrichtung abhängen und $allnicht wahr sein können. Denn die Skripte werden abhängig von $allzuletzt beim Start geladen. Da es zuletzt geladen wird, kann nichts davon abhängen. Dadurch wird die abhängigkeitsbasierte Startsequenz durcheinander gebracht.
  2. Veraltete Skripte : Treten auf, wenn

    • Einige Pakete, die auf neuere Versionen aktualisiert werden, in denen möglicherweise kein Skript verwendet wird /etc/init.d/und in denen der Betreuer möglicherweise den Code zum Entfernen des alten Skripts verpasst hat. Nicht unser Fehler.

Die Ursache ist sicherlich fremd. Springen /etc/init.dund die Datei anzuzeigen entsprechend cups-browsedund bestätigt , dass sie haben einen LSB Kommentar mit Provides, Required-Start/ Required-Stop(zumindest leer), Default-Start/ Default-Stopin ihm unten mögen.

### BEGIN INIT INFO
# Provides :          cups-browsed
# Required-Start :
# Required-Stop :
# Default-Start :     2 3 4 5
# Default-Stop  :     0 1 6
# Short-Description : Some info
# Description :       Some more info
### END INIT INFO

Ist dies nicht der Fall, können Sie den LSB-Kommentar hinzufügen oder das Programm und die Skripte vollständig aus /etc/init.d/und /etc/rc?Dateien löschen. Hoffe das würde funktionieren.

Fühlen Sie sich frei zu fragen, ob Sie irgendwelche Zweifel haben.


Es ist mehr als einen Monat her, seit ich die Frage gestellt habe. Da ich zu diesem Zeitpunkt keine Antwort bekam, habe ich das Programm gelöscht und alles hat funktioniert. Jetzt habe ich wieder installiert cupsund auf mysteriöse Weise funktioniert alles einwandfrei. Ich akzeptiere immer noch Ihre als richtige Antwort, weil Sie den Vorschlag für ein Bereinigungsprogramm darin erwähnt haben.
Pranjal

1
Ich habe das gleiche Problem. Ich habe die /etc/init.d/cups-browsedDatei überprüft und sie enthält bereits die von Ihnen erwähnten Kommentare. Wie lösche ich das Programm und die Skripte?
Mohan

Ok, ich verstehe, aber was ich nicht verstehe, ist warum? Diese INIT-INFO-Header gab es seit mehr als einem Jahrzehnt, aber niemand kümmerte sich um sie. Aus menschlicher Sicht ist das Festlegen der Startreihenfolge mit zwei Ziffern von 0 bis 99 ein sehr klarer Weg, aber muss ich jetzt Required-Start-Header nachverfolgen? Warum? Manchmal ist weniger mehr.
Soger

1
Ubuntu mag die Leerzeichen vor den Doppelpunkten nicht.
Tak3shi
Durch die Nutzung unserer Website bestätigen Sie, dass Sie unsere Cookie-Richtlinie und Datenschutzrichtlinie gelesen und verstanden haben.
Licensed under cc by-sa 3.0 with attribution required.