Urs Rau wrote:>>I start to wonder what "dammage" it would do to set lpq to >>lpq command =/bin/true >>for my pdf printer? ;-) > > > > Well, wonder no more sir!!!!!! I set my lpq command = /bin/trueand> ALL QUEUES CLEAR AND ACT PROPERLY!!!!!!!!!!!! I could kiss you!That was all I did, I can't believe it worked......thank you!!!!!!>I am glad it helped. Thanks for doing the testing for me. ;-) Actually I can't really take full credit for this idea as it was one of my colleagues Matt that had suggested doing just that with my pdf problems, minutes before I saw your post, in order to avoid the cups printer not found msgs I got with my "proper" lpq command line.> printer share's are configured for each department : (preprintpdf is > just a sepaerate file so I could quickly set the pdf size , etc.) > > [IT pdf printer] > printer admin = "NEWYORK+domain users" > force printername = yes > browseable = yes > path = /pdfdropbox/IT > printable = yes > print command = /usr/bin/preprintpdf %s > lpq command = /bin/true > lprm commandHello, I'm hoping someone can help me. I have several pdf printers set up and when I print to them samba becomes unstable and several errors are dumped to the log. These pdf printers were working when I was using version 3.0.6. When I went to a newer version of samba the queue would not clear on the windows side and no errors were logged. Yesterday I upgraded to version 3.0.13-1 and the errors started and the queue still will not clear. I have deleted several tdb files to no avail. I am using "printing = bsd" option as I have in the past. Below is a clip from the log. Please let me know if anyone needs more information. [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 1409 ltype=0 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 0 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 295 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 4128 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 3445 ltype=0 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 4128 ltype=0 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 3445 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 1717 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 480 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] printing/printing.c:print_queue_update_internal(1195) print_queue_update: failed to store MSG_PENDING flag for [IT pdf printer]! [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 1321 ltype=1 (Bad file descriptor) [2005/03/29 10:49:05, 0] printing/printing_db.c:get_print_db_byname(66) get_print_db: Failed to close tdb for printer IT pdf printer [2005/03/29 10:49:11, 1] smbd/service.c:make_connection_snum(642) bmg2001 (192.168.42.106) connect to service public initially as user NEWYORK+deborahp (uid=10008, gid=10011) (pid 23475) [2005/03/29 10:50:04, 0] lib/fault.c:fault_report(36) ==============================================================[2005/03/29 10:50:04, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 23459 (3.0.13) Please read the appendix Bugs of the Samba HOWTO collection [2005/03/29 10:50:04, 0] lib/fault.c:fault_report(39) ==============================================================[2005/03/29 10:50:04, 0] lib/util.c:smb_panic2(1495) PANIC: internal error [2005/03/29 10:50:04, 0] lib/util.c:smb_panic2(1503) BACKTRACE: 14 stack frames: #0 smbd(smb_panic2+0x128) [0x81df9d8] #1 smbd(smb_panic+0x19) [0x81df8a9] #2 smbd [0x81cd252] #3 /lib/tls/libc.so.6 [0x420277b8] #4 smbd(tdb_fetch_int32_byblob+0x45) [0x81f4f75] #5 smbd(tdb_fetch_int32+0x28) [0x81f4fe8] #6 smbd [0x81fb637] #7 smbd [0x81fbe51] #8 smbd [0x81fc06e] #9 smbd(message_dispatch+0x13c) [0x81e823c] #10 smbd(start_background_queue+0x1cd) [0x81fc28d] #11 smbd(main+0x68b) [0x8257abb] #12 /lib/tls/libc.so.6(__libc_start_main+0xe4) [0x42015704] #13 smbd(ldap_msgfree+0x89) [0x80792a1]
Hi all, Has anyone figured out why some people are not having a problem with similar configurations, however some people require that we add the "lpq command = /bin/true" line? It is a very good and simple solution. Should all pdf printers be set with this option for future reference? Urs Rau wrote:>>I start to wonder what "dammage" it would do to set lpq to >>lpq command =/bin/true >>for my pdf printer? ;-) > > > > Well, wonder no more sir!!!!!! I set my lpq command = /bin/trueand> ALL QUEUES CLEAR AND ACT PROPERLY!!!!!!!!!!!! I could kiss you!That was all I did, I can't believe it worked......thank you!!!!!!>I am glad it helped. Thanks for doing the testing for me. ;-) Actually I can't really take full credit for this idea as it was one of my colleagues Matt that had suggested doing just that with my pdf problems, minutes before I saw your post, in order to avoid the cups printer not found msgs I got with my "proper" lpq command line.> printer share's are configured for each department : (preprintpdf is > just a sepaerate file so I could quickly set the pdf size , etc.) > > [IT pdf printer] > printer admin = "NEWYORK+domain users" > force printername = yes > browseable = yes > path = /pdfdropbox/IT > printable = yes > print command = /usr/bin/preprintpdf %s > lpq command = /bin/true > lprm commandHello, I'm hoping someone can help me. I have several pdf printers set up and when I print to them samba becomes unstable and several errors are dumped to the log. These pdf printers were working when I was using version 3.0.6. When I went to a newer version of samba the queue would not clear on the windows side and no errors were logged. Yesterday I upgraded to version 3.0.13-1 and the errors started and the queue still will not clear. I have deleted several tdb files to no avail. I am using "printing = bsd" option as I have in the past. Below is a clip from the log. Please let me know if anyone needs more information. [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 1409 ltype=0 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 0 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 295 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 4128 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 3445 ltype=0 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 4128 ltype=0 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 3445 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 1717 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 480 ltype=1 (Bad file descriptor) [2005/03/29 10:49:03, 0] printing/printing.c:print_queue_update_internal(1195) print_queue_update: failed to store MSG_PENDING flag for [IT pdf printer]! [2005/03/29 10:49:03, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/printing/IT pdf printer.tdb): tdb_lock failed on list 1321 ltype=1 (Bad file descriptor) [2005/03/29 10:49:05, 0] printing/printing_db.c:get_print_db_byname(66) get_print_db: Failed to close tdb for printer IT pdf printer [2005/03/29 10:49:11, 1] smbd/service.c:make_connection_snum(642) bmg2001 (192.168.42.106) connect to service public initially as user NEWYORK+deborahp (uid=10008, gid=10011) (pid 23475) [2005/03/29 10:50:04, 0] lib/fault.c:fault_report(36) ==============================================================[2005/03/29 10:50:04, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 23459 (3.0.13) Please read the appendix Bugs of the Samba HOWTO collection [2005/03/29 10:50:04, 0] lib/fault.c:fault_report(39) ==============================================================[2005/03/29 10:50:04, 0] lib/util.c:smb_panic2(1495) PANIC: internal error [2005/03/29 10:50:04, 0] lib/util.c:smb_panic2(1503) BACKTRACE: 14 stack frames: #0 smbd(smb_panic2+0x128) [0x81df9d8] #1 smbd(smb_panic+0x19) [0x81df8a9] #2 smbd [0x81cd252] #3 /lib/tls/libc.so.6 [0x420277b8] #4 smbd(tdb_fetch_int32_byblob+0x45) [0x81f4f75] #5 smbd(tdb_fetch_int32+0x28) [0x81f4fe8] #6 smbd [0x81fb637] #7 smbd [0x81fbe51] #8 smbd [0x81fc06e] #9 smbd(message_dispatch+0x13c) [0x81e823c] #10 smbd(start_background_queue+0x1cd) [0x81fc28d] #11 smbd(main+0x68b) [0x8257abb] #12 /lib/tls/libc.so.6(__libc_start_main+0xe4) [0x42015704] #13 smbd(ldap_msgfree+0x89) [0x80792a1]
> Luca Olivetti wrote: > > Vincent Mikalinis wrote: > > > > > Hi all, > > > > > > Has anyone figured out why some people are not havinga> > > problem with similar configurations, however some > > > people require that we add the "lpq command /bin/true" > > > line? It is a very good and simple solution. Shouldall> > > pdf printers be set with this option for futurereference?> > > > I don't know, but I bypassed the problem by using a pdf > > backend in cups (which is really a simple shell script > > that I tailored to my needs), so even the pdf printer > > is a "normal" cups printer. > > Somebody called "misty" said the same thing in IRC #samba > yesterday, but they had to run before they could show me > the contents of the file. Would you mind sending this to > the list? I think it is still at least slighlty > "on-topic". > > The person on IRC said they then have another cron job > that goes and emails the so created pdf every 5 minutes > to the users that created them. For one situation here > that would be THE ideal solution. So if misty or anybody > else that happens to have the same solution wouldn't mind > emailing me the details for that, that would be really > appreciated. >There is a cups backend pdf creator tool by Volker Behr which can be set up to write the pdf file to the user's home directory. To do this the tool must be compiled with this option (documentation is available). Using this option there is no need to use a script + cron job to move the pdf to the user's home directory. The drawback of using this method is that cups security must be relaxed a bit to include "RunAsUser=No". The tool can be found at: http://cip.physik.uni-wuerzburg.de/~vrbehr/cups-pdf/