Home Products Support About SD Contact SD

dot

JAGUAR FAQs

Printer Issues

Some printer problems are not hardware related but system software related. Usually, the symptoms are merely that the operator complains that "the printer used to work, but now, no printed plots come out"

The following pages are an attempt to distribute some fixes in case you have these problems in the future. I have arranged these problems and fixes in a rough order that you should use to correct the printer problem. It is also a rough order of potential damage to system files, if you are not careful.

At the end of each fix, check the printer operation by pressing the 'Print' button in any of our applications.
  1. Things to try first:
    • Unplug the printer from the power outlet, wait 15 seconds and plug it back in, leaving the data cable connected. During power-up, the printer may check for a connected parallel port. If the printer cable was connected after the power was already on, the benefit of this power-up test does not occur.
    • Power OFF the Sun and then power it on. The Sun parallelport may be hung.
    • Check that the printer cable is plugged into the parallel port (identified by the "//" symbol) and not the serial port (identified by the "A" or "B" symbol).
    • Check that the 'Print Command' window contains entries for 'Text:' as "lp -o nobanner", 'B/W Graphics:' as "default_printer" and 'Color Graphics:' as "default_printer".
    • Reset the 'Print Command' window Graphics Position to the original settings of: X1=0.5, Y1=0.5 and X2=8, Y2=10.5.
    • Enter the command 'lpstat' or 'lpstat -o' in an XTerm window to determine if there are any jobs in the print queue. If there are, the request-id is in the form 'lp-190'. You can cancel the jobs with the command 'cancel <request-id>' where <request-id> was found from the 'lpstat' command. (% cancel lp-190)
    • Check for 'file system full'. The command '% df -k' will show the disk capacity remaining. Delete files if greater than 95% full since print jobs require creation of temporary files.
    • Delete the problem printer using 'admintool', then add a new printer with the same settings..

  2. The Print Scheduler, a daemon called 'lpsched' which waits for and schedules print requests, has terminated unexpectedly.

    Fix: Start the print scheduler

    In an XTerm window, enter the following commands:

      % su
      # ps -ef | grep lpsched
      (see if the print scheduler is alive)
      root xxxx ..... grep lpsched (only one line shows missing 'lpsched' process)
      # /usr/lib/lpsched (start the print scheduler)
      Print service started
      # ps -ef | grep lpsched
      (see if the print scheduler is alive)
      root xxxx ..... /usr/lib/lpsched (two lines, print scheduler is alive)
      root xxxx ..... grep lpsched
      #

  3. The print scheduler always terminates when started, as above, because of a print queue problem that generates a 'Signal 11'.

    Fix: Delete all print jobs in the print queue.

    In an XTerm window, enter the following commands:

      % su
      # more /var/lp/logs/lpsched
      (look at the log of print scheduler messages)

      00:00:00 Jan 01 Print services started
      00:00:00 Jan 01 Received unexpected signal 11: terminating
      # cd /var/spool/lp/requests
      (this is the print request directory)
      # ls (look for hosts with a printer)
      SD255X (host names that have a printer attached)

      # cd SD255X (enter the queue for the host that has the problem)
      # ls (look for print jobs)
      190-0 190-1 (these are the print requests seen in the 'lpstat' command)
      # rm * (remove all print requests)
      # cd ../../tmp/SD255X (this is the shadow directory)
      # rm * (remove shadow requests, too)
      #


  4. The print queue is hopelessly corrupted and 'admintool' cannot delete a printer.
    Fix: Delete the current print queue and create another.


      % su
      # lpshut
      (stop print scheduler)
      Print services stopped
      # cd /var/spool
      (directory containing print queue)
      # mv lp lp.orig (rename the print queue)
      # /usr/lib/lpsched (start print scheduler to rebuild a new print queue)
      Print services started<
      #

    Delete the problem printer using the 'admintool' utility.
    Add a new local printer using the 'admintool' utility.

  5. The printer definitions are hopelessly corrupted and 'admintool' cannot delete a printer.
    Fix: Delete the current printer definitions.

      % su
      # cd /etc/lp/printers
      (here are the defined printers)
      # ls (look for printers)
      hp lp ps (these directories contain printer information)
      # cd lp (lp is a printer definition directory)
      # ls
      comment configuration users.deny
      (printer definition files)
      # rm * (delete definitions)
      # cd .. (go up one level)
      # rmdir lp (delete directory)
      # cd ../interfaces (here are more definitions to be deleted)
      # ls
      lp
      # cd lp
      # rm *
      # cd ..
      # rmdir lp
      #

    Delete the problem printer using the 'admintool' utility.
    Add a new local printer using the 'admintool' utility.

dot

Spectral Dynamics, Inc. 2730 Orchard Parkway, San Jose CA 95134-2012, tel: 408-678-3500, fax: 408-678-3580