I am seeing the exact same 'status buffer overflow' messages and
occasional pauses until a timeout from my HP Laser Jet 4SiMX. I don't
believe that the two are necessarily related to one another, though. I
cut back the time delay between print jobs that stall out by changing
the ifhp.conf value of waitend_interval to 120, which has shortened the
delays to about (stunningly enough) two minutes.

I have begun to attribute these problems to the fact that it is an old
and crufty printer model. However, just in case anyone is interested
(likely Patrick or Justus), I have here a status log (the first two
lines of which are from my chooser script) and, below that, the
status.b095 log of a print job that contained quite a few instances of
this message:

 Filter_status: Checking status of printer at Fri Aug 11 13:12:32 2000
 Filter_status: Printer b095.mitre.org found at Fri Aug 11 13:12:32 2000
 Filter_status: (of) using model 'DEFAULT' at 13:12:43.065
 Filter_status: (of) pagecount using 'pjl info pagecount' at
13:12:43.068
 Filter_status: (of) setting up printer at 13:12:43.068
 Filter_status: (of) starting OF mode passthrough at 13:12:43.101
 Filter_status: (of) getting sync using 'pjl echo' at 13:12:43.101
 Filter_status: (of) code = 30010, 'status buffer overflow' at
13:12:44.610
 Filter_status: (of) sync done at 13:12:45.067
 Filter_status: (of) pagecounter 1031087 at 13:12:45.068
 Filter_status: (of) pagecounter 1031087 at 13:12:45.068
 Filter_status: (of) getting sync using 'pjl echo' at 13:12:45.089
 Filter_status: (of) sync done at 13:12:47.110
 Filter_status: (of) sending 359 bytes of OF input at 13:12:47.111
 Filter_status: (of) starting transfer at 13:12:47.112
 Filter_status: (of) initial job type 'PJL' at 13:12:47.112
 Filter_status: (of) decoded job type 'PJL' at 13:12:47.112
 Filter_status: (of) job type 'PJL' at 13:12:47.113
 Filter_status: (of) transferring 359 bytes at 13:12:47.113
 Filter_status: (of) 100 percent done at 13:12:47.113
 Filter_status: (of) data sent at 13:12:47.114
 Filter_status: (of) OF process suspending at 13:12:47.114
 Filter_status: using model 'DEFAULT' at 13:12:47.170
 Filter_status: pagecount using 'pjl info pagecount' at 13:12:47.174
 Filter_status: setting up printer at 13:12:47.175
 Filter_status: getting sync using 'pjl echo' at 13:12:47.175
 Filter_status: sync done at 13:12:49.924
 Filter_status: pagecounter 1031087 at 13:12:49.925
 Filter_status: pagecounter 1031087 at 13:12:49.925
 Filter_status: sending job file at 13:12:49.926
 Filter_status: starting transfer at 13:12:49.926
 Filter_status: file program = '/usr/local/bin/file -' at 13:12:49.927
 Filter_status: started FILE_UTIL- '/usr/local/bin/file -' at
13:12:49.990
 Filter_status: file information = 'ascii_text' at 13:12:50.005
 Filter_status: initial job type 'ascii_text' at 13:12:50.005
 Filter_status: decoded job type 'PCL' at 13:12:50.006
 Filter_status: job type 'PCL' at 13:12:50.006
 Filter_status: transferring 1038 bytes at 13:12:50.008
 Filter_status: 100 percent done at 13:12:50.008
 Filter_status: data sent at 13:12:50.009
 Filter_status: sent job file at 13:12:50.009
 Filter_status: getting end using 'pjl job/eoj' at 13:12:50.010
 Filter_status: code = 30010, 'status buffer overflow' at 13:12:50.889
 Filter_status: code = 30010, 'status buffer overflow' at 13:12:54.640
 Filter_status: code = 30010, 'status buffer overflow' at 13:13:00.960
 Filter_status: code = 30010, 'status buffer overflow' at 13:13:04.651
 Filter_status: end of job detected at 13:13:08.850
 Filter_status: pagecounter 1031089 at 13:13:10.040
 Filter_status: pagecounter 1031089, pages 2 at 13:13:10.041
 Filter_status: done at 13:13:10.041
 Filter_status: (of) OF process running at 13:13:10.044
 Filter_status: (of) getting end using 'pjl job/eoj' at 13:13:10.058
 Filter_status: (of) end of job detected at 13:13:12.073
 Filter_status: (of) pagecounter 1031089 at 13:13:14.080
 Filter_status: (of) pagecounter 1031089, pages 2 at 13:13:14.081
 Filter_status: (of) ending OF mode passthrough at 13:13:14.095
 Filter_status: (of) done at 13:13:14.096

 Status: CHOOSER selected 'b095' at 13:12:32.726
 Status: subserver pid 10158 starting at 13:12:32.886
 Status: accounting at start at 13:12:32.886
 Status: opening device 'b095.mitre.org%9100' at 13:12:32.887
 Status: waiting for subserver to exit at 13:12:34.103
 Status: printing job 'smart@oraalpha+183' at 13:12:42.897
 Status: creating banner at 13:12:42.897
 Status: printing 'smart@oraalpha+183' starting OF 'ofhp' at
13:12:42.980
 Status: OF filter suspended at 13:12:47.116
 Status: processing 'dfA183oraalpha', size 1038, format 'f', IF filter
'ifhp' at 13:12:47.116
 Status: IF filter 'ifhp' filter finished at 13:13:10.043
 Status: OF filter finished at 13:13:14.098
 Status: printing finished at 13:13:14.098
 Status: accounting at end at 13:13:14.105
 Status: finished 'smart@oraalpha+183', status 'JSUCC' at 13:13:14.105
 Status: subserver pid 10158 exit status 'JSUCC' at 13:13:14.161
 Status: [EMAIL PROTECTED]: job 'smart@oraalpha+183' printed at
13:13:14.162
 Status: job 'smart@oraalpha+183' removed at 13:13:14.255

If anyone wants me to dig out a little bit more info or do some debug
logging, let me know and I can try to arrange something.
-- 
                        Bill Knox
                        Senior Operating Systems Programmer/Analyst
                        The MITRE Corporation

[EMAIL PROTECTED] wrote:
> 
[portion of mesage in which I am less interested deleted]
> 
> >
> > 2) On my HPIVsi I often have a problem where a job prints but ifhp hangs out
> > afterward waiting for the page count status to come back. It misses (or it is
> > never sent) the feedback from the printer and has to time out. The lpq command
> > often returns "code = 30010, 'status buffer overflow'" when this condition
> > happens. On the next attempt to get status it's successful and printing
> > continues. The printercap is:
> 
> We are seeing a horrible problem between the TCP/IP support,  the
> PostScript Engine, and status reporting.
> 
> After the job is sent to the printer,  and the status reporting is
> enabled in PostScript mode,  the ifhp filter periodically sends out
> a ^T (Control T) to prompt the printer to give it status.  It also
> sends a job that would cause it to send back job status.  Unfortunately,
> these do not get processed until all of the current job is done.
> 
> Then,  in a fit of passion,  the PostScript interpreter tries to generate
> all of the output and send it.  Thus,  we have 'status buffer overflow'.
> Now,  I am puzzled why it is getting buffer overflow.  Usually this happens
> only when LOTS and LOTS of time is taken by the job.
> 
> >
> > It's annoying to have to wait for the timeouts between jobs. It doesn't happen
> > all the time but it's frequent enough, especially on small jobs, to be a pain.
> > Any ideas?
> >
> > - Justus
> 
> -----------------------------------------------------------------------------
> 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.
-----------------------------------------------------------------------------

Reply via email to