Hallo, My System: Samba 3.0.9 with printing-3.0.9-patch as printserver (Domainmember) on Sparc-Solaris-2.8 with CUPS-Server in a WINDOWS 2003 Server Domain. The BUG was already described by Spike Burkhardt and answered by Gerald (Jerry) Carter.(lists.samba.org/archive/samba/2004-October/094707.html). The problem isn't solved. Here a short description: When I print a file from a Windows-XP-Client over my printserver the job prints, the file get deleted on the server but in my system tray, it seems like the job never gets removed from the que. It seems like once the job doesn't get removed from the que it won't unless I specifically cancel the job. After I restart the samba server the problem vanish some times. m.f.g.
I am seeing this as well with a slightly modified version of 3.0.10 (see bug 2107), with samba on Solaris 9 and printing=sysv. It seems that jobs are aren't being removed from the samba print job list after they have been printed and are no longer on the Solaris print queue. There is also a weirdness if you view the queue with smbclient from solaris, as the first "queue" command gives the job number as 1-11 and the second and subsequent lists multiplies these numbers by 256.
(In reply to comment #1) > I am seeing this as well with a slightly modified version of 3.0.10 (see bug > 2107), with samba on Solaris 9 and printing=sysv. It seems that jobs are aren't > being removed from the samba print job list after they have been printed and are > no longer on the Solaris print queue. There is also a weirdness if you view the > queue with smbclient from solaris, as the first "queue" command gives the job > number as 1-11 and the second and subsequent lists multiplies these numbers by 256. I see the same behavior, if I view the queue with smbclient.
please test 3.0.11pre1. There is a chance this has been fixed (50/50 maybe).
Got a confirmation that the bug is indeed fixed in 3.0.11pre1.
(In reply to comment #4) > Got a confirmation that the bug is indeed fixed in 3.0.11pre1. At this time it seems that the bug is fixed. But the the problem with the jobnumbers described by Michael Young in Comment1 (There is also a weirdness if you view the queue with smbclient from solaris, as the first "queue" command gives the job number as 1-11 and the second and subsequent lists multiplies these numbers by 256.) still exist.
Ithink the odd job id's ia a byte ordering bug and different that the other reported issue of jobs not being cleared from queues that was reported on multiple platforms. Reopening the bug to deal with SOlaris.
*** Bug 1998 has been marked as a duplicate of this bug. ***
Actually I have had a reoccurence of the original queue problem with 3.0.11pre1. One extra thing I have noticed; from the windows list of all printers the total jobs in a queue is larger than the number of jobs listed if you view the queue, which suggests that sometimes a job is only partially deleted.
Created attachment 886 [details] Dump of printing/liblev2.dump This is a dump of one of the file which is presumably associated to one of the print queues liblev2. I notice it contains tags associated to a different queue cm131col which seems strange to me.
(In reply to comment #4) > Got a confirmation that the bug is indeed fixed in 3.0.11pre1. :-( Not yet - On linux x86 today I have again 600 print jobs on Windows Printer view. Samba is builded from this spec: http://cvs.pld-linux.org/cgi-bin/cvsweb/SPECS/samba.spec
I have now tried adding the patch mentioned in http://lists.samba.org/archive/samba/2005-January/098266.html and, so far at least, I haven't seen the print queue build up problem occuring.
(In reply to comment #11) > I have now tried adding the patch mentioned in > http://lists.samba.org/archive/samba/2005-January/098266.html > and, so far at least, I haven't seen the print queue build up problem occuring. Yes! Thanks!! Now my Win 98 clients doesn't get stack.
The problem on AIX is not fixed with 3.0.11pre1 and this patch. Still insane ID numbers in smbclient's "queue" output when running it multiple times, and not beeing able to cancel jobs, not reliable. Windows XP could never delete a job. I have the impression that it has improved for one situation: if smbd is freshly restarted you are the only connected client and you use the virtual ID number that you got from the first "queue" command to run "cancel ID", then it mostly works.
(In reply to comment #12) > (In reply to comment #11) > > I have now tried adding the patch mentioned in > > http://lists.samba.org/archive/samba/2005-January/098266.html > > and, so far at least, I haven't seen the print queue build up problem occuring. > Yes! Thanks!! Now my Win 98 clients doesn't get stack. CVS (or .11pre1+one line patch) is working for us fine too, no jobs stay any longer in the queue, W2K/XP.
looks like we're done here.
I have had a minor reoccurance of this with 3.0.14a. Some jobs were left in one queue in the "spooling" state, from about a week ago. There is no sign the jobs ever reached the server, so I am guessing they failed for some reason (maybe cancelled or the application sending them crashed), so the bug may still exist in a rare case.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.