[Samba] Samba, CUPS and Windows Printer Queue
Collins, Kevin
too much of a hitch on RedHat Enterprise "ES" 3.0. Late last week, RedHat
issued an Errata that moved Samba from the 3.0.2 base to the 3.0.4 base. So
when I did the "up2date" this weekend as part of my normal maintenance, this
server was updated and everything appeared to be fine.
Things are working, print jobs are getting sent so for the most part I am
happy. But, I am experiencing one problem. The Windows printer queue (I
have a mixed set of clients - mostly Windows 2000 and some Windows XP) show
active jobs even *after* the job has completed.
I've checked the CUPS Web-Management console and there are no active jobs.
Yet on my Windows machine, I have 4 printers that show to have a total of 47
print jobs in the queue.
Here is a snippet of the Print Server's smb.conf:
=================================================
[global]
# Server Name and description
workgroup = nesbitt.local
netbios name = valykyrie
server string = Samba 3 Print and Backup Server
# Samba log information
log file = /var/log/samba/%m.log
max log size = 7168
# Security information
security = user
encrypt passwords = yes
# To help performance
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
# Settings for PDC setup
local master = no
os level = 0
domain master = no
preferred master = no
domain logons = no
# Activate these Network Services
wins server = 10.200.8.253
# LDAP Declarations -- Needed to allow the LDAP backend to work
ldap suffix = dc=nesbitt,dc=local
ldap admin dn = cn=Manager,dc=nesbitt,dc=local
passdb backend = ldapsam:ldap://stargazer.nesbitt.local
ldap delete dn = no
ldap user suffix = ou=People
ldap group suffix = ou=Groups
ldap machine suffix = ou=Computers
ldap filter = (&(uid=%u)(objectClass=sambaSamAccount))
ldap passwd sync = yes
# Global settings for printers
printing = cups
printcap name = cups
load printers = yes
use client driver = yes
# Oplocks settings - disable all oplocks for compatibility reasons
oplocks = no
level2 oplocks = no
kernel oplocks = no
[printers]
comment = All Printers
path = /var/spool/samba
public = yes
guest ok = yes
writeable = no
printable = yes
=================================================
Has anyone experienced this? What other information is needed to help
diagnose this issue?
Any help would be welcomed...
--
Kevin L. Collins, MCSE
Systems Manager
Nesbitt Engineering, Inc.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
ALLEN, David (Shipley)
I cannot help you, but we have experienced a similar problem with 3.0.2a
running on Solaris and cups.
Old print jobs remain in the queue, connection to the printers is lost, and
worse, samba crashes for the user, causing Outlook to lock up. As a quick
fix we have deleted the printing lock files in /usr/local/samba/var/locks.
Samba.org have said it may be bug 1147, and recommend upgrading to 3.0.5. If
you find anything else I would be interested.
David
Collins, Kevin
I don't believe this is our problem...I'm not having Samba lock-up (or at
least not yet); I'm simply seeing every print job that has past though the
Samba/CUPS queue remain in the Windows printer queue.
Things _seem_ to be otherwise unaffected, this may change and I may indeed
experience a lock-up in the end, but I haven't yet.
Kevin
Collins, Kevin
3.0.2.
Also (and I don't know if it matters or not), this machine is part of a
Samba/LDAP controlled domain. All during this scenario the PDC was running
Samba 3.0.2. I've not yet had enough time to take the PDC down to do the
upgrade. Could the mixing of the two versions have caused the problem?
Kevin
>
> Just a bit more information...
>
> On the print server, if I delete
> /var/cache/samba/printing/<printername>.tdb, the queue for
> <printername> is cleared, but the retention starts again.
>
> In addition, I can remove the print jobs from the Windows
> side by right-clicking on the jobs and selecting "Cancel".
> But again, this doesn't not prevent the next job from being retained.
>
> I'm not sure if this helps or makes the diagnosis harder,
> just thought I'd let everyone know.
>
> Kevin
Craig White
> I've had a Samba 3.0.2 Print Server running for nearly 7 months now without
> too much of a hitch on RedHat Enterprise "ES" 3.0. Late last week, RedHat
> issued an Errata that moved Samba from the 3.0.2 base to the 3.0.4 base. So
> when I did the "up2date" this weekend as part of my normal maintenance, this
> server was updated and everything appeared to be fine.
>
> Things are working, print jobs are getting sent so for the most part I am
> happy. But, I am experiencing one problem. The Windows printer queue (I
> have a mixed set of clients - mostly Windows 2000 and some Windows XP) show
> active jobs even *after* the job has completed.
>
> I've checked the CUPS Web-Management console and there are no active jobs.
> Yet on my Windows machine, I have 4 printers that show to have a total of 47
> print jobs in the queue.
>
I have experienced this same problem - RH AS 3 upgraded to 3.0.4 and
printed jobs remain visible in the queue. I haven't spent any time on
this issue yet but if you find a solution, please post it.
Thanks,
Craig
Umberto Zanatta
rpm source, 'cos it doesn't support cups.
You should do:
# ldd /usr/sbin/smbd
if there isn't libcups.so.2 on screen, you have to do rebuild.
Il mar, 2004-07-27 alle 20:13, Craig White ha scritto:
> On Mon, 2004-07-26 at 05:51, Collins, Kevin wrote:
> > I've had a Samba 3.0.2 Print Server running for nearly 7 months now without
> > too much of a hitch on RedHat Enterprise "ES" 3.0. Late last week, RedHat
> > issued an Errata that moved Samba from the 3.0.2 base to the 3.0.4 base. So
> > when I did the "up2date" this weekend as part of my normal maintenance, this
> > server was updated and everything appeared to be fine.
> >
> > Things are working, print jobs are getting sent so for the most part I am
> > happy. But, I am experiencing one problem. The Windows printer queue (I
> > have a mixed set of clients - mostly Windows 2000 and some Windows XP) show
> > active jobs even *after* the job has completed.
> >
> > I've checked the CUPS Web-Management console and there are no active jobs.
> > Yet on my Windows machine, I have 4 printers that show to have a total of 47
> > print jobs in the queue.
> >
> ----
> I have experienced this same problem - RH AS 3 upgraded to 3.0.4 and
> printed jobs remain visible in the queue. I haven't spent any time on
> this issue yet but if you find a solution, please post it.
>
> Thanks,
>
> Craig
_______________________
Umberto Zanatta
linuxDidattica
tel: +39 (335) 54 71 385
email: umbe...@tin.it
web: http://linuxdidattica.org
_______________________
Craig White
> I've been experience by rpm compiled: you have to do rebuild samba
> from rpm source, 'cos it doesn't support cups.
>
> You should do:
>
> # ldd /usr/sbin/smbd
>
> if there isn't libcups.so.2 on screen, you have to do rebuild.
>
clearly not the issue...
# ldd /usr/sbin/smbd
libldap.so.2 => /usr/lib/libldap.so.2 (0xb75b3000)
liblber.so.2 => /usr/lib/liblber.so.2 (0xb75a8000)
libgssapi_krb5.so.2 => /usr/kerberos/lib/libgssapi_krb5.so.2
(0xb7595000)
libkrb5.so.3 => /usr/kerberos/lib/libkrb5.so.3 (0xb7537000)
libk5crypto.so.3 => /usr/kerberos/lib/libk5crypto.so.3
(0xb7526000)
libcom_err.so.3 => /usr/kerberos/lib/libcom_err.so.3
(0xb7524000)
libcups.so.2 => /usr/lib/libcups.so.2 (0xb750a000)
libssl.so.4 => /lib/libssl.so.4 (0xb74d6000)
libcrypto.so.4 => /lib/libcrypto.so.4 (0xb73e5000)
libnsl.so.1 => /lib/libnsl.so.1 (0xb73d0000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xb73a2000)
libpam.so.0 => /lib/libpam.so.0 (0xb739a000)
libattr.so.1 => /lib/libattr.so.1 (0xb7397000)
libacl.so.1 => /lib/libacl.so.1 (0xb7391000)
libresolv.so.2 => /lib/libresolv.so.2 (0xb737f000)
libdl.so.2 => /lib/libdl.so.2 (0xb737c000)
libpopt.so.0 => /usr/lib/libpopt.so.0 (0xb7373000)
libc.so.6 => /lib/tls/libc.so.6 (0xb723b000)
libsasl.so.7 => /usr/lib/libsasl.so.7 (0xb722f000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7221000)
liblaus.so.1 => /lib/liblaus.so.1 (0xb721e000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb75eb000)
libgdbm.so.2 => /usr/lib/libgdbm.so.2 (0xb7216000)
It would seem that something changed perhaps it was the way Samba was
compiled by Red Hat packagers but I don't think so.
By default, cups 'retains' successful print jobs (at least on RH AS 3),
and these jobs remain in the spool for the printer - and can be deleted
by the user if they are sufficiently privileged to alter the queue.
Craig