I have some HP inkjets. Sometimes they'll run low on ink, and cups will disable the printer. After replacing the cartridges, you need root access to re-enable the printers in system-config-printers. How can I avoid the need for root access? Is there a "printer enable thyself" option? The error.log is below. A jam is reported at [12/Nov/2009:16:23:40 -0500] (yesterday). A pause is reported at [12/Nov/2009:16:23:40 -0500]. I re-enable the printer (as root) at [13/Nov/2009:10:14:14 -0500], the next day. The printer UI was reporting that the cartridges were low. I replaced them 1/2 hr before restarting the printer manual. I'm not sure if that was the true error, because the log also mentions paper jams. - Mike D [12/Nov/2009:16:23:40 -0500] [Job 316] PAGE: 12 1 D [12/Nov/2009:16:23:40 -0500] [Job 316] Copying page 14... D [12/Nov/2009:16:23:40 -0500] [Job 316] pagew = 540.0, pagel = 720.0 D [12/Nov/2009:16:23:40 -0500] [Job 316] bboxx = 0, bboxy = 0, bboxw = 612, bboxl = 792 D [12/Nov/2009:16:23:40 -0500] [Job 316] PageLeft = 36.0, PageRight = 576.0 D [12/Nov/2009:16:23:40 -0500] [Job 316] PageTop = 756.0, PageBottom = 36.0 D [12/Nov/2009:16:23:40 -0500] [Job 316] PageWidth = 612.0, PageLength = 792.0 D [12/Nov/2009:16:23:40 -0500] [Job 316] PAGE: 13 1 D [12/Nov/2009:16:23:40 -0500] [Job 316] STATE: +media-jam-error D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... D [12/Nov/2009:16:23:40 -0500] [Job 316] STATE: -media-jam-error D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 618: ERROR: 5012 device communication error! D [12/Nov/2009:16:23:40 -0500] [Job 316] Wrote 14 pages... D [12/Nov/2009:16:23:40 -0500] [Job 316] D [12/Nov/2009:16:23:40 -0500] [Job 316] Closing renderer D [12/Nov/2009:16:23:40 -0500] [Job 316] PAGE: 14 1 D [12/Nov/2009:16:23:40 -0500] [Job 316] renderer exited with status 0 D [12/Nov/2009:16:23:40 -0500] [Job 316] kid4 exited with status 0 D [12/Nov/2009:16:23:40 -0500] [Job 316] kid3 finished D [12/Nov/2009:16:23:40 -0500] [Job 316] kid3 exited with status 0 D [12/Nov/2009:16:23:40 -0500] [Job 316] D [12/Nov/2009:16:23:40 -0500] [Job 316] Closing foomatic-rip. D [12/Nov/2009:16:23:40 -0500] [Job 316] Backend returned status 1 (failed) D [12/Nov/2009:16:23:40 -0500] [Job 316] Printer stopped due to backend errors; please consult the error_log file for details. D [12/Nov/2009:16:23:40 -0500] [Job 316] End of messages D [12/Nov/2009:16:23:40 -0500] [Job 316] printer-state=5(stopped) D [12/Nov/2009:16:23:40 -0500] [Job 316] printer-state-message="/usr/lib/cups/backend/hp failed" D [12/Nov/2009:16:23:40 -0500] [Job 316] printer-state-reasons=marker-supply-low-warning,paused I [12/Nov/2009:16:24:09 -0500] Saving printers.conf... I [12/Nov/2009:16:24:09 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [12/Nov/2009:16:24:09 -0500] Saving subscriptions.conf... I [12/Nov/2009:16:26:11 -0500] Scheduler shutting down normally. I [12/Nov/2009:16:26:11 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:07:30:31 -0500] Listening to ::1:631 (IPv6) I [13/Nov/2009:07:30:31 -0500] Listening to 127.0.0.1:631 (IPv4) I [13/Nov/2009:07:30:31 -0500] Listening to /var/run/cups/cups.sock (Domain) W [13/Nov/2009:07:30:31 -0500] No limit for CUPS-Get-Document defined in policy default - using Send-Document's policy I [13/Nov/2009:07:30:31 -0500] Remote access is disabled. I [13/Nov/2009:07:30:31 -0500] Loaded configuration file "/etc/cups/cupsd.conf" I [13/Nov/2009:07:30:31 -0500] Using default TempDir of /var/spool/cups/tmp... I [13/Nov/2009:07:30:31 -0500] Configured for up to 100 clients. I [13/Nov/2009:07:30:31 -0500] Allowing up to 100 client connections per host. I [13/Nov/2009:07:30:31 -0500] Using policy "default" as the default! I [13/Nov/2009:07:30:31 -0500] Full reload is required. I [13/Nov/2009:07:30:31 -0500] Loaded MIME database from "/usr/share/cups/mime" and "/etc/cups": 36 types, 41 filters... I [13/Nov/2009:07:30:31 -0500] Loading job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:07:30:31 -0500] Full reload complete. I [13/Nov/2009:07:30:31 -0500] Cleaning out old temporary files in "/var/spool/cups/tmp"... I [13/Nov/2009:07:30:31 -0500] Listening to ::1:631 on fd 7... I [13/Nov/2009:07:30:31 -0500] Listening to 127.0.0.1:631 on fd 8... I [13/Nov/2009:07:30:31 -0500] Listening to /var/run/cups/cups.sock on fd 9... I [13/Nov/2009:07:30:31 -0500] Resuming new connection processing... I [13/Nov/2009:07:31:34 -0500] Saving subscriptions.conf... I [13/Nov/2009:08:24:35 -0500] Subscription 164 has expired... I [13/Nov/2009:08:25:06 -0500] Saving subscriptions.conf... I [13/Nov/2009:09:14:00 -0500] [Job ???] Request file type is application/postscript. I [13/Nov/2009:09:14:31 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:09:14:31 -0500] Saving subscriptions.conf... I [13/Nov/2009:09:14:39 -0500] [Job ???] Request file type is application/postscript. I [13/Nov/2009:09:15:10 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:09:15:10 -0500] Saving subscriptions.conf... I [13/Nov/2009:09:21:57 -0500] [Job ???] Request file type is application/postscript. I [13/Nov/2009:09:22:28 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:09:22:28 -0500] Saving subscriptions.conf... I [13/Nov/2009:09:23:43 -0500] Saving subscriptions.conf... I [13/Nov/2009:09:23:43 -0500] [Job 319] Canceled by "walter". I [13/Nov/2009:09:23:47 -0500] [Job 318] Canceled by "walter". I [13/Nov/2009:09:23:51 -0500] [Job 317] Canceled by "walter". I [13/Nov/2009:09:23:56 -0500] [Job 316] Canceled by "walter". I [13/Nov/2009:09:24:14 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:09:24:14 -0500] Saving subscriptions.conf... I [13/Nov/2009:09:29:10 -0500] [Job ???] Request file type is application/postscript. I [13/Nov/2009:09:29:41 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:09:29:41 -0500] Saving subscriptions.conf... I [13/Nov/2009:09:30:40 -0500] [Job 320] Canceled by "walter". I [13/Nov/2009:09:30:54 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:09:30:54 -0500] Saving subscriptions.conf... I [13/Nov/2009:09:37:06 -0500] [Job ???] Request file type is application/postscript. I [13/Nov/2009:09:37:18 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:09:37:18 -0500] Saving subscriptions.conf... I [13/Nov/2009:09:37:46 -0500] [Job ???] Request file type is application/postscript. I [13/Nov/2009:09:38:17 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:09:38:17 -0500] Saving subscriptions.conf... I [13/Nov/2009:10:13:47 -0500] [Job ???] Request file type is application/postscript. I [13/Nov/2009:10:13:53 -0500] [Job 323] Canceled by "walter". I [13/Nov/2009:10:13:56 -0500] [Job 321] Canceled by "walter". I [13/Nov/2009:10:13:59 -0500] [Job 322] Canceled by "walter". I [13/Nov/2009:10:14:14 -0500] Printer "HP6940" started by "root". I [13/Nov/2009:10:14:18 -0500] Saving printers.conf... I [13/Nov/2009:10:14:18 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:10:14:18 -0500] Saving subscriptions.conf... I [13/Nov/2009:10:14:26 -0500] [Job ???] Request file type is application/postscript. I [13/Nov/2009:10:14:49 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:10:14:49 -0500] Saving subscriptions.conf... I [13/Nov/2009:10:15:26 -0500] Saving job cache file "/var/cache/cups/job.cache"... I [13/Nov/2009:10:15:26 -0500] Saving subscriptions.conf...
This is the reason the printer was disabled: D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 618: ERROR: 5012 device communication error! HPLIP might have logged more information in /var/log/messages. Can you please take a look to see if you can find any HPLIP-related messages in /var/log/messages* from that moment?
Nov 12 16:17:05 thorn hp[5872]: io/hpmud/jd.c 531: timeout write_channel hp:/net/Deskjet_6940_series?ip=192.168.0.161 Nov 12 16:17:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:17:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:18:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:18:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:19:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:19:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:20:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:20:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:21:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:21:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:22:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:22:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:23:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:23:38 thorn hp[5872]: io/hpmud/jd.c 88: unable to read device-id Nov 12 16:23:38 thorn hp[5872]: prnt/backend/hp.c 618: ERROR: 5012 device communication error! The computer was turned off shortly after that, and turned on next morning. No further hp[....] messages occur after the above ones. - Mike
Perhaps the printer was turned off at 16:23? That would explain "unable to read device-id" which seems to be the cause of the communication error which led to the print queue becoming disabled.
I spoke to the user: 1) A print job was being printed, and they noticed the paper tray was almost empty. 2) They somehow inserted more paper, but this made the printer unhappy ("printer jam"). 3) They turned it off and went home. Which is all fine and good - but it would be nice if the printer auto-re-enabled the next morning, after printer and cpu power up. I've run into this in other now-forgotten situations. I (the admin) have to re-enable a printer as root, and the printer is then fine. - Mike
So, in this situation, there is no way for CUPS or HPLIP to know whether this is a temporary or permanent error. The job gets marked as having failed, so the printer-error-policy is followed. It sounds like you want to change the printer-error-policy to retry-job.
It would make more sense to set the default error policy to retry-job. That way, the user does not require root to re-start the printer once the paper jam (or whatever) has been fixed. Ubuntu has done so: https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/41313 - Mike