SUMMARY : LP error / Solaris 2.x

From: Xavier Cauchoix (xc@eurolang.fr)
Date: Thu Nov 21 1996 - 04:25:49 CST


First solution
1. check if lpsched is running
2. Yes lpshut, then lpsched
3. run lpsched

Second solution:
/etc/init.d/lp start

Also, you may need

        enable lptrad
        accept lptrad

Third solution:
kill -9 pid_lpshed
cd /var/spool/lp
rm -r tmp/*
rm -r requests/*
/usr/lib/lpsched

Thanks go to :

AO <cherub@lava.net>
Colin McNeill <colin@gtl.com>
gmp@adc.com (Gregory M Polanski)
Rasana Atreya <atreya@library.ucsf.edu>
john@tdi.com (John)
Marina.Daniels@ccd.tas.gov.au (Marina Daniels)
Christophe DIARRA <diarra@ipno.in2p3.fr>

-- 

Xavier

====================================================================== Xavier Cauchoix SysAdmin Eurolang (http://www.eurolang.fr) Maisons-Alfort FRANCE Tel : 33 (1) 45 13 05 38 Fax : 33 (1) 45 13 05 59 Email:xc@eurolang.fr

mail from Rasana Atreya ubject: Re: LP error / Solaris 2.x Date: Wed, 20 Nov 1996 10:51:07 -0800 From: Rasana Atreya <atreya@library.ucsf.edu> To: Xavier Cauchoix <xc@eurolang.fr>

Check the following document out:

SYNOPSIS: troubleshooting no output (nothing prints) DETAIL DESCRIPTION:

When user sets up a printer, trying for the first time to print a file, there may be no output, that is, nothing prints. How does user troubleshoot "No Output?" SOLUTION SUMMARY:

When nothing prints, there are three basic areas to check:

The printer hardware

The network

The LP print service

To check the hardware:

1. Check that the printer is plugged in and turned on.

2. Check that the cable is connected to the port on the printer and to the port on the workstation or server.

3. Check that the cable is the correct cable and that it is not defective. Refer to the manufacturer's documentation. If the printer is connected to a serial port, make sure that the cable supports hardware flow control. A NULL modem adapter supports this.

Pin Configuration for NULL Modem Cables

Host Printer

Mini-Din-8 25-Pin D-sub 25-Pin D-sub ----------------------------------------------------------------

- 1(FG) 1(FG)

3(TD) 2(TD) 3(RD)

5(RD) 3(RD) 2(TD)

6(RTS) 4(RTS) 5(CTS)

2(CTS) 5(CTS) 4(RTS)

4(SG) 7(SG) 7(SG)

7(DCD) 6(DSR), 8(DCD) 20(DTR)

1(DTR) 20(DTR) 6(DSR), 8(DCD)

----------------------------------------------------------------

4. Check that any hardware switches for the ports are set properly.

5. Check that the printer is operational.

Use the printer's self-test feature, if the printer has one. Check the printer documentation for information about printer self-testing.

6. Check that the baud settings for the computer and the printer are correct. If the baud settings are not the same for both the computer and the printer, sometimes nothing will print, but more often user gets incorrect output.

To check the network:

1. On a print client or server, type ping system-name and press Return. This command helps check that the network link between the print server and the print client is set up correctly.

If the message says that the system is alive, user can reach it, so the network is all right. It also tells user that either a naming service or the local /etc/hosts file has translated the host (system) name entered, into an IP address; otherwise, user has to enter the IP address.

If user gets a "not available" message, try to answer the following questions: How is NIS or NIS+ set up at the site? Does user need to take additional steps so that print servers and print clients can communicate with one another? If the site is not running NIS or NIS+, has user entered the IP address for the print server in each clients /etc/hosts file, and entered all print client IP addresses in the /etc/hosts file of the print server?

2. Check that the port monitor is configured correctly on the print server.

Type sacadm -l and press Return. The example below shows a print server that is configured correctly.

landshark 21: sacadm -l PMTAG PMTYPE FLGS RCNT STATUS COMMAND tcp listen - 9999 ENABLED /usr/lib/saf/listen tcp #

3. Check that the network listen services are registered with the port monitor on the print server.

Type pmadm -l and press Return. The example below shows a server that is configured for all three services.

landshark 20: pmadm -l PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC> tcp listen lp - root - - p - /var/spool/lp/fifos/listenS5 # tcp listen lpd - root \x00020203000000000000000000000000 - p - /var/spool/lp/fifos/listenBSD # tcp listen 0 - root \x00020ACE000000000000000000000000 - c - /usr/lib/saf/nlps_server #

To check the basic functions of the LP print service:

1. On both the print server and the print client, make sure that the LP print service is running.

a. Type lpstat -r and press Return. This command shows if the LP scheduler is running.

b. If the scheduler is not running, become root or lp, type /usr/lib/lp/lpsched and press Return.

2. On both the print server and the client, make sure that the printer is accepting requests.

a. Type lpstat -a and press Return. This command verifies that the LP system is accepting requests for each printer that is configured for the system.

b. If the printer is not accepting requests, become root or lp, type accept printer-name and press Return. The printer specified now accepts requests.

3. On both the print server and print client, make sure that the printer is enabled to print requests.

a. Type lpstat -p printer-name and press Return. Information about printer status is displayed. You can omit the printer name to obtain information about all printers set up for the system.

b. If the printer is disabled, become root or lp, type enable printer-name and press Return. The printer specified is enabled.

4. On the print server, make surethat the printer is connected to the correct serial port.

a. Type lpstat -t and press Return. This command tells user the port to which the printer is connected. The message "device for printer-name" shows the port address. Is the cable connected to the port to which the LP print service thinks it is connected? If the prot is correct, skip to step 5.

b. Become root or lp.

c. Type chown lp device-filename and press Return. This command assigns the special user lp as the owner of the device file.

d. Type chmod 600 device-filename and press Return. This command allows only lp (or root) to access the printer port device.

5. On both the print server and the print client, make sure that the printer is configured properly.

a. lpstat -p printer-name -l and press Return.

landshark 31: lpstat -p NeWSprinter20 -l printer NeWSprinter20 is idle. enabled since Mon Mar 28 14:51:58 PST 1994. available. Content types: any Printer types: unknown Description: in prphls area Users allowed: (all) Forms allowed: (none) Banner not required Character sets: (none) Default pitch: Default page size:

b. If the printer type or file content is incorrect, type lpadmin -p printer-name -T printer-type -I file-content-type and press Return. On a print client, try setting the print type to unknown and the content type to any.

6. On the print server, make sure that the printer is not waiting because of a fault.

a.Type lpadmin -p printer-name -F continue and press Return. You have instructed the LP print service to continue if it is waiting because of a fault.

b. Type enable printer-name and press Return. This command forces an immediate retry.

c. (Optional) Type lpadmin -p printer-name -A 'write root' and press Return. You have instructed the LP print service to set a default policy of writing root - sending the printer fault messages to the terminal on which root is logged in - if the printer fails. This may help to get quick notification of faults as user tries to fix the problem.

7. Make sure that the printer is not set up incorrectly as a login terminal.

----------------------------------------------------------------------------- NOTE - It is easy to mistakenly set up a printer as a login terminal. -----------------------------------------------------------------------------

a. Type ps -ef and press Return. Look for the printer port entry.In the example, port /dev/term/a is incorrectly set as a login terminal. You can tell by the "passwd\n## information at the end of the line. If the port is set up correctly, skip the last steps in this procedure.

# ps -ef

root 859 858 0 19:18:54 term/a 0:01 /bin/sh -c /etc/lp/interfaces/pinecone pinecone-294 bumpcity!fowler "passwd\n##

b. Type cancel request-id and press Return.

c. Type lpadmin -p printer-name -h and press Return. The printer port is set to be a non-login device.

d. Type ps -ef and press Return. Verify that the printer port is no longer a login device.

For additional information, refer to chapter 7 of the Solaris 2.3 Setting Up Accounts, Printers, and Mail manual #801-5281-10.

PATCH ID: n/a PRODUCT AREA: n/a PRODUCT: prphl SUNOS RELEASE: any UNBUNDLED RELEASE: n/a HARDWARE: n/a

---------------------------------------------------------------------------- Comments and suggestions?

Copyright 1994 Sun Microsystems, Inc. 2550 Garcia Ave., Mt. View, CA 94043-1100 USA. All rights reserved. Rasana

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ Rasana Atreya Voice: (415) 476-3623 ~ ~ System Administrator Fax: (415) 476-4653 ~ ~ Library & Ctr for Knowledge Mgnt, Univ. of California at San Francisco ~ ~ 530 Parnassus Ave, Box 0840, San Francisco, CA 94143-0840 ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:16 CDT