Now I'm going to see if I can answer my own question - is my active
connection by the if filter what is preventing the of filter from
getting in on some occasions, such that if I'm not doing banner printing
I should not have an of entry?
--
Bill Knox
Senior Operating Systems Programmer/Analyst
The MITRE Corporation
"William R. Knox" wrote:
>
> I have a Phaser 850 set up to print over the AppSocket port with
> IFHP-3.3.19 and LPRng-3.6.23. The printcap follows the current
> recommendation of letting IFHP make the connection to the 9100 port (see
> printcap entry below). However, it seems that IFHP can't handle a
> connection flakeout (to use the technical term) as well as LPRng can. I
> just had a print job suck up 25% of the CPU on an Sun Enterprise 250
> server (well, the CPU time was available, but still...) as it tried to
> reestablish the connection at a rate of once every millisecond or two.
> Here is a slice of the relevant log entries:
>
> Filter_status: (of) connect to '129.83.149.81 port 9100' failed -
> Connection refused at 13:05:45.691
> Filter_status: (of) connect to '129.83.149.81 port 9100' failed -
> Connection refused at 13:05:45.692
> Filter_status: (of) connect to '129.83.149.81 port 9100' failed -
> Connection refused at 13:05:45.694
> Filter_status: (of) connect to '129.83.149.81 port 9100' failed -
> Connection refused at 13:05:45.695
> Filter_status: (of) connect to '129.83.149.81 port 9100' failed -
> Connection refused at 13:05:45.697
>
> This went on for about twenty minutes as the printer, reporting via it's
> web interface, was first initializing and then cleaning.
>
> Is there anything that can be done to prevent this? I am already using a
> chooser script to make sure that the printer is up and listening on port
> 9100 before I release the job, so something must have happened to break
> the connection. But can IFHP be configured to step back in some way?
>
> Here is the printcap entry, in case you are interested:
>
> d275a|D275A:tc=.printsrv3-ip
> d275a|D275A:client:lpr_bounce:lp=d275a@localhost
> d275a|D275A:server:sh:if=/usr/local/etc/filters/ifhp
> -Tmodel=phaser,dev=d275a.mi
> tre.org%9100:of=/usr/local/etc/filters/ofhp
> -Tmodel=phaser,dev=d275a.mitre.org%9
> 100:lp=/var/spool/lpd/d275a/null
>
> .printsrv3-ip:\
> sd=/var/spool/lpd/%P:\
> chooser=/usr/local/eprint/bin/poll_printer.pl:\
> connect_grace=10:\
> network_connect_grace=10
>
> Thanks in advance.
> --
> Bill Knox
> Senior Operating Systems Programmer/Analyst
> The MITRE Corporation
>
> -----------------------------------------------------------------------------
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body. For the impatient,
> 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, send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> -----------------------------------------------------------------------------
-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
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, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
