[cups] Error log not recording printer id

Bryan Mason bmason at redhat.com
Thu Mar 31 10:26:24 PDT 2016


On Thu, 2016-03-31 at 10:14 +1000, Alex Wilson wrote:
> Hi,
> 
> I support several Red Hat servers with different versions of cups.
>
> System A,
> CUPS version: cups-1.4.2-48.el6_3.1.i686
>  
> Error log identifies the printer:
> 
> D [31/Mar/2016:09:39:54 +1100] [Job 5334786] job-sheets=none,none
> D [31/Mar/2016:09:39:54 +1100] [Job 5334786] argv[0]="mainsps5"
> D [31/Mar/2016:09:39:54 +1100] [Job 5334786] argv[1]="5334786"
> 
> System B,
> Cups version: cups-1.4.2-67.el6.x86_64
> 
> Error log not listing printer ID:
> W [31/Mar/2016:10:06:46 +1100] [Job 518222] Remote host did not
>   respond with command status byte after 10 seconds!
> D [31/Mar/2016:10:06:46 +1100] [Job 518222] The following messages
>   were recorded from 10:06:46 AM to 10:06:46 AM
> D [31/Mar/2016:10:06:46 +1100] [Job 518222] Backend returned status 1
>   (failed)
> D [31/Mar/2016:10:06:46 +1100] [Job 518222] Retrying job on same
>   printer.
> D [31/Mar/2016:10:06:46 +1100] [Job 518222] End of messages
> 
> Both system cupsd.conf: LogLevel warn
> 
> System B cupsd.conf has: LogDebugHistory 2-messages
>
> What needs to be done to have the printer id recorded?

With "LogDebugHistory 2", only the last two debug messages are printed
when a job fails.  These are the "Backend returned status 1" and
"Retrying Job on same printer" messages above.

The debug message with the print queue name (argv[0]="mainsps5") is
created at the very beginning of a print job.  To get that message
printed, you'll need to increase "LogDebugHistory" or set it back to
it's default of 200, but then you'll get the entire debug history for
failed jobs.

~ Bryan




More information about the cups mailing list