On Thu 20 Apr 2017 at 21:04:28 +1000, Ben Finney wrote: > On 20-Apr-2017, Brian Potkin wrote: > > > 1. Do 'cupsctl debuglevel=warn' and 'systemctl status cups'. cups crashes > > for me on the first command. > > ===== > $ sudo systemctl restart cups > > $ sudo systemctl status cups > ● cups.service - CUPS Scheduler > Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > enabled) > Active: active (running) since Thu 2017-04-20 21:00:04 AEST; 1s ago > Docs: man:cupsd(8) > Main PID: 8587 (cupsd) > Tasks: 4 (limit: 4915) > Memory: 6.4M > CPU: 311ms > CGroup: /system.slice/cups.service > ├─8587 /usr/sbin/cupsd -l > ├─8594 SCX-4623-Series 68 bignose Test page 1 > job-uuid=urn:uuid:8b94617c-da70-3de2-40ae-62d8e2feba78 > job-originating-host-name=localhost date-time-at-creation= > date-time-at-processing= time-at-creation=1492684769 time-at-proces > └─8595 > usb://Samsung/SCX-4623%20Series?serial=Z2WUBFFZ300396N&interface=1 68 bignose > Test page 1 job-uuid=urn:uuid:8b94617c-da70-3de2-40ae-62d8e2feba78 > job-originating-host-name=localhost date-time-at-creation= date-time-at-pro > > Apr 20 21:00:04 lantana systemd[1]: Started CUPS Scheduler. > > $ sudo cupsctl debuglevel=warn > > $ sudo systemctl status cups > ● cups.service - CUPS Scheduler > Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > enabled) > Active: failed (Result: exit-code) since Thu 2017-04-20 21:00:13 AEST; 1s > ago > Docs: man:cupsd(8) > Process: 8587 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE) > Main PID: 8587 (code=exited, status=1/FAILURE) > CPU: 324ms > > Apr 20 21:00:04 lantana systemd[1]: Started CUPS Scheduler. > Apr 20 21:00:13 lantana systemd[1]: cups.service: Main process exited, > code=exited, status=1/FAILURE > Apr 20 21:00:13 lantana systemd[1]: cups.service: Unit entered failed state. > Apr 20 21:00:13 lantana systemd[1]: cups.service: Failed with result > 'exit-code'.
We get the same outcome. This looks like a different issue from yours. -- Brian.
