SUMMARY: lpsched failure

From: Richard Zinar (zinar@shannon.jpl.nasa.gov)
Date: Fri Jun 04 1999 - 20:33:58 CDT


  Sorry for the late summary - I received a few replies, but I
  ultimately decided to simply print the problem files from
  a Solaris 2.6 host, since there are several in the same NIS domain.

  The suggestions I received were:

  - From Dave Foster <foster@bial1.ucsd.edu>:

        Back out the suspected patch and see if the problem
        goes away.

  - From Robert Metcalf <robertm@bscg.com>:

        Use the HP JetAdmin software, since the printer in question
        was an HP network printer. [I was already using a fairly
        recent version of HPNP]

  - From Igor Schein <igor@txc.com>:

        Try looking at the PostScript file with GhostScript, and
        possibly try to edit the PostScript file to fix the problem code.

My original post:

   I installed the latest recommended patch cluster for Solaris 2.5.1
   on a set of machines last weekend. A user mentioned a couple
   of days later that she was unable to print a particular file
   which she had printed before the upgrade. I checked into it,
   and printing this file (a PostScript file) or any of several
   similar ones consistently causes lpsched and lpNet to crash,
   and require a manual restart. I am able to print some PostScript
   files and text files, so it's not like I can't print at all.

   I've tried printing the file on three machines which have this
   set of patches installed, and all cause the same failure, so it's
   pretty clear (to me anyway) that the patch installation is
   the culprit.

   The lpNet file contains the following:

   05/09 07:25:45 p 195 <none> Initialized & Polling.
   05/09 07:25:45 p 195 <none> build info: 12/04/98:08:00:56
   05/14 11:22:30 p 195 <none> ERROR: class=NonFatal, type=Internal,
                                 trace=(LpExecEvent), Broken lpExec pipe.
   05/14 11:22:30 p 195 <none> ERROR: class=Fatal, type=Internal,
                                 trace=(LpExecEvent), Cannot recover.
   05/14 11:22:30 p 195 <none> Abnormal process termination.

   I've tried doing:

            sh /etc/init.d/lp stop
            cd /var/spool/lp
            rm -rf fifos temp tmp requests SCHEDLOCK
            sh /etc/init.d/lp start

   and re-printing, but the same thing occurs.

   I am able to print the problem files from a Solaris 2.6 machine,
   by the way.

   If anyone has any troubleshooting suggestions, I'd like to
   hear from you. I already have the latest version of the
   lp patch (103959-09) installed.



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:20 CDT