How to keep RHEL printers from being permanently disabled due to printing errors

Solution Verified - Updated -


  • Print jobs are stopped if network printer is not reachable
  • Some print jobs are not printing as expected
  • Printer host is unreachable causing issues
  • Printing jobs in the printing queue disabled randomly.
  • How to reprint jobs that fail due to lost connection?
  • Printer disabled with the following messages:

    W [07/Jan/2012:17:19:04 +0900] [Job 2564] Remote host did not respond with command status byte after 300 seconds!
    D [07/Jan/2012:17:19:04 +0900] [Job 2564] lpd_command returning 98
    E [07/Jan/2012:17:19:04 +0900] PID 16592 stopped with status 1!
  • A network printer is configured on the server. Some times the printer switches from "Enable" to "Disable". The printer must be re-enabled manually to be able to use it.

  • Sometimes we are having issues with printing and users will complain that invoices or delivery notes are not printing. When I run "lpq -P Q7PRINTER" the output shows:

    lpq -P Q7PRINTER
    Q7PRINTER not ready 
  • Is there a configuration item that makes CUPS retry if the client connection times-out to a CUPS server?

  • We are using the CUPS utility to print jobs in RHEL servers. For some reason the printers are going to paused state.
  • One of the printers gets disabled frequently with the following status:

    # lpstat -p IT1
    printer IT1 disabled since Fri 15 Nov 2013 03:50:04 PM EST -
            /usr/lib/cups/backend/lpd failed


  • Red Hat Enterprise Linux (RHEL) 7 with Common Unix Printing System (CUPS) 1.6.3
  • RHEL 6 / CUPS 1.4.2
  • RHEL 5 / CUPS 1.3.5
  • RHEL 4 / CUPS 1.1.22

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In