I found that when a job is sent to a printer over IPP, and the printer reports back any kind of an issue (cover open, no toner, jam, etc). the job is held in the queue for the MaxJobTime.
However, after MaxJobTime not only the job gets cancelled, but the printer itself gets paused as well and never unpaused. It's surprising because server-wide policy is retry-job and printer's own policy is retry-job.
Here is the printer setup:
<Printer blip-color>
UUID urn:uuid:c2ed813e-507b-30b4-7bc6-698a9226378e
AuthInfoRequired none
Info blip-color
MakeModel Ricoh Aficio MP C3004 PS
DeviceURI ipp://blip-color:631/printer
State Idle
StateTime 1550157235
ConfigTime 1549568815
Type 8434172
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy retry-job
</Printer>
Attached is a debug log for a Job 72, that was sent on 20:55, got cancelled on 21:55 (because printer cover was open), and the printer itself had become paused. (error_log_Job_72.txt)
Also attached cupsd.conf, cups-files.conf, and whole error_log from 20:55 to 21:55.
Could this please be looked at? It seems to be an unexpected behaviour of IPP backend for such a setup.
Relevant feature request: please add a line to the log showing when the printer was paused and why. It exists for manual cupsenable/cupsdisable (Printer "blip-color" started by "admin"), but doesn't seem to exist for internal events like this one.
I found that when a job is sent to a printer over IPP, and the printer reports back any kind of an issue (cover open, no toner, jam, etc). the job is held in the queue for the MaxJobTime.
However, after MaxJobTime not only the job gets cancelled, but the printer itself gets paused as well and never unpaused. It's surprising because server-wide policy is retry-job and printer's own policy is retry-job.
Here is the printer setup:
Attached is a debug log for a Job 72, that was sent on 20:55, got cancelled on 21:55 (because printer cover was open), and the printer itself had become paused. (error_log_Job_72.txt)
Also attached cupsd.conf, cups-files.conf, and whole error_log from 20:55 to 21:55.
Could this please be looked at? It seems to be an unexpected behaviour of IPP backend for such a setup.
Relevant feature request: please add a line to the log showing when the printer was paused and why. It exists for manual cupsenable/cupsdisable (Printer "blip-color" started by "admin"), but doesn't seem to exist for internal events like this one.