/share/doc/smm/07.lpd/7.t

  1.\" Copyright (c) 1983, 1993
  2.\"	The Regents of the University of California.  All rights reserved.
  3.\"
  4.\" Redistribution and use in source and binary forms, with or without
  5.\" modification, are permitted provided that the following conditions
  6.\" are met:
  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. All advertising materials mentioning features or use of this software
 13.\"    must display the following acknowledgement:
 14.\"	This product includes software developed by the University of
 15.\"	California, Berkeley and its contributors.
 16.\" 4. Neither the name of the University nor the names of its contributors
 17.\"    may be used to endorse or promote products derived from this software
 18.\"    without specific prior written permission.
 19.\"
 20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 30.\" SUCH DAMAGE.
 31.\"
 32.\"	@(#)7.t	8.1 (Berkeley) 6/8/93
 33.\"
 34.NH 1
 35Troubleshooting
 36.PP
 37There are several messages that may be generated by the
 38the line printer system.  This section
 39categorizes the most common and explains the cause
 40for their generation.  Where the message implies a failure,
 41directions are given to remedy the problem.
 42.PP
 43In the examples below, the name
 44.I printer
 45is the name of the printer from the
 46.I printcap
 47database.
 48.NH 2
 49LPR
 50.SH
 51lpr: \fIprinter\fP\|: unknown printer
 52.IP
 53The
 54.I printer
 55was not found in the
 56.I printcap
 57database.  Usually this is a typing mistake; however, it may indicate
 58a missing or incorrect entry in the /etc/printcap file.
 59.SH
 60lpr: \fIprinter\fP\|: jobs queued, but cannot start daemon.
 61.IP
 62The connection to 
 63.I lpd
 64on the local machine failed. 
 65This usually means the printer server started at
 66boot time has died or is hung.  Check the local socket
 67/dev/printer to be sure it still exists (if it does not exist,
 68there is no 
 69.I lpd
 70process running). 
 71Usually it is enough to get a super-user to type the following to
 72restart
 73.IR lpd .
 74.DS
 75% /usr/lib/lpd
 76.DE
 77You can also check the state of the master printer daemon with the following.
 78.DS
 79% ps l`cat /usr/spool/lpd.lock`
 80.DE
 81.IP
 82Another possibility is that the
 83.I lpr
 84program is not set-user-id to \fIroot\fP, set-group-id to group \fIdaemon\fP.
 85This can be checked with
 86.DS
 87% ls \-lg /usr/ucb/lpr
 88.DE
 89.SH
 90lpr: \fIprinter\fP\|: printer queue is disabled
 91.IP
 92This means the queue was turned off with
 93.DS
 94% lpc disable \fIprinter\fP
 95.DE
 96to prevent 
 97.I lpr
 98from putting files in the queue.  This is normally
 99done by the system manager when a printer is
100going to be down for a long time.  The
101printer can be turned back on by a super-user with
102.IR lpc .
103.NH 2
104LPQ
105.SH
106waiting for \fIprinter\fP to become ready (offline ?)
107.IP
108The printer device could not be opened by the daemon. 
109This can happen for several reasons,
110the most common is that the printer is turned off-line.
111This message can also be generated if the printer is out
112of paper, the paper is jammed, etc.
113The actual reason is dependent on the meaning
114of error codes returned by system device driver. 
115Not all printers supply enough information 
116to distinguish when a printer is off-line or having
117trouble (e.g. a printer connected through a serial line). 
118Another possible cause of this message is
119some other process, such as an output filter,
120has an exclusive open on the device.  Your only recourse
121here is to kill off the offending program(s) and
122restart the printer with
123.IR lpc .
124.SH
125\fIprinter\fP is ready and printing
126.IP
127The
128.I lpq
129program checks to see if a daemon process exists for
130.I printer
131and prints the file \fIstatus\fP located in the spooling directory.
132If the daemon is hung, a super user can use
133.I lpc
134to abort the current daemon and start a new one.
135.SH
136waiting for \fIhost\fP to come up
137.IP
138This implies there is a daemon trying to connect to the remote
139machine named
140.I host
141to send the files in the local queue. 
142If the remote machine is up,
143.I lpd
144on the remote machine is probably dead or
145hung and should be restarted as mentioned for
146.IR lpr .
147.SH
148sending to \fIhost\fP
149.IP
150The files should be in the process of being transferred to the remote
151.IR host .
152If not, the local daemon should be aborted and started with
153.IR lpc .
154.SH
155Warning: \fIprinter\fP is down
156.IP
157The printer has been marked as being unavailable with
158.IR lpc .
159.SH
160Warning: no daemon present
161.IP
162The \fIlpd\fP process overseeing
163the spooling queue, as specified in the ``lock'' file
164in that directory, does not exist.  This normally occurs
165only when the daemon has unexpectedly died.
166The error log file for the printer and the \fIsyslogd\fP logs
167should be checked for a
168diagnostic from the deceased process.
169To restart an \fIlpd\fP, use
170.DS
171% lpc restart \fIprinter\fP
172.DE
173.SH
174no space on remote; waiting for queue to drain
175.IP
176This implies that there is insufficient disk space on the remote.
177If the file is large enough, there will never be enough space on
178the remote (even after the queue on the remote is empty). The solution here
179is to move the spooling queue or make more free space on the remote.
180.NH 2
181LPRM
182.SH
183lprm: \fIprinter\fP\|: cannot restart printer daemon
184.IP
185This case is the same as when
186.I lpr
187prints that the daemon cannot be started.
188.NH 2
189LPD
190.PP
191The
192.I lpd
193program can log many different messages using \fIsyslogd\fP\|(8).
194Most of these messages are about files that can not
195be opened and usually imply that the
196.I printcap
197file or the protection modes of the files are
198incorrect.   Files may also be inaccessible if people
199manually manipulate the line printer system (i.e. they
200bypass the
201.I lpr
202program). 
203.PP
204In addition to messages generated by 
205.IR lpd ,
206any of the filters that
207.I lpd
208spawns may log messages using \fIsyslogd\fP or to the error log file
209(the file specified in the \fBlf\fP entry in \fIprintcap\fP\|).
210.NH 2
211LPC
212.PP
213.SH
214couldn't start printer
215.IP
216This case is the same as when
217.I lpr
218reports that the daemon cannot be started.
219.SH
220cannot examine spool directory
221.IP
222Error messages beginning with ``cannot ...'' are usually because of
223incorrect ownership or protection mode of the lock file, spooling
224directory or the
225.I lpc
226program.