Printing Issue (CUPS) - Jobs Not Printing
Overview
If a customer is configured to automatically print jobs such as Group Pages, etc., they may encounter an issue where the printing service stops, resulting in jobs not printing.
Goal
Using the steps below, the printing service will be restarted, allowing for jobs to resume printing. Jobs in the printing queue should then be printed successfully.
First Step
As an optional, but recommended, first step, check the print queue by connecting to the customer's server (typically the database server) and use the lpq command.
[amcom@dbhost01 ~]$ lpq
This will show the number of items in the print queue, helping to verify the issue (items stuck in the queue will verify there is a problem).
Second Step
Connect to the customer's Common UNIX Printing System (CUPS) web GUI (if using SecureLink, typically this will be an option under the database server entry). By default, CUPS is accessed on port 631, and should therefore be accessible via that port (ex. http://127.0.0.1:631) once connected to the customer. The user name and password, if asked, should be root/AM_Amcom_04.
Third Step
Once connected to the CUPS GUI, navigate to the Printers tab to view the status of the printer. The state should include "accepting jobs" and "published". If not, it's likely the printer has stopped, requiring a manual start via the Maintenance dropdown on the affected printer's page. Select Resume Printer to reconnect CUPS to the printer.
What's Next
After starting the printer, wait a minute then re-examine the queue, either in the CUPS GUI or using the lpq command on the server to verify that jobs are now printing normally.
Another Option
Alternative method to access Printer via Linux if CUPS isn't available.
--view queue
lpstat -l -t (to see status and queue)
--enable printer
lpadmin -p printername -E