[cups] CUPS sometimes losing jobs upon restart

[Nick]

On Mon, Aug 24, 2015 at 1:01 PM, Tim Mooney <Tim.Mooney at ndsu.edu> wrote:

> In regard to: [cups] CUPS sometimes losing jobs upon restart, Nick Hall...:
>
> D [08/Aug/2015:06:36:28 -0500] [Job 498606] Loading from cache...
>> I [08/Aug/2015:06:36:28 -0500] [Job 498606] Data files have gone away!
>> E [08/Aug/2015:06:36:28 -0500] Bad File number 1 on line 88798!
>> D [08/Aug/2015:06:36:28 -0500] [Job 498606] Loading attributes...
>> E [08/Aug/2015:06:36:37 -0500] [Job 498606] Aborting job because it has no
>> files.
>>
>> This is CUPS version 1.5.3-5+deb7u6 which is part of Debian wheezy.
>>
>> Does anyone know what is going on or have a suggestion of what I can do to
>> track down this problem? Thanks,
>>
>
> You'll want to read up on ErrorPolicy.  The default is probably abort-job,
> which isn't what you want in this case.  Take a look at retry-job.
>
> However, that may not be enough.  The "Data files have gone away!" error
> is concerning.  Even if you switch your ErrorPolicy to retry-job, it
> probably can't retry it if the data file has disappeared.
>
> Could you also check your /etc/cups/cupsd.conf to see if you have any
> setting for MaxJobs?  I'm asking, because I wonder if the data file might
> be "going away" because your MaxJobs is too low?
>
> Tim
> --
> Tim Mooney                                             Tim.Mooney at ndsu.edu
> Enterprise Computing & Infrastructure                  701-231-1076
> (Voice)
> Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
>
Here are some relevant settings in cupsd.conf:

MaxJobs 10000
FilterLimit 0
ErrorPolicy retry-job
JobRetryInterval 15
JobRetryLimit 999999999

The printer in question also has "ErrorPolicy retry-job".

So it should be retrying automatically instead of aborting, and MaxJobs is
set to 10000 which is plenty that we would never hit that limit. Thanks,

Nick