Print queue not clearing for windows machines 1

[dodge20]

I have several networked printers to our linux server. 1 printer is having some issues. When I open the print queue for this printer on a windows machine it has everything that was printed since Jan 1 of this year. When I go into the common unix printing system, I don't see anything in queue. Is there a way I can clear this out? It is only happening with 1 printer.

Thanks

Dodge20

 

[QatQat]

try to delete the file /var/spool/lpd/your_trouble_printer.

Your samba printing cache instead sould be somewhere like

/var/cache/samba/printing/youprinter.tbd

Probably the latter file is the one that is causing problems. If you delete the former instead you may need to run printconf again and re-install the printer to get an empty file again.


Cheers
QatQat

Life is what happens when you are making other plans.

 

[dodge20]

QatQat

Thanks for the /var/cache/samba/printing/youprinter.tbd that cleared out the thousands of jobs in the queue. But it looks like all new jobs are remaining in the queue. I tried to find /var/spool/lpd/myprinter but I can't seem to find it. When I go into /var/spool/lpd and ls everything it doesn't show anything.

Any ideas?

Dodge20

 

[QatQat]

That's your unix printing queue, it means that nothing gets stuck there; your problem is samba in this case.

Check smb.conf for your queue settings, or try to setup winodz boxes top "print directly to the printer".

Usually you fin dsuch setting in the windoz printer driver config utility.

QatQat

Life is what happens when you are making other plans.

 

[dodge20]

Here is my smb.conf
I don't really know what I am looking for.

# Global parameters
[global]
workgroup = TCCDOMAIN
;netbios name = PDC
server string = ATBox Server
interfaces = eth0
bind interfaces only = Yes
;passdb backend = tdbsam smbpasswd
passdb backend = tdbsam
pam password change = Yes
passwd chat = *New*Password* %n\n *Re-enter*new*password* %n\n *Password*changed
*
username map = /etc/samba/smbusers
unix password sync = Yes
log level = 3
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139 445
name resolve order = wins bcast hosts
time server = Yes
printcap name = CUPS
show add printer wizard = No
add user script = /usr/sbin/useradd -m %u
delete user script = /usr/sbin/userdel -r %u
add group script = /usr/sbin/groupadd %g
delete group script = /usr/sbin/groupdel %g
add user to group script = /usr/sbin/usermod -G %g %u
add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null %u
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
logon script = scripts\logon.bat
#logon path = \\%L\profiles\%U
logon drive = X:
logon home = \\%L\%U
#domain logons = Yes
local master = Yes
os level = 33
preferred master = Yes
domain master = Yes
wins support = Yes
utmp = Yes
map acl inherit = Yes
printing = cups
veto oplock files = /*.doc/*.xls/*.mdb/

[IPC$]
path = /tmp

[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No

[printers]
comment = SMB Print Spool
path = /var/spool/samba
guest ok = no
printable = Yes
use client driver = Yes
default devmode = Yes
browseable = No

[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
guest ok = Yes
locking = No

#[profiles]
#comment = Profile Share
#path = /var/lib/samba/profiles
#read only = No
#profile acls = Yes

#[shared]
#comment = Network Shares
#path = /shared
#read only = No

Dodge20

 

[John Lewis]

There was a Samba bug that caused this problem. Fixed in 3.0.8. Type 'smbd -V' (capital V) at a command prompt to check your version and upgrade if your ar using 3.0.x < 8.

 

[dodge20]

I am using

3.0.10-1.4E

Dodge20

 

[John Lewis]

Evidently this one has been a bit stick for the Samba folks. There are several "resolved" bugs with similar problems, including one labeled fixed in 3.0.8.

The most recent report indicates that this is fixed in 3.0.23. You should upgrade and report this one to bugzilla if it persists.