On networked printers, you should check that the hostname in the printer's URI resolves to the printer's IP address via DNS, e.g. Copy down the information displayed, click 'Modify Printer' to proceed to the next page(s), and so on.Īll jobs are 'The printer is not responding' To check the printer's settings go to Printers, then Modify Printer. Using the CUPS web interface, go to Printers > Delete Printer. If it does not yield any useful hints to what is the source of the issue, delete the printer and add it again. If all jobs sent to the printer become 'stopped', first check the error log at /var/log/cups/error_log. Reason: This seems a rather brute-force way of fixing this maybe the printer is simply disabled? (Discuss in Talk:CUPS/Troubleshooting) To use the new configuration, copy /etc/cups/ to /etc/cups/nf (backup the old configuration if needed) and restart CUPS to employ the new settings. Messages such as '404 - page not found' may result from trying to manage CUPS via localhost:631, for example. The chances are that a new configuration file is needed for the new version to work properly. Issues that appeared after CUPS and related program packages underwent a version increment CUPS stops working

Print a document and watch error_log to get a more detailed and correct image of the printing process.

/var/log/cups/access_log - Lists all cupsd http1.1 server activity.

/var/log/cups/page_log - Echoes a new entry each time a print is successful.

The characters at the left of the output stand for:

The best way to get printing working is to set LogLevel in /etc/cups/nf to:Īnd then viewing the output from /var/log/cups/error_log like this: This article covers all non-specific (ie, not related to any one printer) troubleshooting of CUPS and printing drivers (but not problems related to printer sharing), including methods of determining the exact nature of the problem, and of solving the identified problem.

Laser printer test page pdf