[cups.bugs] cups 1.1.21 socket backend problem?

[David Schlenk]

We are also running samba 3.0.7.  I can't believe that it is a samba 
problem as our samba/cups server is a step removed from the cups server 
that's having the problems (essentially the samba/cups server sends all 
jobs to another cups server via IPP and then that server actually send 
them to the printer via the socket backend).

Hansjoerg Maurer wrote:
> Hi
> 
> David Schlenk wrote:
> 
>> First, brief overview of my setup:
>>
>> 2 backend cups servers that actually send the jobs to printers
>> 3 frontend cups servers, 2 of which serve out the load balanced 
>> backend queues via netatalk (two different subnets), and the other 
>> servers them out via samba.
>>
>> I upgraded to 1.1.21 a week ago or so and ever since have been 
>> experiencing a couple queues stop themselves because of a job that 
>> seems to get stuck in the queue. The printer becomes unavailable on 
>> port 9100, but I can still ping it from the print server.  The printer 
>> won't start printing again until I clear out the queue and restart the 
>> printer, and then cancel whatever job is stuck on the printer one last 
>> time (if you cancel it prior to clearing out the cups queue it keeps 
>> coming back). It seems like some kind of two way communication is 
>> breaking down, but I can't really tell from the logs what's going on.  
>> There doesn't seem to be any pattern to what kind of jobs stop it, but 
>> I believe once it was a word file and at least twice it was a PDF file.
>>
> we have seen the same problem on after a cups update to 1.1.21 on 
> solaris 8 and found no soltution until now...
> 
> Unfortunatly we did a  samba update to 3.0.7 at the same time to, so I 
> haven't been sure , if this is a cups or a samba problem.
> Are you running the same samba version as before?
> 
> Thank you very much
> 
> Hansjörg
> 
> 
>> Another note - when one of my backend cups servers goes down, it seems 
>> to also crash the frontend cups server that runs on the samba box. 
>> Anyone else experience this? Its been happening to me since at least 
>> 1.1.18. Kinda makes loadbalanced/failsafe rather useless...
> 
> 
> 
> 

-- 
David Schlenk
Operating Systems Analyst
Bethel University
david-schlenk at bethel.edu