Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: manilg on 2020/11/30, 10:18:46
-
Nach dem update auf Version cups (2.3.3op1-2) funktioniert das Drucken nicht mehr.
localhost:631 ist nicht erreichbar und
systemctl restart cups
Job for cups.service failed because a fatal signal was delivered to the control process.
See "systemctl status cups.service" and "journalctl -xe" for details.
root@xxxx:systemctl status cups.service
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: signal) since Mon 2020-11-30 10:11:01 CET; 19s ago
TriggeredBy: ● cups.socket
● cups.path
Docs: man:cupsd(8)
Process: 1238993 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=SEGV)
Main PID: 1238993 (code=killed, signal=SEGV)
Nov 30 10:11:01 xxx systemd[1]: cups.service: Scheduled restart job, restart counter is at 12.
Nov 30 10:11:01 xxx systemd[1]: Stopped CUPS Scheduler.
Nov 30 10:11:01 xxx systemd[1]: Dependency failed for CUPS Scheduler.
Nov 30 10:11:01 xxx systemd[1]: cups.service: Job cups.service/start failed with result 'dependency'.
Gruß
manilg
-
Kann ich nicht nachvollziehen. http://localhost:631 geht hier ebenso wie systemctl restart cups.
apt policy cups
cups:
Installiert: 2.3.3op1-2
Installationskandidat: 2.3.3op1-2
Versionstabelle:
*** 2.3.3op1-2 500
500 http://ftp.de.debian.org/debian unstable/main amd64 Packages
500 http://incoming.debian.org/debian-buildd buildd-unstable/main amd64 Packages
100 /var/lib/dpkg/status
2.3.3-4 500
500 http://ftp.de.debian.org/debian testing/main amd64 Packages
-
Den vermeintlichen cups-Fehler kann ich auch nicht bestätigen, hier ist alles in Ordnung nach dem cups-Update.
Da klemmt irgend etwas anderes in Deiner Installation
-
Ich kann den Fehler hingegen bestätigen.
Weder cups.service .path oder . socket scheinen zu laufen.
$ systemctl status cups.service cups.socket cups.path
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: signal) since Mon 2020-11-30 12:36:11 CET; 3min 32s ago
TriggeredBy: ● cups.socket
● cups.path
Docs: man:cupsd(8)
Process: 131693 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=SEGV)
Main PID: 131693 (code=killed, signal=SEGV)
Nov 30 12:36:11 host systemd[1]: cups.service: Scheduled restart job, restart counter is at 31.
Nov 30 12:36:11 host systemd[1]: Stopped CUPS Scheduler.
Nov 30 12:36:11 host systemd[1]: Dependency failed for CUPS Scheduler.
Nov 30 12:36:11 host systemd[1]: cups.service: Job cups.service/start failed with result 'dependency'.
● cups.socket - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.socket; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Mon 2020-11-30 12:36:11 CET; 3min 32s ago
Triggers: ● cups.service
Listen: /run/cups/cups.sock (Stream)
Nov 30 12:36:11 host systemd[1]: Stopping CUPS Scheduler.
Nov 30 12:36:11 host systemd[1]: Listening on CUPS Scheduler.
Nov 30 12:36:11 host systemd[1]: cups.socket: Succeeded.
Nov 30 12:36:11 host systemd[1]: Closed CUPS Scheduler.
Nov 30 12:36:11 host systemd[1]: Stopping CUPS Scheduler.
Nov 30 12:36:11 host systemd[1]: cups.socket: Start request repeated too quickly.
Nov 30 12:36:11 host systemd[1]: cups.socket: Failed with result 'start-limit-hit'.
Nov 30 12:36:11 host systemd[1]: Failed to listen on CUPS Scheduler.
● cups.path - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.path; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Mon 2020-11-30 12:25:15 CET; 14min ago
Triggers: ● cups.service
Nov 30 12:25:14 host systemd[1]: Started CUPS Scheduler.
Nov 30 12:25:15 host systemd[1]: cups.path: Succeeded.
Nov 30 12:25:15 host systemd[1]: Stopped CUPS Scheduler.
Nov 30 12:25:15 host systemd[1]: Stopping CUPS Scheduler.
Nov 30 12:25:15 host systemd[1]: cups.path: Start request repeated too quickly.
Nov 30 12:25:15 host systemd[1]: cups.path: Failed with result 'start-limit-hit'.
Nov 30 12:25:15 host systemd[1]: Failed to start CUPS Scheduler.
Und auch bei mir führt ein Neustart von CUPS zu
# systemctl restart cups.service
Job for cups.service failed because a fatal signal was delivered to the control process.
See "systemctl status cups.service" and "journalctl -xe" for details.
Ein blick in journalctl liefert dann https://paste.debian.net/plain/1174927 (https://paste.debian.net/plain/1174927) wo von einem segfault die Rede ist.
Ich habe bereits cups reinstalliert, leider hat das auch nicht geholfen.
Mister00X
-
Ich habe das Problem bei mir inzwischen behoben.
Der springende Punkt ist ein simples
apt install --reinstall cups
reicht nicht aus.
Was jedoch funktioniert ist ein
apt purge cups*
gefolgt von einem autoremove und einem reboot. Dann wieder
apt install cups und es läuft.
Ich habe im Rahmen meines Problemlösungsvorgangs auch ein paar Brother-Treiber deinstalliert, bin mir allerdings nicht sicher ob das was damit zu tun hat.
Mister00X
-
All correct here:
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2020-11-30 13:49:05 EST; 5min ago
TriggeredBy: ● cups.path
● cups.socket
Docs: man:cupsd(8)
Main PID: 653 (cupsd)
Status: "Scheduler is running..."
Tasks: 2 (limit: 4578)
Memory: 6.4M
CGroup: /system.slice/cups.service
├─ 653 /usr/sbin/cupsd -l
└─2114 /usr/lib/cups/notifier/dbus dbus://
Nov 30 13:49:04 dibl-HP350 systemd[1]: Starting CUPS Scheduler...
Nov 30 13:49:05 dibl-HP350 systemd[1]: Started CUPS Scheduler.
$ sudo apt policy cups
cups:
Installed: 2.3.3op1-2
Candidate: 2.3.3op1-2
Version table:
*** 2.3.3op1-2 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status