hmmm,
you got me at that point: I'm using a self made filter, but it worked
fine over the years with LPRng...
Nothing has changed in the printcap or the filter, I just updated LPRng
from 3.6.12 to 3.6.22 / 3.6.23 though I have to admit that my filter is
sending the job himself via hpnpn to the printer. Is the new version
waiting for a socket to be closed ? I know that it is not your fault /
problem but I would greatly appreciate any help for solving this...
thanks a lot
Christoph
3.6.23 produced the following in the debug modus:
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) pubps2:
setstatus: msg 'IF filter 'lpr2unisap' filter finished'
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) pubps2:
setstatus: msg 'pubps2: Read_write_timeout: readfd 8 closed'
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) (ERR) pubps2:
Read_write_timeout: readfd 8 closed
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) pubps2: cleanup:
signal No signal, Errorcode 33, exits 0
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) pubps2:
Killchildren: pid 26326, signal Interrupt, count 2
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) pubps2:
Killchildren: pid 26327, signal 'Interrupt'
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) pubps2:
Killchildren: pid 26349, signal 'Interrupt'
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) pubps2: ***
Dump_pinfo Killchildren - after - count 1 ***
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) pubps2: pid
26327
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) pubps2: *** done
***
2000-08-15-08:42:05 printsrv4 [26326] (Worker - Print) pubps2: cleanup:
done, exit(33)
2000-08-15-08:42:05 printsrv4 [26325] (Server) pubps2: plp_waitpid: pid
-1, options 64
2000-08-15-08:42:05 printsrv4 [26325] (Server) pubps2: plp_waitpid:
returned 26326, status exit status 33 (JABORT)
2000-08-15-08:42:05 printsrv4 [26325] (Server) pubps2:
Wait_for_subserver: pid 26326, status 'exit status 33 (JABORT)'
2000-08-15-08:42:05 printsrv4 [26325] (Server) pubps2:
Wait_for_subserver: pid 26326 final status JABORT
2000-08-15-08:42:05 printsrv4 [26325] (Server) pubps2: setstatus: msg
'subserver pid 26326 exit status 'JABORT''
2000-08-15-08:42:05 printsrv4 [26325] (Server) pubps2:
Wait_for_subserver: server pid 26326 for 'pubps2' for
'/usr/spool/lpd/request/pubps2/hfA324' finished
2000-08-15-08:42:05 printsrv4 [26325] (Server) pubps2: setmessage: msg
'EXITSTATUS JABORT'
2000-08-15-08:42:05 printsrv4 [26325] (Server) pubps2: Update_status:
again - status 'JABORT', id 'root@printsrv4+324', dest id '<NULL>'
2000-08-15-08:42:05 printsrv4 [26325] (Server) pubps2: setmessage: msg
'PROCESSSTATUS JABORT'
2000-08-15-08:42:05 printsrv4 [26325] (Server) pubps2: setstatus: msg
'job 'root@printsrv4+324' error 'aborting operations''
[EMAIL PROTECTED] schrieb:
>
> > From [EMAIL PROTECTED] Mon Aug 14 04:22:01 2000
> > Date: Mon, 14 Aug 2000 12:18:22 +0200
> > From: Christoph Beyer <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: LPRng: errormessage in status
> >
> > hi,
> >
> > there theems to be a little problem still in 3.6.22 and in 3.6.23:
> > I'm spooling on a SOLARIS 2.7 machine, everything works fine but the
> > status line of the lpq request says "Filter-status ... ABORT"
> >
> > The debug flag produced the following output:
> >
> > 2000-08-14-11:47:43 printsrv2 [26582] (Worker - Print) testp5:
> > Wait_for_pid: pid 26605 exit status 'exit status 0 (JSUCC)'
> > 2000-08-14-11:47:43 printsrv2 [26582] (Worker - Print) testp5:
> > Wait_for_pid: returning 'JSUCC', exit status 'exit status 0 (JSUCC)'
> > 2000-08-14-11:47:43 printsrv2 [26582] (Worker - Print) testp5:
> > setstatus: msg 'IF filter 'lpr2uni_failover' filter finished'
> > 2000-08-14-11:47:43 printsrv2 [26582] (Worker - Print) testp5:
> > setstatus: msg 'testp5: Read_write_timeout: readfd 8 closed'
> > 2000-08-14-11:47:43 printsrv2 [26582] (Worker - Print) (ERR) testp5:
> > Read_write_timeout: readfd 8 closed
> > 2000-08-14-11:47:43 printsrv2 [26582] (Worker - Print) testp5: cleanup:
> > signal No signal, Errorcode 33, exits 0
> > 2000-08-14-11:47:43 printsrv2 [26582] (Worker - Print) testp5:
> > Get_max_fd: returning 64
>
> ^^^^ This error message is not in LPRng-3.6.23. Please update
> to the latest version. I suspect you are running an older version.
>
> > 2000-08-14-11:47:43 printsrv2 [26582] (Worker - Print) testp5:
> > Killchildren: pid 26582, signal Interrupt, count 2
> >
> > Naturally the error status confuses a few customers so I had to 'fall
> > back' on an older version for a while...
> >
> > regards Christoph
>
> Patrick Powell Astart Technologies,
> [EMAIL PROTECTED] 9475 Chesapeake Drive, Suite D,
> Network and System San Diego, CA 92123
> Consulting 858-874-6543 FAX 858-279-8424
> LPRng - Print Spooler (http://www.astart.com)
>
> -----------------------------------------------------------------------------
> 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.
-----------------------------------------------------------------------------
