After updating to latest kernel available I see these messages in the journalctl journalctl -b0 --priority 4 Apr 05 11:17:43 systemd[1]: Failed to start CUPS Scheduler. Apr 05 11:17:43 systemd[1]: cups.service: Failed with result 'exit-code'. Apr 05 11:17:43 systemd[1]: Failed to start CUPS Scheduler. Apr 05 11:17:43 systemd[1]: cups.service: Failed with result 'exit-code'. Apr 05 11:17:43 systemd[1]: Failed to start CUPS Scheduler. Apr 05 11:17:43 systemd[1]: cups.service: Failed with result 'exit-code'. Apr 05 11:17:43 systemd[1]: Failed to start CUPS Scheduler. Apr 05 11:17:43 systemd[1]: cups.service: Failed with result 'exit-code'. Apr 05 11:17:43 systemd[1]: Failed to start CUPS Scheduler. Apr 05 11:17:43 systemd[1]: cups.service: Failed with result 'exit-code'. Apr 05 11:17:43 systemd[1]: cups.service: Start request repeated too quickly. Apr 05 11:17:43 systemd[1]: Failed to start CUPS Scheduler. Apr 05 11:17:43 smbd[1052]: [2017/04/05 11:17:43.751999, 0] ../source3/printing/print_cups.c:366(cups_cache_reload_async) Apr 05 11:17:43 systemd[1]: cups.service: Failed with result 'start-limit-hit'. Apr 05 11:17:43 smbd[1052]: Unable to get printer list - server-error-internal-error systemctl status cups ● cups.service - CUPS Scheduler Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit-hit) since Wed 2017-04-05 11:17:43 CEST; 2min 5s ago Docs: man:cupsd(8) Process: 1076 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE) Main PID: 1076 (code=exited, status=1/FAILURE) Apr 05 11:17:43 systemd[1]: Starting CUPS Scheduler... Apr 05 11:17:43 cupsd[1076]: cupsd: Cannot get a status of /etc/resolv.conf Apr 05 11:17:43 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE Apr 05 11:17:43 systemd[1]: Failed to start CUPS Scheduler. Apr 05 11:17:43 systemd[1]: cups.service: Unit entered failed state. Apr 05 11:17:43 systemd[1]: cups.service: Failed with result 'exit-code'. Apr 05 11:17:43 systemd[1]: cups.service: Start request repeated too quickly. Apr 05 11:17:43 systemd[1]: Failed to start CUPS Scheduler. Apr 05 11:17:43 systemd[1]: cups.service: Failed with result 'start-limit-hit'.
Hi Ed, your issue is duplicate of issue #1437065 https://bugzilla.redhat.com/show_bug.cgi?id=1437065 . It was temporarily solved with cups-2.2.0-7 release. If you want to solve it immediately, install rpms from koji https://koji.fedoraproject.org/koji/taskinfo?taskID=18780789 or wait until update from bodhi gets into stable release. *** This bug has been marked as a duplicate of bug 1437065 ***