Conference turris::digital_unix

8911.0. "spool hang with "tell no such node or DECdns objec"" by MDR01::CARRANZ (MCS Madrid) Thu Feb 20 1997 12:02

Hello out here,

I have a very particular problem into a customer:

	2*2100 with Digital Unix V3.2C
	ASEBASE125
	DNAxxxx320
	PWKxxxx510

From time to time when they print a job, the job is printing, but its spool 
is locked because in the directory spool:

	/usr/spool/lpd?? ----> cfA#hostname (the dfA#hostname isn't)
	/usr/spool/lpd?? ----> into status file appears (something doesn't
    go OK):

	"Wed Feb 19 14:20:29 1997: Notifying user"

	/usr/spool/lpd?? ----> lock file (continue with the same file):
	
	Pid
	Job name

	/var/adm/lp??err ---> "tell, No such node or DECdns object"

The "# lpq -Pprinter" shows the spool trying to print this job, but that
    job has 0 bytes.
    
    The only way to solve the problem is removint it from that queue
    (lprm).

It happens with lat configured printers and tcp/ip printers, any file type 
(ascii,ps) lock printer.

It's printcap entry looks:
#
# Impresora Remota Xerox 3700 (Planta 15-Gesbansander)
#
lpd5|5-R159
        :af=/usr/adm/lp5acct:\
        :br#9600:\
        :ct=LAT:\
        :lf=/usr/adm/lp5err:\
        :lp=/dev/lat/622:\
        :mx#0:\
        :of=/usr/lbin/xf:\
        :op=PORT_4:\
        :pl#66:\
        :pw#132:\
        :sd:/usr/spool/lpd5:\
        :sh:\
        :ts=SVR700:\
#
3-product|13|lpd13
        :af=/usr/adm/lp13acct:\
        :br#19200:\
        :ct=LAT:\
        :fc#0177777:\
        :fs#023:\
        :lf=/usr/adm/lp13err:\
        :lp=/dev/lsy/630:\
        :mx#0:\
        :of=/usr/lbin/xf:\
        :op=PORT_1:\
        :pl#66:\
        :pw#132:\
        :sd=/usr/spool/lpd13:\
        :ct=LAT:\
        :fc#0177777:\
        :fs#023:\
        :sh:\
        :ts=LATPR6:\
        :xc#0177777:\
        :xf=/usr/lbin/xf:\
        :xs#044000:\

The problem occurs into lat printers and tcp/ip configured printers.

Any other conexion goes OK (pathworks).

I can't post here the "/var/adm/syslog.dated/date/lpr.log", because i haven't
them here at the moment.

I am waiting customer boot without decnet to define more closely our problem, 
but in order to gain time i'm posting this note into Digital_unix & decnet 
conference.

I think it looks like a decnet resolver problem, but i don't know decnet so 
any suggestion would be very appreciate.

I think it looks like a decnet resolution problem, does anybody knows how 
define more closely it.


Thanks in advance, again any help would ve quite appreciate,

Carmen Arranz

    I forgotted to point it, this note has been posted into dnu_osi
        & digital_unix conference.
    
        Does anybody know/any suggestion to look for?
    
        Thanks,
    
        Carmen.