Antwort: Re: LPRng: too many errors, only workers here
Hi Patrick, I already sent the scripts. It was a hint from walter to change the printcap entry to pipe the stream through the script via lp=| and not invoke the if= parameter. Until now, it seems to work. ps2pdf|PDF-Server:\ :bk:sh:mx#0:ml#0:\ :lpd_bounce=true:\ :sd=/var/spool/lpd/ps2pdf:\ :lp=|/usr/local/bin/ps2pdf/pdfmail.pl: Thanks ! juergen Patrick Powell [EMAIL PROTECTED] com An Gesendet von: [EMAIL PROTECTED] [EMAIL PROTECTED] Kopie .com Thema Re: LPRng: too many errors, only 05.10.2004 18:45 workers here Bitte antworten an [EMAIL PROTECTED] ps2pdf|PDF-Server:\ :bk:sh:mx#0:ml#0:\ :lp=/dev/null:\ :lpd_bounce=true:\ :sd=/var/spool/lpd/ps2pdf:\ :if=/usr/local/bin/ps2pdf/pdfmail.pl: -- how it happens The Client prints as usually his request to the PDF-Printer (HP/Lexmark) via LPR to the LPRng Server. LPRng invokes the perl script and nothing else happens, no result, nothing. The 'lpq -c -n5 -Pps2pdf' shows me the following result: I suspect the pdftops script is the cause of problems here. One of the issues with PDF is that it usually needs some temp file directory. Can you send me the details of the pdfmail.pl script? Patrick - YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRng MAILING LIST The address you post from or your Reply-To address MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. To subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST mailaddr | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST mailaddr | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, call Patrick Powell or one of the friendly staff at Astart Technologies for help. Astart also does support for LPRng. Also, check the Web Page at: http://www.lprng.com for any announcements. Astart Technologies (LPRng - Print Spooler http://www.lprng.com) 6741 Convoy Court San Diego, CA 92111 858-874-6543 FAX 858-751-2435 - - YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRng MAILING LIST The address you post from or your Reply-To address MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. To subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST mailaddr | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST mailaddr | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, call Patrick Powell or one of the friendly staff at Astart Technologies for help. Astart also does support for LPRng. Also, check the Web Page at: http://www.lprng.com for any announcements. Astart Technologies (LPRng - Print Spooler http://www.lprng.com) 6741 Convoy Court San Diego, CA 92111 858-874-6543 FAX 858-751-2435 -
Antwort: Re: LPRng: too many errors, only workers here
hi christoph, not at all. the client sends the lp-job to the LPRng server which activates a perl script. there is no printer connected. thanx jn christoph.beyer@ desy.de Gesendet von: An [EMAIL PROTECTED] [EMAIL PROTECTED] .comKopie Thema 01.10.2004 08:12 Re: LPRng: too many errors, only workers here Bitte antworten an [EMAIL PROTECTED] Hi Juergen, looks a bit strange, are you sur you don't have a networking or 'printer-connecting' problem ? In the printcap or the lpd.conf file (globally) you can set 'send_try=0' The default is at 3 which means the server will try to connect the printer three times, ( - too many errors after three tries) '0' means infinite tries. So you can try to connect the port (probably 515) manually during the non-working period with 'lpq -P515@printer' and see if there is a problem connecting the port you are using... Hope this helps... best regards ~christoph -- /* Christoph Beyer | Office: Building 2b / 23 *\ * DESY|Phone: 040-8998-2317* * - IT - | Fax: 040-8998-4060* \* 22603 Hamburg | http://www.desy.de */ On Wed, 22 Sep 2004 [EMAIL PROTECTED] wrote: I have found strange behavior of LPRng working together with a perl/ghostscript ps2pdf script. This combination worked in the past (RH 7.2 - 8.0) without difficulties but since RedHat dropped LPRng from the distrib-CDs, my trio sometimes -not predictable - comes out on strike. After a reboot it works again (same client, same printjob, etc) -- environment different hardware = P2 266 Compaq Proliant / Dual Xeon 3,0 GHz Tarox Intel Servers (all with RAID) OS = Fedora FC1 / FC2 (2.6.8-1) rpmbuild LPRng, SPEC without modification = ftp://ftp.lprng.com/pub/LPRng/LPRng/LPRng-3.8.27-1.src.rpm XP Client = LPR Port, with HP ColorLaserJet 5 / Lexmark Optra Color 1200 PS printcap= .. ps2pdf|PDF-Server:\ :bk:sh:mx#0:ml#0:\ :lp=/dev/null:\ :lpd_bounce=true:\ :sd=/var/spool/lpd/ps2pdf:\ :if=/usr/local/bin/ps2pdf/pdfmail.pl: -- how it happens The Client prints as usually his request to the PDF-Printer (HP/Lexmark) via LPR to the LPRng Server. LPRng invokes the perl script and nothing else happens, no result, nothing. The 'lpq -c -n5 -Pps2pdf' shows me the following result: Printer: [EMAIL PROTECTED] 'PDF-Server' Queue: no printable jobs in queue Server: no server active Status: finished '[EMAIL PROTECTED]', status 'JFAIL' at 11:52:53.559 Status: job '[EMAIL PROTECTED]', attempt 3, allowed 3 at 11:52:53.579 Status: send_failure_action 'JREMOVE' at 11:52:53.580 Status: job '[EMAIL PROTECTED]', removing job - status JREMOVE at 11:52:53.581 Status: job '[EMAIL PROTECTED]' saved at 11:52:53.587 Rank Owner/ID Pr/Class Job Files Size Time error [EMAIL PROTECTED] A 6 ERROR: too many errors The hereby created spool-file (dfA005SBIV0302-34) runs without errors through the filterscript. # cat dfA005SBIV0302-34 | /usr/local/bin/ps2pdf/pdfmail.pl #job 15 at 2004-09-16 11:39 (errorlevel=0) Very very strange is, that from now on, there is no way out to get a PDF File out from LPRng. Every job is aborted/killed with too many errors ! The Page which was printed, can be as simple as it could be (eg. notepad test) I tried rm -f /var/spool/lpd/ps2pdf/* /usr/sbin/checkpc -f /sbin/service lpd restart print again the same simple page - same result. Only a reboot of the whole server solves the problem. I reboot the linux server and print the same page through the same Printer (hundred times) - OK. -- digging in the logs I took a closer look at the logfiles and compared the one when LPRng reports me a too many error failure and the logfile (printing the same document) after a reboot (restarting lpd is not sufficient
Re: LPRng: too many errors, only workers here
From [EMAIL PROTECTED] Thu Sep 30 16:19:20 2004 Subject: LPRng: too many errors, only workers here To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Date: Wed, 22 Sep 2004 19:41:57 +0200 I have found strange behavior of LPRng working together with a perl/ghostscript ps2pdf script. This combination worked in the past (RH 7.2 - 8.0) without difficulties but since RedHat dropped LPRng from the distrib-CDs, my trio sometimes -not predictable - comes out on strike. After a reboot it works again (same client, same printjob, etc) -- environment different hardware = P2 266 Compaq Proliant / Dual Xeon 3,0 GHz Tarox Intel Servers (all with RAID) OS = Fedora FC1 / FC2 (2.6.8-1) rpmbuild LPRng, SPEC without modification = ftp://ftp.lprng.com/pub/LPRng/LPRng/LPRng-3.8.27-1.src.rpm XP Client = LPR Port, with HP ColorLaserJet 5 / Lexmark Optra Color 1200 PS printcap= .. ps2pdf|PDF-Server:\ :bk:sh:mx#0:ml#0:\ :lp=/dev/null:\ :lpd_bounce=true:\ :sd=/var/spool/lpd/ps2pdf:\ :if=/usr/local/bin/ps2pdf/pdfmail.pl: -- how it happens The Client prints as usually his request to the PDF-Printer (HP/Lexmark) via LPR to the LPRng Server. LPRng invokes the perl script and nothing else happens, no result, nothing. The 'lpq -c -n5 -Pps2pdf' shows me the following result: I suspect the pdftops script is the cause of problems here. One of the issues with PDF is that it usually needs some temp file directory. Can you send me the details of the pdfmail.pl script? Patrick - YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRng MAILING LIST The address you post from or your Reply-To address MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. To subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST mailaddr | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST mailaddr | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, call Patrick Powell or one of the friendly staff at Astart Technologies for help. Astart also does support for LPRng. Also, check the Web Page at: http://www.lprng.com for any announcements. Astart Technologies (LPRng - Print Spooler http://www.lprng.com) 6741 Convoy Court San Diego, CA 92111 858-874-6543 FAX 858-751-2435 -
Re: LPRng: too many errors, only workers here
hi juergen, i am looking for a comparable effect. (sonetimes) under load the queue stops and the worker dont start. causing the queue to pile up work. stop/start the daemon restarts the queue. The problem is not reproduceable so far it ust happens. its not replated to memory/filesystem etc. regards, walter - - - - - - - - - - - - - - Original Message - - - - - - - - - - - - - - From: [EMAIL PROTECTED] Subject: LPRng: too many errors, only workers here Date: 09/22/04 19:41 - YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRng MAILING LIST The address you post from or your Reply-To address MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. To subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST mailaddr | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST mailaddr | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, call Patrick Powell or one of the friendly staff at Astart Technologies for help. Astart also does support for LPRng. Also, check the Web Page at: http://www.lprng.com for any announcements. Astart Technologies (LPRng - Print Spooler http://www.lprng.com) 6741 Convoy Court San Diego, CA 92111 858-874-6543 FAX 858-751-2435 -
Re: LPRng: too many errors, only workers here
Hi Juergen, looks a bit strange, are you sur you don't have a networking or 'printer-connecting' problem ? In the printcap or the lpd.conf file (globally) you can set 'send_try=0' The default is at 3 which means the server will try to connect the printer three times, ( - too many errors after three tries) '0' means infinite tries. So you can try to connect the port (probably 515) manually during the non-working period with 'lpq -P515@printer' and see if there is a problem connecting the port you are using... Hope this helps... best regards ~christoph -- /* Christoph Beyer | Office: Building 2b / 23 *\ * DESY|Phone: 040-8998-2317* * - IT - | Fax: 040-8998-4060* \* 22603 Hamburg | http://www.desy.de */ On Wed, 22 Sep 2004 [EMAIL PROTECTED] wrote: I have found strange behavior of LPRng working together with a perl/ghostscript ps2pdf script. This combination worked in the past (RH 7.2 - 8.0) without difficulties but since RedHat dropped LPRng from the distrib-CDs, my trio sometimes -not predictable - comes out on strike. After a reboot it works again (same client, same printjob, etc) -- environment different hardware = P2 266 Compaq Proliant / Dual Xeon 3,0 GHz Tarox Intel Servers (all with RAID) OS = Fedora FC1 / FC2 (2.6.8-1) rpmbuild LPRng, SPEC without modification = ftp://ftp.lprng.com/pub/LPRng/LPRng/LPRng-3.8.27-1.src.rpm XP Client = LPR Port, with HP ColorLaserJet 5 / Lexmark Optra Color 1200 PS printcap= .. ps2pdf|PDF-Server:\ :bk:sh:mx#0:ml#0:\ :lp=/dev/null:\ :lpd_bounce=true:\ :sd=/var/spool/lpd/ps2pdf:\ :if=/usr/local/bin/ps2pdf/pdfmail.pl: -- how it happens The Client prints as usually his request to the PDF-Printer (HP/Lexmark) via LPR to the LPRng Server. LPRng invokes the perl script and nothing else happens, no result, nothing. The 'lpq -c -n5 -Pps2pdf' shows me the following result: Printer: [EMAIL PROTECTED] 'PDF-Server' Queue: no printable jobs in queue Server: no server active Status: finished '[EMAIL PROTECTED]', status 'JFAIL' at 11:52:53.559 Status: job '[EMAIL PROTECTED]', attempt 3, allowed 3 at 11:52:53.579 Status: send_failure_action 'JREMOVE' at 11:52:53.580 Status: job '[EMAIL PROTECTED]', removing job - status JREMOVE at 11:52:53.581 Status: job '[EMAIL PROTECTED]' saved at 11:52:53.587 Rank Owner/ID Pr/Class Job Files Size Time error [EMAIL PROTECTED] A 6 ERROR: too many errors The hereby created spool-file (dfA005SBIV0302-34) runs without errors through the filterscript. # cat dfA005SBIV0302-34 | /usr/local/bin/ps2pdf/pdfmail.pl #job 15 at 2004-09-16 11:39 (errorlevel=0) Very very strange is, that from now on, there is no way out to get a PDF File out from LPRng. Every job is aborted/killed with too many errors ! The Page which was printed, can be as simple as it could be (eg. notepad test) I tried rm -f /var/spool/lpd/ps2pdf/* /usr/sbin/checkpc -f /sbin/service lpd restart print again the same simple page - same result. Only a reboot of the whole server solves the problem. I reboot the linux server and print the same page through the same Printer (hundred times) - OK. -- digging in the logs I took a closer look at the logfiles and compared the one when LPRng reports me a too many error failure and the logfile (printing the same document) after a reboot (restarting lpd is not sufficient) As you can see, the Server process did not start (wonder why) in the faulty print job. I miss the (Server) ps2pdf: Start_worker (Server) ps2pdf: Do_queue_jobs: MAIN LOOP (Server) ps2pdf: Do_queue_jobs: Susr1 before lines which I marked with an asterik in the log of the working job. Can anyone explain me that phenomenon / reason for that behavior ? logfile of the working job AFTER reboot .. 2004-09-22-14:43:29.586 jh-server08 [2080] LPD_CALL ps2pdf: Make_lpd_call: fd 2 - 2 2004-09-22-14:43:29.586 jh-server08 [2080] LPD_CALL ps2pdf: Make_lpd_call: fd 3 - 3 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) ps2pdf: Service_worker: begin 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) ps2pdf: Fix_Rm_Rp_info: printer name 'ps2pdf' 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) Reset_config: starting * 2004-09-22-14:43:29.586 jh-server08 [2079] (Server) ps2pdf: Start_worker: pid 2080 * 2004-09-22-14:43:29.586 jh-server08 [2079] (Server) ps2pdf: Do_queue_jobs: MAIN LOOP 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) ps2pdf: Select_pc_info: looking for 'ps2pdf', depth 0 * 2004-09-22-14:43:29.586 jh-server08 [2079] (Server) ps2pdf: Do_queue_jobs: Susr1 before scan 0, check_for_done 1 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) ps2pdf: Find_pc_info:
LPRng: too many errors, only workers here
I have found strange behavior of LPRng working together with a perl/ghostscript ps2pdf script. This combination worked in the past (RH 7.2 - 8.0) without difficulties but since RedHat dropped LPRng from the distrib-CDs, my trio sometimes -not predictable - comes out on strike. After a reboot it works again (same client, same printjob, etc) -- environment different hardware = P2 266 Compaq Proliant / Dual Xeon 3,0 GHz Tarox Intel Servers (all with RAID) OS = Fedora FC1 / FC2 (2.6.8-1) rpmbuild LPRng, SPEC without modification = ftp://ftp.lprng.com/pub/LPRng/LPRng/LPRng-3.8.27-1.src.rpm XP Client = LPR Port, with HP ColorLaserJet 5 / Lexmark Optra Color 1200 PS printcap= .. ps2pdf|PDF-Server:\ :bk:sh:mx#0:ml#0:\ :lp=/dev/null:\ :lpd_bounce=true:\ :sd=/var/spool/lpd/ps2pdf:\ :if=/usr/local/bin/ps2pdf/pdfmail.pl: -- how it happens The Client prints as usually his request to the PDF-Printer (HP/Lexmark) via LPR to the LPRng Server. LPRng invokes the perl script and nothing else happens, no result, nothing. The 'lpq -c -n5 -Pps2pdf' shows me the following result: Printer: [EMAIL PROTECTED] 'PDF-Server' Queue: no printable jobs in queue Server: no server active Status: finished '[EMAIL PROTECTED]', status 'JFAIL' at 11:52:53.559 Status: job '[EMAIL PROTECTED]', attempt 3, allowed 3 at 11:52:53.579 Status: send_failure_action 'JREMOVE' at 11:52:53.580 Status: job '[EMAIL PROTECTED]', removing job - status JREMOVE at 11:52:53.581 Status: job '[EMAIL PROTECTED]' saved at 11:52:53.587 Rank Owner/ID Pr/Class Job Files Size Time error [EMAIL PROTECTED] A 6 ERROR: too many errors The hereby created spool-file (dfA005SBIV0302-34) runs without errors through the filterscript. # cat dfA005SBIV0302-34 | /usr/local/bin/ps2pdf/pdfmail.pl #job 15 at 2004-09-16 11:39 (errorlevel=0) Very very strange is, that from now on, there is no way out to get a PDF File out from LPRng. Every job is aborted/killed with too many errors ! The Page which was printed, can be as simple as it could be (eg. notepad test) I tried rm -f /var/spool/lpd/ps2pdf/* /usr/sbin/checkpc -f /sbin/service lpd restart print again the same simple page - same result. Only a reboot of the whole server solves the problem. I reboot the linux server and print the same page through the same Printer (hundred times) - OK. -- digging in the logs I took a closer look at the logfiles and compared the one when LPRng reports me a too many error failure and the logfile (printing the same document) after a reboot (restarting lpd is not sufficient) As you can see, the Server process did not start (wonder why) in the faulty print job. I miss the (Server) ps2pdf: Start_worker (Server) ps2pdf: Do_queue_jobs: MAIN LOOP (Server) ps2pdf: Do_queue_jobs: Susr1 before lines which I marked with an asterik in the log of the working job. Can anyone explain me that phenomenon / reason for that behavior ? logfile of the working job AFTER reboot .. 2004-09-22-14:43:29.586 jh-server08 [2080] LPD_CALL ps2pdf: Make_lpd_call: fd 2 - 2 2004-09-22-14:43:29.586 jh-server08 [2080] LPD_CALL ps2pdf: Make_lpd_call: fd 3 - 3 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) ps2pdf: Service_worker: begin 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) ps2pdf: Fix_Rm_Rp_info: printer name 'ps2pdf' 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) Reset_config: starting * 2004-09-22-14:43:29.586 jh-server08 [2079] (Server) ps2pdf: Start_worker: pid 2080 * 2004-09-22-14:43:29.586 jh-server08 [2079] (Server) ps2pdf: Do_queue_jobs: MAIN LOOP 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) ps2pdf: Select_pc_info: looking for 'ps2pdf', depth 0 * 2004-09-22-14:43:29.586 jh-server08 [2079] (Server) ps2pdf: Do_queue_jobs: Susr1 before scan 0, check_for_done 1 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) ps2pdf: Find_pc_info: found name 'ps2pdf' * 2004-09-22-14:43:29.586 jh-server08 [2079] (Server) ps2pdf: Get_hold_file: checking on 'hfA022' 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) ps2pdf: Select_pc_info: returning 'ps2pdf' 2004-09-22-14:43:29.586 jh-server08 [2080] (Worker) ps2pdf: Fix_Rm_Rp_info: found 'ps2pdf' .. long too many error-logfile BEFORE reboot ~~~ ... 2004-09-22-12:59:36.422 jh-server08 [3808] LPD_CALL ps2pdf: Make_lpd_call: fd 2 - 2 2004-09-22-12:59:36.422 jh-server08 [3808] LPD_CALL ps2pdf: Make_lpd_call: fd 3 - 3 2004-09-22-12:59:36.422 jh-server08 [3808] (Worker) ps2pdf: Service_worker: begin 2004-09-22-12:59:36.422 jh-server08 [3808] (Worker) ps2pdf: Fix_Rm_Rp_info: printer name 'ps2pdf' 2004-09-22-12:59:36.422 jh-server08 [3808] (Worker) Reset_config: starting 2004-09-22-12:59:36.422 jh-server08 [3808] (Worker) ps2pdf: Select_pc_info: looking for 'ps2pdf', depth 0
