samba - Sep 2009 - Print queue show jobs when queried from windows, nothing in cups

We have a print server running RHEL 4, w/ samba-3.0.33-0.15.el4

When viewed from windows, one queue on the system has the "remains" of
264
print jobs - some dating back to April, but I can't find where the 
information is coming from. Apparently the jobs print fine, but then the 
information sticks in the queue information.

Running lpq on the Samba system shows:
# lpq -a
no entries 

I dumped a few tdbs and upped my log level to 10, but I didn't see any 
logging from cups_queue_get. I thought Samba would go into that code to 
reload the queue information.

Any hints on what to try next to clean up my queue?

Thanks,
- Bill

On 09/25/2009 03:30 PM, William Marshall wrote:
> We have a print server running RHEL 4, w/ samba-3.0.33-0.15.el4
> 
> When viewed from windows, one queue on the system has the
"remains" of 264
> print jobs - some dating back to April, but I can't find where the 
> information is coming from. Apparently the jobs print fine, but then the 
> information sticks in the queue information.
> 
> Running lpq on the Samba system shows:
> # lpq -a
> no entries 
> 
> I dumped a few tdbs and upped my log level to 10, but I didn't see any 
> logging from cups_queue_get. I thought Samba would go into that code to 
> reload the queue information.
> 
> Any hints on what to try next to clean up my queue?
> 
> Thanks,
> - Bill
Suggest you check the CUPS printing directory (/var/spool/cups) for the
presence of completed print job info.  If these exist:

a) Remove them all, then restart CUPS.

b) Edit /etc/cups/cupsd.conf so it will delete completed print job info.

- John T.

On Fri, Sep 25, 2009 at 03:30:14PM -0500, William Marshall
wrote:
> We have a print server running RHEL 4, w/ samba-3.0.33-0.15.el4
> 
> When viewed from windows, one queue on the system has the
"remains" of 264
> print jobs - some dating back to April, but I can't find where the 
> information is coming from. Apparently the jobs print fine, but then the 
> information sticks in the queue information.
> 
> Running lpq on the Samba system shows:
> # lpq -a
> no entries 
> 
> I dumped a few tdbs and upped my log level to 10, but I didn't see any 
> logging from cups_queue_get. I thought Samba would go into that code to 
> reload the queue information.
> 
> Any hints on what to try next to clean up my queue?
I think once the printer queue is empty you can stop Samba,
delete the specific printer tdb and restart. Should do it.
Deleting the tdb whist Samba is running should also be safe,
but I'm less confident about that :-).

Jeremy.