samba - Jan 2006 - Windows print queue not clearing: Part II

Sorry for the addendum, but I've also noticed the following entries in the
logs:

Jan 30 12:28:38 primary smbd[2577]:
tdb(/var/cache/samba/printing/claser_3.tdb): rec_read bad magic 0x0 at
offset=21904
Jan 30 12:28:38 primary smbd[2577]: [2006/01/30 12:28:38, 0]
tdb/tdbutil.c:tdb_log(725)
Jan 30 12:28:38 primary smbd[2577]:
tdb(/var/cache/samba/printing/copier_4.tdb): rec_read bad magic 0xd9fee666
at offset=23256
Jan 30 12:28:38 primary smbd[2577]: [2006/01/30 12:28:38, 0]
tdb/tdbutil.c:tdb_log(725)
Jan 30 12:28:38 primary smbd[2577]:
tdb(/var/cache/samba/printing/copier_2.tdb): rec_read bad magic 0x0 at
offset=1

Lots of these.  I've tried deleting the /var/cache/samba/printing/name.tdb
but no luck.  My config looks as such:

     64 [copier_2]
     65         comment = Ricoh Aficio 2035
     66         printable = yes
     67         path = /var/spool/samba
     68         guest ok = yes
     69         printer admin = @wheel
     70 [copier_3]
     71         comment = Ricoh Aficio 2045eSP
     72         printable = yes
     73         path = /var/spool/samba
     74         public = yes
     75         guest ok = yes
     76         printer admin = @wheel
     77 [copier_4]
     78         comment = Ricoh Aficio 2035
     79         printable = yes
     80         path = /var/spool/samba
     81         public = yes
     82         guest ok = yes
     83         printer admin = @wheel
     84 [claser_3]
     85         comment = OkiData 9500
     86         printable = yes
     87         path = /var/spool/samba
     88         public = yes
     89         guest ok = yes
     90         printer admin = @wheel
     91 [server_print]
     92         comment = IBM 1332
     93         printable = yes
     94         path = /var/spool/samba
     95         public = yes
     96         guest ok = no
     97         printer admin = @wheel

Should I change the path to something less generic, such as
/var/spool/samba/printername/ ?  One last note - I am using driverless
printing via cupsaddsmb.

Thanks!

--
Michael S. Christian Jr.

>      64 [copier_2]
>      65         comment = Ricoh Aficio 2035
>      70 [copier_3]
>      71         comment = Ricoh Aficio 2045eSP
>      77 [copier_4]
> I am using driverless printing via cupsaddsmb.
You mean you're using the generic PostScript drivers?  If you're using
cupsaddsmb, why is each printer listed individually?  I think you're
only meant to have one [printers] share, which then picks up
everything you've added in via cupsaddsmb.  Perhaps listing each
printer individually is conflicting with the 'automatic' entries
created by Samba/CUPS?

Cheers,
Adam.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Christian wrote:
> Sorry for the addendum, but I've also noticed the following entries in
the
> logs:
> 
> Jan 30 12:28:38 primary smbd[2577]:
> tdb(/var/cache/samba/printing/claser_3.tdb): rec_read bad magic 0x0 at
> offset=21904
> Jan 30 12:28:38 primary smbd[2577]: [2006/01/30 12:28:38, 0]
> tdb/tdbutil.c:tdb_log(725)
> Jan 30 12:28:38 primary smbd[2577]:
> tdb(/var/cache/samba/printing/copier_4.tdb): rec_read bad magic 0xd9fee666
> at offset=23256
> Jan 30 12:28:38 primary smbd[2577]: [2006/01/30 12:28:38, 0]
> tdb/tdbutil.c:tdb_log(725)
> Jan 30 12:28:38 primary smbd[2577]:
> tdb(/var/cache/samba/printing/copier_2.tdb): rec_read bad magic 0x0 at
> offset=1
>
> Lots of these.  I've tried deleting the
> /var/cache/samba/printing/name.tdb
> but no luck.  My config looks as such:
Somethings wrong then.  tdb corruption is pretty rare in my
experience.

I can't remember your original message but if the prnit job status
in the Windows queue monitor says "Printed", then the problem is
that cups is not removing the job from the queue listing (i.e.
you should see the same job shown via lpq).

If the job stil shows on the Windows client as spooling, then
please test 3.0.21b.  The bug should be resolved (although a
release earlier than 3.0.21b would probably fix the problem
as well).  There's not a single fix I can point you at to fix
it.



cheers, jerry
====================================================================I live in a
Reply-to-All world                -----------------------
Samba                                    ------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD33I1IR7qMdg1EfYRAoeSAJ9AGrJPmcIa/+D5eTxR8Qs2uL0SKgCfXLMD
EskM1LIukxxGDOm8Oe0qryQ=Rdf7
-----END PGP SIGNATURE-----