t.pompe@architekt-prinz.at
2004-Dec-14 17:25 UTC
[Samba] Samba 3.0.9 doesn't remove printjobs ?
Hello! I'm using samba with CUPS printing (with raw passthru) for a long time now and it worked very well. But after upgrading my samba installation from 3.0.2 to 3.0.9, the printjobs (sent from XP Workstations) aren't removed from the joblist anymore. Means: the job is printed correctly, but opening the printqueue on the XP machine still contains the job (not only mine, but jobs from every user who sent one). When I now delete them manually, they're gone. Since I can't find any remaining SMB or CUPS spool-files, (thought about missing access rights for deletion) I don't know what to look for. The only error message I found is: tdb(/var/lib/samba/printing/Kyocera7000.tdb): rec_read bad magic 0xd9fee666 at offset=26084 in /var/log/samba/smbd (but I got this message sometimes before the upgrade too ...) Thanks for some hints on that (2) problem(s) Thomas
I've experienced this as well. I emailed Jerry off-list and he is working on it. On Dec 14, 2004, at 11:24 AM, t.pompe@architekt-prinz.at wrote:> Hello! > I'm using samba with CUPS printing (with raw passthru) > for a long time now and it worked very well. > > But after upgrading my samba installation from 3.0.2 to 3.0.9, > the printjobs (sent from XP Workstations) aren't > removed from the joblist anymore. > Means: the job is printed correctly, but opening the > printqueue on the XP machine still contains the job > (not only mine, but jobs from every user who sent one). > When I now delete them manually, they're gone. > > Since I can't find any remaining SMB or CUPS spool-files, > (thought about missing access rights for deletion) > I don't know what to look for. > > The only error message I found is: > tdb(/var/lib/samba/printing/Kyocera7000.tdb): rec_read bad magic > 0xd9fee666 at offset=26084 > in /var/log/samba/smbd (but I got this message sometimes before the > upgrade too ...) > > Thanks for some hints on that (2) problem(s) > Thomas > > > > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba >-- David Schlenk Operating Systems Analyst Bethel University Saint Paul, Minnesota david-schlenk@bethel.edu
Refer to some older messages -- there's a printing patch. HOWEVER, I am also told that this is related to an XP SP2 bug. Do you have SP2? ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - User Support Spec. III |$&| |__| | | |__/ | \| _| | novosirj@umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical Science Bldg - C630 On Tue, 14 Dec 2004 t.pompe@architekt-prinz.at wrote:> Hello! > I'm using samba with CUPS printing (with raw passthru) > for a long time now and it worked very well. > > But after upgrading my samba installation from 3.0.2 to 3.0.9, > the printjobs (sent from XP Workstations) aren't > removed from the joblist anymore. > Means: the job is printed correctly, but opening the > printqueue on the XP machine still contains the job > (not only mine, but jobs from every user who sent one). > When I now delete them manually, they're gone. > > Since I can't find any remaining SMB or CUPS spool-files, > (thought about missing access rights for deletion) > I don't know what to look for. > > The only error message I found is: > tdb(/var/lib/samba/printing/Kyocera7000.tdb): rec_read bad magic 0xd9fee666 at offset=26084 > in /var/log/samba/smbd (but I got this message sometimes before the upgrade too ...) > > Thanks for some hints on that (2) problem(s) > Thomas > > > > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba >
We just upgraded to Samba 3.0.9 (RedHat Enterprise 3 packages) this weekend and are now seeing similar issues on our workstations. I do not see any printing related errors in our logs however. I do however see these "backed up print queues" on every workstation. We run a mix of Windows 2000 (SP4) and XP Pro (SP2) machines. So it appears, at least in my case, that it's /not/ an XP-SP2 only issue. One other thing to note: We're in the midst of testing/deploying Debian Sarge servers to replace the RedHat boxes. On a whim this morning, I created a print server using one of my already-in-place Debian machines. To my amazement, the printer that I have hanging off of the Debian box does /not/ have this issue. What's odd about this...both of the print servers are running version 3.0.9. I've used the supplied distro's packages and not built from source in either case. So it appears from my simple tests, that something is different in the Debian build of Samba that cures this issue. A couple things that need to be said about this...I've only hung one printer off of the Debian box. In addition, I've only had two workstations printing to it - one XP-SP2 and one W2k-SP4. So it may very well have something to do with load or other such factor. But the problem has not yet appeared with the Debian package. I hope that this gives someone on the development team some clue as to the exact nature of the problem. I'll be available to answer any questions or fill any need for information that I can. Kevin> -----Original Message----- > From: t.pompe@architekt-prinz.at [mailto:t.pompe@architekt-prinz.at] > Sent: Tuesday, December 14, 2004 12:25 PM > To: samba@lists.samba.org > Subject: [Samba] Samba 3.0.9 doesn't remove printjobs ? > > Hello! > I'm using samba with CUPS printing (with raw passthru) for a > long time now and it worked very well. > > But after upgrading my samba installation from 3.0.2 to > 3.0.9, the printjobs (sent from XP Workstations) aren't > removed from the joblist anymore. > Means: the job is printed correctly, but opening the > printqueue on the XP machine still contains the job (not only > mine, but jobs from every user who sent one). > When I now delete them manually, they're gone. > > Since I can't find any remaining SMB or CUPS spool-files, > (thought about missing access rights for deletion) I don't > know what to look for. > > The only error message I found is: > tdb(/var/lib/samba/printing/Kyocera7000.tdb): rec_read bad > magic 0xd9fee666 at offset=26084 in /var/log/samba/smbd (but > I got this message sometimes before the upgrade too ...) > > Thanks for some hints on that (2) problem(s) Thomas > > > > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba >
Christian: The print jobs are working just fine, they simply seem to be hanging around in the client's queues. Any idea when the updated packages will be out? Kevin> -----Original Message----- > From: Christian Merrill [mailto:cmerrill@redhat.com] > Sent: Tuesday, December 21, 2004 10:36 AM > To: Collins, Kevin > Cc: 't.pompe@architekt-prinz.at'; samba@lists.samba.org > Subject: Re: [Samba] Samba 3.0.9 doesn't remove printjobs ? > > Collins, Kevin wrote: > > >We just upgraded to Samba 3.0.9 (RedHat Enterprise 3 packages) this > >weekend and are now seeing similar issues on our workstations. I do > >not see any printing related errors in our logs however. I > do however > >see these "backed up print queues" on every workstation. We > run a mix > >of Windows 2000 (SP4) and XP Pro (SP2) machines. So it appears, at > >least in my case, that it's /not/ an XP-SP2 only issue. > > > >One other thing to note: > > > >We're in the midst of testing/deploying Debian Sarge servers > to replace > >the RedHat boxes. On a whim this morning, I created a print server > >using one of my already-in-place Debian machines. To my > amazement, the > >printer that I have hanging off of the Debian box does /not/ > have this issue. > > > >What's odd about this...both of the print servers are > running version 3.0.9. > >I've used the supplied distro's packages and not built from > source in > >either case. So it appears from my simple tests, that something is > >different in the Debian build of Samba that cures this issue. > > > >A couple things that need to be said about this...I've only hung one > >printer off of the Debian box. In addition, I've only had two > >workstations printing to it - one XP-SP2 and one W2k-SP4. So it may > >very well have something to do with load or other such > factor. But the > >problem has not yet appeared with the Debian package. > > > >I hope that this gives someone on the development team some > clue as to > >the exact nature of the problem. > > > >I'll be available to answer any questions or fill any need for > >information that I can. > > > >Kevin > > > > > > > >>-----Original Message----- > >>From: t.pompe@architekt-prinz.at [mailto:t.pompe@architekt-prinz.at] > >>Sent: Tuesday, December 14, 2004 12:25 PM > >>To: samba@lists.samba.org > >>Subject: [Samba] Samba 3.0.9 doesn't remove printjobs ? > >> > >>Hello! > >>I'm using samba with CUPS printing (with raw passthru) for > a long time > >>now and it worked very well. > >> > >>But after upgrading my samba installation from 3.0.2 to 3.0.9, the > >>printjobs (sent from XP Workstations) aren't removed from > the joblist > >>anymore. > >>Means: the job is printed correctly, but opening the > printqueue on the > >>XP machine still contains the job (not only mine, but jobs > from every > >>user who sent one). > >>When I now delete them manually, they're gone. > >> > >>Since I can't find any remaining SMB or CUPS spool-files, (thought > >>about missing access rights for deletion) I don't know what to look > >>for. > >> > >>The only error message I found is: > >>tdb(/var/lib/samba/printing/Kyocera7000.tdb): rec_read bad magic > >>0xd9fee666 at offset=26084 in /var/log/samba/smbd (but I got this > >>message sometimes before the upgrade too ...) > >> > >>Thanks for some hints on that (2) problem(s) Thomas > >> > >> > >> > >> > >> > >> > >> > >>-- > >>To unsubscribe from this list go to the following URL and read the > >>instructions: https://lists.samba.org/mailman/listinfo/samba > >> > >> > >> > Are you seeing a problem where windows clients are able to > print but the print queues never clear? Or are they not even > printing? If you are experiencing the former then this is a > RH samba problem that should have been fixed by now -- please > let me know. It also warrants mentioning (per an earlier > thread) that our 3.0.9 packages are likely going to be > revised in a very short period of time to fix a kerberos > related problem. > > Christian >