Large cups systems?

[Kurt Pfeifle]

Seth Galitzer wrote:
> Kurt Pfeifle wrote:
>> You should indeed grab the next few spoolfiles which provoke a "hanging
>> job" and save them to somewhere else, and note down the target printers,
>> the job settings used, etc.
>>
>> (The files will be in the original format as received by CUPS, prior to
>> any filtering being applied).
>>
>> Then you can use these to try and reproduce the problem. You can also
>> see if the files would print if you sent them to a different printer
>> (model).
>>
> 
> One more quick question for clarification: So I have the spoolfile, I
> resubmit it with a simple lpr command, or just drop it back in the spooldir?

Re-submit it with "lpr -P printer1" or "lp -d printer333" to any printer
you like.

Dropping to the spool dir will not change a thing.

Resubmitting it will create a new job with the same input file.

*HOWEVER* make sure you use the same commandline params that CUPS is
seeing for that job (grep for "argv[5]" in the error_log). If it is
a job originating from Windows, that goes unfiltered through CUPS be-
cause of usage of native Windows printer drivers, then add the "-o raw"
option.

And *IF* it is a Windows RAW file, you can only re-submit it to the same
model family of printers.

Watch out if you notice any pattern for these jobs that make your printer
hang. Which file types, sizes, submitting clients, commandline options,
target printers, etc.

-- 
Kurt Pfeifle
System & Network Printing Consultant ---- Linux/Unix/Windows/Samba/CUPS
Infotec Deutschland GmbH  .....................  Hedelfinger Strasse 58
A RICOH Company  ...........................  D-70327 Stuttgart/Germany