I posted a summary of answers to an unsolved question. I suspect that
because I posted it on the eve of July 4th, the number of replies I got
was greatly diminished. So, in my summary, I again requested help. I got
what looks like an answer this time -- We don't have the patch listed
installed.
Thanks to:
"Mark A. Baldwin" <baldma@aur.alcatel.com>
Cathy Hargrave <cathy@mercury.stm.com>
"Ing. Erick Cedeņo" <erickc@sonitel.com>
Their replies follow the original.
---- ORIGINAL QUESTION ----
> We're running several workstations at various patched levels of Solaris
> 2.5 (kernel version ...-03 & ...-08 on the machines we're having trouble
> with).
>
> We have a HP 4m+ hooked up to the network, and we aren't using the
> JetDirect software, but are using the lpr support that is built into the
> printer. Here is the setup script we use to enable the printer for
> a particular machine:
>
> cp /cs1/solaris2/files/filter.table /etc/lp/filter.table
> chown lp:lp /etc/lp/filter.table
>
> lpsystem -t bsd hplj4m
> lpadmin -p hp4m -s hplj4m -T PS -I postscript
> enable hp4m
> accept hp4m
>
> This will work, but occasionally we find that lpsched dies or quits
> responding. It quit the other day on our SS5 (Solaris 2.5) a couple of
> minutes after reboot. Here are some log messages from /var/lp/logs/lpNet:
>
> 07/02 17:28:19 p 170 <none> Starting lpNetParent.
> 07/02 17:28:19 p 170 <none> Initialized & Polling.
> 07/02 17:28:19 p 170 <none> build info: 01/17/97:11:40:05
> 07/02 17:28:24 p 170 <none> Started child for hplj4m, pid = 193
> 07/02 17:28:36 p 170 <none> ERROR: class=NonFatal, type=Internal,
> trace=(LpExecEvent), Broken lpExec pipe.
> 07/02 17:28:36 p 170 <none> ERROR: class=Fatal, type=Internal,
> trace=(LpExecEvent), Cannot recover.
> 07/02 17:28:36 p 170 <none> Abnormal process termination.
>
> Similar messages show up on other machines that lpsched has died on.
>
> Can anyone help me identify the problem? It looks like either the HP or
> the Sun box is cutting the connection off short (the HP probably?) -- does
> this indicate that we should stick with the JetDirect software? Anybody
> out there got an idea of what is happening?
Additional Info:
We have an HP 5m that is hooked up to the network similarly, and
it doesn't exhibit the same problems.
---- END ORIGINAL ----
From: "Mark A. Baldwin" <baldma@aur.alcatel.com>
Subject: Re: SUMMARY: Re: HP LaserJet 4M+ and lpr
I would be willing to bet that one of 2 things is causing this:
1. Make sure you have patch 103959-03 installed.
2. Make sure you do not have a printer defined that does not actually
exist. Look in /etc/lp/printers. If you see a printer defined that doesn't
exist, remove it. Then do /etc/init.d/lp stop. Then remove
/var/spool/lp/tmp, /var/spool/lp/temp, and /var/spool/lp/requests. Then run
/etc/init.d/lp start.
-----------
From: Cathy Hargrave <cathy@mercury.stm.com>
Subject: Re: SUMMARY: Re: HP LaserJet 4M+ and lpr
i recently had to deal with something similar for a print
server for an hp laserjet 4 with jetdirect admin installed.
it turned out that once i cleaned out the directories on a
print client, in /var/spool/lp/tmp, the problem went away.
our printer is configured only for postscript. the client
was trying to send ascii files. however, before we got to
that point, we could not keep the lpsched running at all.
to get it up i installed sun's 2.5 recommended patch cluster
on the print server. there are 2 patches for lp in the
cluster. the whole thing was a mess from beginning to end
with lots of people doing different things. i don't know if
the patches were necessary.
----------
From: "Ing. Erick Cedeņo" <erickc@sonitel.com>
Subject: RE: SUMMARY: Re: HP LaserJet 4M+ and lpr
Patch-ID# 102964-06 is supposed to solve a lot of causes of lpsched hangs.
I guess that when you said "various patched levels" you included this
patch. If not, give it a try.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:59 CDT