Zen

Source string Source string

$ lp -d <print_queue_name> <file1> ... <fileN> request id is <print_queue_name>-<JID> (N file(s))
98/10000 · 98

The string is read-only.

English Actions
tail -f /var/log/cups/error_log
Enable CUPS debug logging
Enable full debugging information with:
$ cupsctl LogLevel=debug2
CUPS job log
If the problem appears when you sent document to print or if you are trying to, capture logs for this job. If the job log is available, its attaching is *REQUIRED*.
Prepare CUPS for job logging
For being able to see specific job log, please turn on:
PreserveJobFiles Yes
in your [filename]`/etc/cups/cupsd.conf` file and restart cup service. Do not forget to remove the line after you are done with debugging. [command]`lpstat -W all` seems to be empty after printing if you do not enable the directive.
Get a job log for a specific job ID
To capture job log you need to know Job ID (JID) of the job - it is the number after dash in a request ID:
Request ID looks like this:
<print_queue_name>-<JID>
and can be seen in terminal if you send a document to print by [command]`lp` command:
$ lp -d <print_queue_name> <file1> ... <fileN>
request id is <print_queue_name>-<JID> (N file(s))
Or when you list jobs (see [command]`man lpstat`) - the latest job is at the end:
$ lpstat -W all
...
<print_queue_name>-<JID> <user> 1024 Wed 11 Jan 2017 05:52:19 PM CET
You can get the latest job logs automatically (if you have [command]`awk` installed and [command]`lpstat -W` all returns jobs) by:
$ journalctl -u cups JID=`lpstat -W all | awk '{print $1}' | awk -F '-' '{print $NF}' | tail -n 1` > cups_job_log
Or manually, if you found JID by yourself:
journalctl -u cups JID=<JID> > cups_job_log
Incident-bound cupsd log (broken print queue isn't HPLIP supported)
Sometimes we cannot bind the error with a specific print job, so the job log is uneffective. Incident-bound cupsd log is needed.
How to start to capture incident-bound cupsd logging
In new terminal/terminal tab, please issue:
journalctl -f -u cups > cups_whole_log
How to get incident-bound cupsd logging
After you trigger the error condition you are trying to diagnose e.g. printing something, try to find a printer via [command]`lpinfo` etc., you terminate capturing incident-bound cupsd log from xref:_how_to_start_to_capture_incident_bound_cupsd_logging[step above] by `<ctrl>+<c>`.
Incident-bound cupsd log (broken print queue is HPLIP supported)
Unfortunately, HPLIP libraries don't log into CUPS unit in journal, so if your print queue is installed with HPLIP driver (its device uri starts with `hp://`), we need incident-bound journal log.

Loading…

User avatar None

String updated in the repository
$ lp -d <print_queue_name> <file1> ... <fileN>
request id is <print_queue_name>-<JID> (N file(s))
$ lp -d <print_queue_name> <file1> ... <fileN>
request id is <print_queue_name>-<JID> (N file(s))
a year ago
Browse all string changes

Things to check

Ellipsis 1

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Unpluralised 2

The string is used as plural, but not using plural forms

Reset

Glossary

English English
No related strings found in the glossary.

14999731 String information

Source string description
type: delimited block -
Flags
no-wrap, read-only
Source string location
./pages/cups-debug-printing-issues.adoc:95
String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
pot/master/pages/cups-debug-printing-issues.pot, string 39