Why Are Some Users' Jobs Always Held Pending?

[Kurt Pfeifle]

Brian White <bcwhite at precidia.com> wrote (Monday 19 June 2006 19:13):

> Does anyone have any ideas about this?  I've been unable to locate
> anything about these three machines that differs from the rest of the
> hosts here.

If you set "LogLevel debug" on the server -- do you see any
suspicious job-option set? Like "job-hold-until=indefinite"?

Do these clients print directly to the CUPS server, without
prior local spooling (such as is prompted when they have an
/etc/cups/client.conf, or $HOME/.cupsrc file with the CUPS
server named? Or do they have a local CUPS scheduler ("cupsd")
running?

Do these clients have /etc/cups/lpoptions or $HOME/.lpoptions
files enabled with suspicious entries?

Cheers,
Kurt


> Brian White wrote:
>> Version: 1.1.23-10sarge1
>> 
>> I have cups installed and can print to it via Linux just fine.  I also
>> have installed via Samba (via "cupsaddsmb") and most WinXP users can
>> print just fine, too.
>> 
>> However, a few (3 of about 20) users have the odd problem that every one
>> of their print jobs gets put in the queue and held.  I have to manually
>> go in to the web interface and click "release job" for every one of
>> them.  The other 17 or so users have their jobs go straight through. All
>> WinXP machines are on the same subnet on the same domain with identical
>> (automated, unattended) installations.  The cups logs show that the jobs
>> are being held but do not state any reason why.
>> 
>> What would cause the jobs of a few users to be held while others print
>> immediately?
>> 
>> Can I increase the log verbosity to tell why jobs are held?
>> 
>>                                           Brian
>>                                  ( bcwhite at precidia.com )
>> 
>>
-------------------------------------------------------------------------------
>> 
>>          A computer's attention span is only as long as its power cord.