1 .\" Copyright (c) 1983, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)7.t 8.1 (Berkeley) 6/8/93
33 There are several messages that may be generated by the
34 the line printer system. This section
35 categorizes the most common and explains the cause
36 for their generation. Where the message implies a failure,
37 directions are given to remedy the problem.
39 In the examples below, the name
41 is the name of the printer from the
47 lpr: \fIprinter\fP\|: unknown printer
53 database. Usually this is a typing mistake; however, it may indicate
54 a missing or incorrect entry in the /etc/printcap file.
56 lpr: \fIprinter\fP\|: jobs queued, but cannot start daemon.
60 on the local machine failed.
61 This usually means the printer server started at
62 boot time has died or is hung. Check the local socket
63 /dev/printer to be sure it still exists (if it does not exist,
67 Usually it is enough to get a super-user to type the following to
73 You can also check the state of the master printer daemon with the following.
75 % ps l`cat /usr/spool/lpd.lock`
78 Another possibility is that the
80 program is not set-user-id to \fIroot\fP, set-group-id to group \fIdaemon\fP.
81 This can be checked with
83 % ls \-lg /usr/ucb/lpr
86 lpr: \fIprinter\fP\|: printer queue is disabled
88 This means the queue was turned off with
90 % lpc disable \fIprinter\fP
94 from putting files in the queue. This is normally
95 done by the system manager when a printer is
96 going to be down for a long time. The
97 printer can be turned back on by a super-user with
102 waiting for \fIprinter\fP to become ready (offline ?)
104 The printer device could not be opened by the daemon.
105 This can happen for several reasons,
106 the most common is that the printer is turned off-line.
107 This message can also be generated if the printer is out
108 of paper, the paper is jammed, etc.
109 The actual reason is dependent on the meaning
110 of error codes returned by system device driver.
111 Not all printers supply enough information
112 to distinguish when a printer is off-line or having
113 trouble (e.g. a printer connected through a serial line).
114 Another possible cause of this message is
115 some other process, such as an output filter,
116 has an exclusive open on the device. Your only recourse
117 here is to kill off the offending program(s) and
118 restart the printer with
121 \fIprinter\fP is ready and printing
125 program checks to see if a daemon process exists for
127 and prints the file \fIstatus\fP located in the spooling directory.
128 If the daemon is hung, a super user can use
130 to abort the current daemon and start a new one.
132 waiting for \fIhost\fP to come up
134 This implies there is a daemon trying to connect to the remote
137 to send the files in the local queue.
138 If the remote machine is up,
140 on the remote machine is probably dead or
141 hung and should be restarted as mentioned for
144 sending to \fIhost\fP
146 The files should be in the process of being transferred to the remote
148 If not, the local daemon should be aborted and started with
151 Warning: \fIprinter\fP is down
153 The printer has been marked as being unavailable with
156 Warning: no daemon present
158 The \fIlpd\fP process overseeing
159 the spooling queue, as specified in the ``lock'' file
160 in that directory, does not exist. This normally occurs
161 only when the daemon has unexpectedly died.
162 The error log file for the printer and the \fIsyslogd\fP logs
163 should be checked for a
164 diagnostic from the deceased process.
165 To restart an \fIlpd\fP, use
167 % lpc restart \fIprinter\fP
170 no space on remote; waiting for queue to drain
172 This implies that there is insufficient disk space on the remote.
173 If the file is large enough, there will never be enough space on
174 the remote (even after the queue on the remote is empty). The solution here
175 is to move the spooling queue or make more free space on the remote.
179 lprm: \fIprinter\fP\|: cannot restart printer daemon
181 This case is the same as when
183 prints that the daemon cannot be started.
189 program can log many different messages using \fIsyslogd\fP\|(8).
190 Most of these messages are about files that can not
191 be opened and usually imply that the
193 file or the protection modes of the files are
194 incorrect. Files may also be inaccessible if people
195 manually manipulate the line printer system (i.e. they
200 In addition to messages generated by
202 any of the filters that
204 spawns may log messages using \fIsyslogd\fP or to the error log file
205 (the file specified in the \fBlf\fP entry in \fIprintcap\fP\|).
210 couldn't start printer
212 This case is the same as when
214 reports that the daemon cannot be started.
216 cannot examine spool directory
218 Error messages beginning with ``cannot ...'' are usually because of
219 incorrect ownership or protection mode of the lock file, spooling