did you try different prots e.g. 515 ???


On Thu, 17 Jan 2002, Carl Riches wrote:

> On Thu, 17 Jan 2002 [EMAIL PROTECTED] wrote:
>
> > hmmm,
> >
> > no further ideas from my side, you can run the lpd in debug mode of cause
> > ...
> >
>
> Did that, no clues.  This is a puzzler, all right.  I can show (via
> netstat) that a connection is made to the printer.  I am going to use
> tcpdump to determine if any network traffic occurs, but I don't think that
> happens.  The printer doesn't come out of sleep mode when one of these
> connections is made.
>
> Carl
>
> >
> >
> > On Tue, 15 Jan 2002, Carl Riches wrote:
> >
> > > On Mon, 14 Jan 2002 [EMAIL PROTECTED] wrote:
> > >
> > > > hi,
> > > >
> > > > well this looks much like an IFHP problem, did you ever run it in debug
> > > > mode ?
> > > >
> > > > When you stop the queue and run the file tool on the datafile, what does
> > > > it say?
> > > >
> > > >
> > >
> > > Actually, it is a communication problem between the printing system (LPRng
> > > and IFHP) and the network printer.  Data files in the spool queues are
> > > "ASCII English text" or "PostScript document text conforming at level 3.0"
> > > and so forth.  If I change the "lp" device in the printcap entry from a
> > > network printer to a disk file, the print job ends up in the disk file
> > > just fine.  Here are the tests that I've run, each with IFHP version
> > > 3.1.15 and version 3.5.0:
> > >
> > > On print server computer:
> > >   - set up printcap file with _no_ filter, lp=printer%9100; jobs print
> > >   - set up printcap file with IFHP filter, lp=printer%9100; jobs hang
> > >   - set up printcap file with _no_ filter, lp=/tmp/out; jobs print
> > >   - set up printcap file with IFHP filter, lp=/tmp/out; jobs print
> > >
> > > On client computer(s):
> > >   - turn on lpd
> > >   - set up printcap file with _no_ filter, lp=printer%9100; jobs print
> > >   - set up printcap file with IFHP filter, lp=printer%9100; jobs print
> > >   - set up printcap file with _no_ filter, lp=/tmp/out; jobs print
> > >   - set up printcap file with IFHP filter, lp=/tmp/out; jobs print
> > >
> > > I have just run another test.  I set up a bounce queue to filter the print
> > > job, which then gets fed to a print queue with no filtering, just a
> > > printer device.  Files which go to through the bounce queue end up in the
> > > spool directory for the second print queue all nicely massaged by IFHP
> > > (PJL headers, printer LCD display message, etc.).  The "file" command
> > > reports that all of them are  "HP Printer Job Language data".  There is
> > > some underlying communications problem.
> > >
> > > The only obvious difference between the server machine and the client
> > > machines is the hardware.  The server is a Compaq DS20 (Alpha EV6 CPU).
> > > The clients are Digital AlphaStation 600 (Alpha EV5), Digital AlphaServer
> > > 800 (Alpha EV5) and Compaq DS10 (Alpha EV6) machines.  All are running the
> > > same version of the OS: Compaq Tru64 Unix 5.1a.
> > >
> > > How can I debug what is happening here?
> > >
> > > Thanks,
> > > Carl
> > >
> > > >
> > > >
> > > > On Fri, 11 Jan 2002, Carl Riches wrote:
> > > >
> > > > > On Fri, 11 Jan 2002 [EMAIL PROTECTED] wrote:
> > > > >
> > > > > > hi,
> > > > > >
> > > > > > the output of 'lpq -L' might be useful...
> > > > > >
> > > > >
> > > > > Before continuing, I should add that printing to a disk file on the
> > > > > problem server works just fine--it is just printing to a network printer.
> > > > >
> > > > > I'm not sure if this will tell you much, but here is the output of
> > > > > "lpq -L -v":
> > > > >
> > > > > Printer: test@entropy
> > > > >  Job: riches@entropy+471 Comment: test queue running on HP LaserJet 4000TN 
>in C-28 Padelford
> > > > >  Printing: no
> > > > >  Aborted: no
> > > > >  Spooling: no
> > > > >  Queue: 1 printable job
> > > > >  Server: pid 9473 active,  Unspooler: pid 9467 active
> > > > >  SPOOLCONTROL=
> > > > >  Status: waiting for subserver to exit at 13:22:43.600
> > > > >  Status: subserver pid 425975 starting at 13:22:43.815
> > > > >  Status: accounting at start at 13:22:43.818
> > > > >  Status: opening device 'ent%9100' at 13:22:43.825
> > > > >  Status: printing job 'riches@entropy+983' at 13:22:43.841
> > > > >  Status: processing 'dfA983entropy.ms.washington.edu', size 1939, format 
>'f', IF filter 'ifhp' at 13:22:43.853
> > > > >  Status: subserver pid 425975 exit status 'JFAIL' at 13:24:26.994
> > > > >  Status: subserver pid 9467 starting at 09:12:09.998
> > > > >  Status: waiting for subserver to exit at 09:12:10.005
> > > > >  Status: accounting at start at 09:12:10.010
> > > > >  Status: opening device 'ent%9100' at 09:12:10.017
> > > > >  Status: printing job 'riches@entropy+471' at 09:12:10.025
> > > > >  Status: processing 'dfA471entropy.ms.washington.edu', size 1939, format 
>'f', IF filter 'ifhp' at 09:12:10.037
> > > > >  Job: riches@entropy+471 status= stalled(465sec)
> > > > >  Job: riches@entropy+471 size= 1939
> > > > >  Job: riches@entropy+471 time= 0x3c3f1ce9
> > > > >  Job: riches@entropy+471 CONTROL=
> > > > > Ariches@entropy+471
> > > > > CA
> > > > > D2002-01-11-09:12:09.465
> > > > > Hentropy.ms.washington.edu
> > > > > J/etc/hosts
> > > > > Priches
> > > > > Qtest
> > > > > N/etc/hosts
> > > > > fdfA471entropy.ms.washington.edu
> > > > > UdfA471entropy.ms.washington.edu
> > > > >
> > > > >  Job: riches@entropy+471 HOLDFILE=
> > > > >
> > > > > A=riches@entropy+471
> > > > > C=A
> > > > > D=2002-01-11-09:12:09.465
> > > > > datafile_count=1
> > > > > 
>datafiles=N/etc/hostsfdfA471entropy.ms.washington.eduUdfA471entropy.ms.washington.edu
> > > > > file_hostname=entropy.ms.washington.edu
> > > > > filenames=/etc/hosts
> > > > > H=entropy.ms.washington.edu
> > > > > held=0x0
> > > > > hf_name=hfA471
> > > > > hold_class=0x0
> > > > > hold_time=0x0
> > > > > J=/etc/hosts
> > > > > job_time=0x3c3f1ce9
> > > > > job_time_usec=0x67055
> > > > > number=471
> > > > > P=riches
> > > > > printable=0x1
> > > > > priority=A
> > > > > Q=test
> > > > > server=9467
> > > > > size=1939
> > > > > start_time=0x3c3f1ce9
> > > > > transfername=cfA471entropy.ms.washington.edu
> > > > > update_time=2002-01-11-09:12:09.987
> > > > >
> > > > > Carl
> > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, 10 Jan 2002, Carl Riches wrote:
> > > > > >
> > > > > > >
> > > > > > > We are having a problem with LPRng-3.8.1 and IFHP versions 3.1.15 and
> > > > > > > 3.5.0 when the lpd daemon is running on the server for one of our
> > > > > > > departments, a Compaq DS20 with Compaq Tru64 Unix 5.1a.  We do not have
> > > > > > > a problem if the daemon is running on the servers in our other 
>departments
> > > > > > > (DEC AlphaStation 600s running Compaq Tru64 Unix 5.1), nor do we have a
> > > > > > > problem if the daemon is running on one of our client machines (a mixture
> > > > > > > of DEC AlphaStation 600s, AS 800s and Compaq DS10s).
> > > > > > >
> > > > > > > Here are the symptoms:
> > > > > > >
> > > > > > > Printing hangs on the DS20 when the lpd server hands printing off to a
> > > > > > > filter.  Printing does not hang if no filters are defined (but then one
> > > > > > > can't filter the print job and get the print job to go onto the paper
> > > > > > > properly).
> > > > > > >
> > > > > > > Here are the lines put into the file "status.test" by a print request:
> > > > > > >
> > > > > > > waiting for subserver to exit at 2002-01-10-13:22:43.600 ## A=<NULL> 
>number=0 process=425988
> > > > > > > subserver pid 425975 starting at 2002-01-10-13:22:43.815 ## 
>A=riches@entropy+983 number=983 process=425975
> > > > > > > accounting at start at 2002-01-10-13:22:43.818 ## A=riches@entropy+983 
>number=983 process=425975
> > > > > > > opening device 'ent%9100' at 2002-01-10-13:22:43.825 ## 
>A=riches@entropy+983 number=983 process=425975
> > > > > > > printing job 'riches@entropy+983' at 2002-01-10-13:22:43.841 ## 
>A=riches@entropy+983 number=983 process=425975
> > > > > > > processing 'dfA983entropy.ms.washington.edu', size 1939, format 'f', IF 
>filter 'ifhp' at 2002-01-10-13:22:43.853 ## A=riches@entropy+983 number=983 
>process=425975
> > > > > > >
> > > > > > > At this point, the print job hangs with no activity on the printer.  The
> > > > > > > print queue must be cleared with the "lprm" command, which appends this 
>line
> > > > > > > to the file "status.test":
> > > > > > >
> > > > > > > subserver pid 425975 exit status 'JFAIL' at 2002-01-10-13:24:26.994 ## 
>A=<NULL> number=0 process=425988
> > > > > > >
> > > > > > > I can't figure out why this fails on this particular machine.  Has anyone
> > > > > > > run into this sort of problem in the past and can give me pointers on why
> > > > > > > this is breaking?
> > > > > > >
> > > > > > >
> > > > > > > Here is our printcap file (/usr/local/etc/printcap):
> > > > > > >
> > > > > > > # =======================================================================
> > > > > > > #
> > > > > > > # Printer:      test queue (Hewlett-Packard LaserJet 4000TN with 
>duplexer)
> > > > > > > # Location:     C-28 Padelford Hall
> > > > > > > # Connection:   TCP/IP
> > > > > > > #
> > > > > > > # Notes:
> > > > > > > #
> > > > > > > test:
> > > > > > >         :client
> > > > > > >         :lp=test@entropy
> > > > > > > test:
> > > > > > >         :server
> > > > > > >         :cm=test queue running on HP LaserJet 4000TN in C-28 Padelford
> > > > > > >         :lp=ent%9100
> > > > > > >         :ifhp=model=hp4000
> > > > > > >         :sd=/var/spool/test
> > > > > > >         :sh@
> > > > > > >         :sb@
> > > > > > >         :filter=/usr/local/libexec/filters/ifhp
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Thanks for your help,
> > > > > > > Carl
> > > > > > >
> > > > > > > Carl G. Riches
> > > > > > > Software Engineer
> > > > > > > Department of Mathematics
> > > > > > > Box 354350                        voice:     206-543-5082 or 206-616-3636
> > > > > > > University of Washington  fax:       206-543-0397
> > > > > > > Seattle, WA  98195-4350           internet:  [EMAIL PROTECTED]
> > > > > > >
> > > > > > >
>
>
> -----------------------------------------------------------------------------
> YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> The address you post from 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.  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.
> -----------------------------------------------------------------------------
>


-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from 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.  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