# VERIFICATION: XENIAL
- Using the reproducer defined in the test case and the version in -updates:
ubuntu@xenial-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.1.3-4ubuntu0.7
amd64 Common UNIX Printing System(tm) - PPD/driver support, web
interface
ii cups-common 2.1.3-4ubuntu0.7
all Common UNIX Printing System(tm) - common files
ii cups-daemon 2.1.3-4ubuntu0.7
amd64 Common UNIX Printing System(tm) - daemon
ubuntu@xenial-sssd-ad:~$ grep -i systemgroup /etc/cups/cups-files.conf
SystemGroup lpadmins@TESTS.LOCAL
ubuntu@xenial-sssd-ad:~$ systemd-analyze critical-chain cups.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
cups.service @5d 44min 12.341s
└─basic.target @35.619s
└─sockets.target @35.617s
└─lxd.socket @35.592s +11ms
└─sysinit.target @35.463s
└─cloud-init.service @31.929s +3.152s
└─networking.service @15.375s +16.549s
└─network-pre.target @15.326s
└─cloud-init-local.service @6.646s +8.677s
└─systemd-remount-fs.service @5.484s +342ms
└─system.slice @5.461s
└─-.slice @5.389s
- After reboot, cups fails to start:
ubuntu@xenial-sssd-ad:~$ systemctl status cups
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset:
enabled)
Active: failed (Result: start-limit-hit) since Tue 2019-05-07 10:06:07 UTC;
1min 57s ago
Docs: man:cupsd(8)
Process: 1152 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
Main PID: 1152 (code=exited, status=1/FAILURE)
May 07 10:06:07 xenial-sssd-ad systemd[1]: cups.service: Failed with result
'exit-code'.
May 07 10:06:07 xenial-sssd-ad systemd[1]: Started CUPS Scheduler.
May 07 10:06:07 xenial-sssd-ad cupsd[1152]: Unknown SystemGroup
"lpadmins@TESTS.LOCAL" on line 19 of /etc/
May 07 10:06:07 xenial-sssd-ad cupsd[1152]: Unable to read
"/etc/cups/cups-files.conf" due to errors.
May 07 10:06:07 xenial-sssd-ad systemd[1]: cups.service: Main process exited,
code=exited, status=1/FAILUR
May 07 10:06:07 xenial-sssd-ad systemd[1]: cups.service: Unit entered failed
state.
May 07 10:06:07 xenial-sssd-ad systemd[1]: cups.service: Failed with result
'exit-code'.
May 07 10:06:07 xenial-sssd-ad systemd[1]: cups.service: Start request repeated
too quickly.
May 07 10:06:07 xenial-sssd-ad systemd[1]: Failed to start CUPS Scheduler.
May 07 10:06:07 xenial-sssd-ad systemd[1]: cups.service: Failed with result
'start-limit-hit'.
- Using the version in -proposed, after rebooting:
ubuntu@xenial-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.1.3-4ubuntu0.8
amd64 Common UNIX Printing System(tm) - PPD/driver support, web
interface
ii cups-common 2.1.3-4ubuntu0.8
all Common UNIX Printing System(tm) - common files
ii cups-daemon 2.1.3-4ubuntu0.8
amd64 Common UNIX Printing System(tm) - daemon
ubuntu@xenial-sssd-ad:~$ systemctl status cups
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset:
enabled)
Active: active (running) since Tue 2019-05-07 10:14:10 UTC; 2min 20s ago
Docs: man:cupsd(8)
Main PID: 1276 (cupsd)
Tasks: 1
Memory: 2.1M
CPU: 12ms
CGroup: /system.slice/cups.service
└─1276 /usr/sbin/cupsd -l
May 07 10:14:10 xenial-sssd-ad systemd[1]: Started CUPS Scheduler.
ubuntu@xenial-sssd-ad:~$ systemd-analyze critical-chain cups.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
cups.service @32.661s
└─sssd.service @29.252s +3.393s
└─basic.target @29.247s
└─sockets.target @29.245s
└─lxd.socket @29.225s +10ms
└─sysinit.target @29.117s
└─cloud-init.service @26.685s +2.416s
└─networking.service @11.315s +15.364s
└─network-pre.target @11.301s
└─cloud-init-local.service @3.841s +7.457s
└─systemd-remount-fs.service @3.084s +278ms
└─systemd-journald.socket @3.036s
└─-.slice @2.984s
- Using the version in -proposed, with sssd not installed in the machine
(and setting SystemGroup to the original local group "lpadmin"), cups
still starts:
buntu@xenial-sssd-ad:~$ systemctl status cups
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset:
enabled)
Active: active (running) since Tue 2019-05-07 10:18:50 UTC; 2min 48s ago
Docs: man:cupsd(8)
Main PID: 1072 (cupsd)
Tasks: 1
Memory: 2.0M
CPU: 10ms
CGroup: /system.slice/cups.service
└─1072 /usr/sbin/cupsd -l
May 07 10:18:50 xenial-sssd-ad systemd[1]: Started CUPS Scheduler.
ubuntu@xenial-sssd-ad:~$ systemd-analyze critical-chain cups.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
cups.service @20.058s
└─basic.target @19.746s
└─sockets.target @19.745s
└─lxd.socket @19.679s +57ms
└─sysinit.target @19.650s
└─cloud-init.service @18.406s +1.241s
└─networking.service @7.076s +11.326s
└─network-pre.target @7.068s
└─cloud-init-local.service @2.237s +4.829s
└─systemd-remount-fs.service @1.366s +117ms
└─system.slice @1.307s
└─-.slice @1.250s
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822062
Title:
Race condition on boot between cups and sssd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
