![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to 7.t CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / share / doc / smm / 06.lpd|
Return to 7.t CVS log | Up to [CSRG BSD Unix] / 43BSDReno / share / doc / smm / 06.lpd |
1.1 root 1: .\" Copyright (c) 1983 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted
5: .\" provided that the above copyright notice and this paragraph are
6: .\" duplicated in all such forms and that any documentation,
7: .\" advertising materials, and other materials related to such
8: .\" distribution and use acknowledge that the software was developed
9: .\" by the University of California, Berkeley. The name of the
10: .\" University may not be used to endorse or promote products derived
11: .\" from this software without specific prior written permission.
12: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
13: .\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
14: .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
15: .\"
16: .\" @(#)7.t 6.5 (Berkeley) 3/7/89
17: .\"
18: .NH 1
19: Troubleshooting
20: .PP
21: There are several messages that may be generated by the
22: the line printer system. This section
23: categorizes the most common and explains the cause
24: for their generation. Where the message implies a failure,
25: directions are given to remedy the problem.
26: .PP
27: In the examples below, the name
28: .I printer
29: is the name of the printer from the
30: .I printcap
31: database.
32: .NH 2
33: LPR
34: .SH
35: lpr: \fIprinter\fP\|: unknown printer
36: .IP
37: The
38: .I printer
39: was not found in the
40: .I printcap
41: database. Usually this is a typing mistake; however, it may indicate
42: a missing or incorrect entry in the /etc/printcap file.
43: .SH
44: lpr: \fIprinter\fP\|: jobs queued, but cannot start daemon.
45: .IP
46: The connection to
47: .I lpd
48: on the local machine failed.
49: This usually means the printer server started at
50: boot time has died or is hung. Check the local socket
51: /dev/printer to be sure it still exists (if it does not exist,
52: there is no
53: .I lpd
54: process running).
55: Usually it is enough to get a super-user to type the following to
56: restart
57: .IR lpd .
58: .DS
59: % /usr/lib/lpd
60: .DE
61: You can also check the state of the master printer daemon with the following.
62: .DS
63: % ps l`cat /usr/spool/lpd.lock`
64: .DE
65: .IP
66: Another possibility is that the
67: .I lpr
68: program is not set-user-id to \fIroot\fP, set-group-id to group \fIdaemon\fP.
69: This can be checked with
70: .DS
71: % ls \-lg /usr/ucb/lpr
72: .DE
73: .SH
74: lpr: \fIprinter\fP\|: printer queue is disabled
75: .IP
76: This means the queue was turned off with
77: .DS
78: % lpc disable \fIprinter\fP
79: .DE
80: to prevent
81: .I lpr
82: from putting files in the queue. This is normally
83: done by the system manager when a printer is
84: going to be down for a long time. The
85: printer can be turned back on by a super-user with
86: .IR lpc .
87: .NH 2
88: LPQ
89: .SH
90: waiting for \fIprinter\fP to become ready (offline ?)
91: .IP
92: The printer device could not be opened by the daemon.
93: This can happen for several reasons,
94: the most common is that the printer is turned off-line.
95: This message can also be generated if the printer is out
96: of paper, the paper is jammed, etc.
97: The actual reason is dependent on the meaning
98: of error codes returned by system device driver.
99: Not all printers supply enough information
100: to distinguish when a printer is off-line or having
101: trouble (e.g. a printer connected through a serial line).
102: Another possible cause of this message is
103: some other process, such as an output filter,
104: has an exclusive open on the device. Your only recourse
105: here is to kill off the offending program(s) and
106: restart the printer with
107: .IR lpc .
108: .SH
109: \fIprinter\fP is ready and printing
110: .IP
111: The
112: .I lpq
113: program checks to see if a daemon process exists for
114: .I printer
115: and prints the file \fIstatus\fP located in the spooling directory.
116: If the daemon is hung, a super user can use
117: .I lpc
118: to abort the current daemon and start a new one.
119: .SH
120: waiting for \fIhost\fP to come up
121: .IP
122: This implies there is a daemon trying to connect to the remote
123: machine named
124: .I host
125: to send the files in the local queue.
126: If the remote machine is up,
127: .I lpd
128: on the remote machine is probably dead or
129: hung and should be restarted as mentioned for
130: .IR lpr .
131: .SH
132: sending to \fIhost\fP
133: .IP
134: The files should be in the process of being transferred to the remote
135: .IR host .
136: If not, the local daemon should be aborted and started with
137: .IR lpc .
138: .SH
139: Warning: \fIprinter\fP is down
140: .IP
141: The printer has been marked as being unavailable with
142: .IR lpc .
143: .SH
144: Warning: no daemon present
145: .IP
146: The \fIlpd\fP process overseeing
147: the spooling queue, as specified in the ``lock'' file
148: in that directory, does not exist. This normally occurs
149: only when the daemon has unexpectedly died.
150: The error log file for the printer and the \fIsyslogd\fP logs
151: should be checked for a
152: diagnostic from the deceased process.
153: To restart an \fIlpd\fP, use
154: .DS
155: % lpc restart \fIprinter\fP
156: .DE
157: .SH
158: no space on remote; waiting for queue to drain
159: .IP
160: This implies that there is insufficient disk space on the remote.
161: If the file is large enough, there will never be enough space on
162: the remote (even after the queue on the remote is empty). The solution here
163: is to move the spooling queue or make more free space on the remote.
164: .NH 2
165: LPRM
166: .SH
167: lprm: \fIprinter\fP\|: cannot restart printer daemon
168: .IP
169: This case is the same as when
170: .I lpr
171: prints that the daemon cannot be started.
172: .NH 2
173: LPD
174: .PP
175: The
176: .I lpd
177: program can log many different messages using \fIsyslogd\fP\|(8).
178: Most of these messages are about files that can not
179: be opened and usually imply that the
180: .I printcap
181: file or the protection modes of the files are
182: incorrect. Files may also be inaccessible if people
183: manually manipulate the line printer system (i.e. they
184: bypass the
185: .I lpr
186: program).
187: .PP
188: In addition to messages generated by
189: .IR lpd ,
190: any of the filters that
191: .I lpd
192: spawns may log messages using \fIsyslogd\fP or to the error log file
193: (the file specified in the \fBlf\fP entry in \fIprintcap\fP\|).
194: .NH 2
195: LPC
196: .PP
197: .SH
198: couldn't start printer
199: .IP
200: This case is the same as when
201: .I lpr
202: reports that the daemon cannot be started.
203: .SH
204: cannot examine spool directory
205: .IP
206: Error messages beginning with ``cannot ...'' are usually because of
207: incorrect ownership or protection mode of the lock file, spooling
208: directory or the
209: .I lpc
210: program.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.