old-www/HOWTO/Debian-and-Windows-Shared-P.../troubleshooting.html

351 lines
5.7 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Troubleshooting</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="Debian and Windows Shared Printing mini-HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Sharing Printers With Windows PCs"
HREF="sharing_with_windows.html"><LINK
REL="NEXT"
TITLE="License"
HREF="license.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Debian and Windows Shared Printing mini-HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="sharing_with_windows.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="license.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="troubleshooting"
></A
>5. Troubleshooting</H1
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="connect_failure"
></A
>5.1. Failing To Connect To Windows Printers</H2
><P
>&#13;When <EM
>smbspool</EM
>, the
<B
CLASS="command"
>smbclient</B
> utility CUPS uses,
fails to connect properly it emits error messages
that are humorous but not very helpful. One such message is <TT
CLASS="computeroutput"
>Unable
to connect to SAMBA host: Success.</TT
> Another sign of connection failures
is when documents seem to get stuck on the queue when printing to
Windows printers.
</P
><P
>&#13;View the most recent entries in the CUPS log with the following command:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>/usr/bin/tail /var/log/cups/error_log
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>&#13;If you see a message similar to <TT
CLASS="computeroutput"
>cli_connect() failed...</TT
> then
<EM
>smbspool</EM
> could not find the Windows PC you are
trying to connect to.
Check the spelling of the Windows PC's host name. Check that the
Windows PC is turned on and that its network connection is functioning
properly. Make sure you can connect to it using
<B
CLASS="command"
>smbclient</B
> as shown in <A
HREF="printing_to_windows.html#to_windows"
>Section 3.1</A
>.
</P
><P
>&#13;If you see a message similar to <TT
CLASS="computeroutput"
>SMB tree connect failed: ERRSRV
- ERRinvnetname</TT
> then <B
CLASS="command"
>smbclient</B
> connected
to the Windows PC
but could not connect to the printer you requested. Check the spelling
of the shared printer using <B
CLASS="command"
>smbclient</B
> as shown in
<A
HREF="printing_to_windows.html#to_windows"
>Section 3.1</A
>.
</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="other_failure"
></A
>5.2. Other Failures</H2
><P
>&#13;Other failures include being unable to print to a local printer and
having your print jobs disappear from the queue without being printed.
You may also see vague error messages such as <TT
CLASS="computeroutput"
>Child process 2384
exited with status 32.</TT
>
</P
><P
>&#13;Increase CUPS' logging level to <SPAN
CLASS="QUOTE"
>"debug"</SPAN
> to see more messages about
what happened before the print job failed.
</P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;Open the main CUPS configuration file <TT
CLASS="filename"
>/etc/cups/cupsd.conf</TT
> in
a text editor.
</P
></LI
><LI
><P
>&#13;Change the line that reads <SPAN
CLASS="QUOTE"
>"LogLevel warn"</SPAN
> to <SPAN
CLASS="QUOTE"
>"LogLevel debug"</SPAN
>.
</P
></LI
><LI
><P
>&#13;Save the configuration file and exit the text editor.
</P
></LI
><LI
><P
>Restart the CUPS server with the command:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>/etc/init.d/cupsys restart
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
></OL
><P
>&#13;You can follow the CUPS log with the following command:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>/usr/bin/tail -f /var/log/cups/error_log
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>&#13;You should see a line that reads <TT
CLASS="computeroutput"
>Scheduler shutting down due to
SIGTERM</TT
>. This indicates that the CUPS server was stopped successfully.
</P
><P
>&#13;Send your print job again and watch for useful debug messages that
appear. One example of a useful debug message is <TT
CLASS="computeroutput"
>GNU Ghostscript
7.05: Can't start ijs server 'hpijs'.</TT
> In this case the solution
is to install the <SPAN
CLASS="QUOTE"
>"hpijs"</SPAN
> package.
</P
><P
>&#13;If you cannot determine the cause of the failure, do an Internet search
for key terms in error messages you see; it is likely that someone
has solved your problem before. You may also try upgrading the packages
listed in <A
HREF="getting_started.html#packages"
>Section 2.2</A
> to their latest versions.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="sharing_with_windows.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="license.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Sharing Printers With Windows PCs</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>License</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>