Package: cups
Version: 2.3.3op1-3
Severity: normal
Tags: patch
User: debian-edu@lists.debian.org
Usertags: debian-edu
Dear Maintainer,
while working on Debian Edu 11 Bullseye, I noticed the cups service
failing randomly after rebooting the system:
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2020-12-12 10:25:50 CET; 3min 46s ago
TriggeredBy: ● cups.path
● cups.socket
Docs: man:cupsd(8)
Process: 1201 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
Main PID: 1201 (code=exited, status=1/FAILURE)
Dez 12 10:25:50 tjener.intern systemd[1]: Failed to start CUPS Scheduler.
Dez 12 10:25:50 tjener.intern systemd[1]: cups.service: Scheduled restart job, restart counter is at 5.
Dez 12 10:25:50 tjener.intern systemd[1]: Stopped CUPS Scheduler.
Dez 12 10:25:50 tjener.intern systemd[1]: cups.service: Start request repeated too quickly.
Dez 12 10:25:50 tjener.intern systemd[1]: cups.service: Failed with result 'exit-code'.
Dez 12 10:25:50 tjener.intern systemd[1]: Failed to start CUPS Scheduler.
Debian Edu uses an LDAP group printer-admins in cups-files.conf like so:
SystemGroup lpadmin printer-admins
Please note that Debian Edu uses nslcd.
After adding the nslcd.service (in addition to sssd.service and
ypbind.service) to the cups.service unit file, things work like
expected, this is the proposed change:
diff --git a/scheduler/cups.service.in b/scheduler/cups.service.in
index 9e70b2973..a3fa0e83f 100644
--- a/scheduler/cups.service.in
+++ b/scheduler/cups.service.in
@@ -1,7 +1,7 @@
[Unit]
Description=CUPS Scheduler
Documentation=man:cupsd(8)
-After=network.target sssd.service ypbind.service
+After=network.target sssd.service ypbind.service nslcd.service
Requires=cups.socket
[Service]
Please check if the change could be accepted.
Wolfgang
Attachment:
signature.asc
Description: PGP signature