- Timestamp:
- Sep 30, 2008, 7:14:08 AM (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.0/docs/htmldocs/Samba3-HOWTO/bugreport.html
r134 r158 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 40. Reporting Bugs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="prev" href="problems.html" title="Chapter 39. Analyzing and Solving Samba Problems"><link rel="next" href=" Appendix.html" title="Part VI. Reference Section"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 40. Reporting Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="problems.html">Prev</a> </td><th width="60%" align="center">Part V. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="Appendix.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter 40. Reporting Bugs</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:[email protected]">[email protected]</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:[email protected]">[email protected]</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:[email protected]">[email protected]</a>></code></p></div></div></div></div><div><p class="pubdate"> 27 June 1997 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="bugreport.html#id465317">Introduction</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id465397">General Information</a></span></dt><dt><span class="sect1"><a href="bugreport.html#dbglvl">Debug Levels</a></span></dt><dd><dl><dt><span class="sect2"><a href="bugreport.html#id465615">Debugging-Specific Operations</a></span></dt></dl></dd><dt><span class="sect1"><a href="bugreport.html#id465810">Internal Errors</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id465932">Attaching to a Running Process</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id466047">Patches</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id465317"></a>Introduction</h2></div></div></div><p>2 <a class="indexterm" name="id4 65325"></a>3 <a class="indexterm" name="id4 65332"></a>1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 40. Reporting Bugs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="prev" href="problems.html" title="Chapter 39. Analyzing and Solving Samba Problems"><link rel="next" href=""></a>Introduction</h2></div></div></div><p> 2 <a class="indexterm" name="id4"></a> 3 <a class="indexterm" name="id4"></a> 4 4 Please report bugs using Samba's <a class="ulink" href="https://bugzilla.samba.org/" target="_top">Bugzilla</a> facilities and take 5 5 the time to read this file before you submit a bug report. Also, check to see if it has changed between … … 13 13 us fix it fast. 14 14 </p><p> 15 <a class="indexterm" name="id4 65360"></a>16 <a class="indexterm" name="id4 65366"></a>17 <a class="indexterm" name="id4 65373"></a>15 <a class="indexterm" name="id4"></a> 16 <a class="indexterm" name="id4"></a> 17 <a class="indexterm" name="id4"></a> 18 18 If you post the bug to the comp.protocols.smb 19 19 newsgroup or the mailing list, do not assume that we will read it. If you suspect that your … … 25 25 which are conveniently accessible on the Samba Web pages 26 26 at <a class="ulink" href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>. 27 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4 65397"></a>General Information</h2></div></div></div><p>27 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4"></a>General Information</h2></div></div></div><p> 28 28 Before submitting a bug report, check your config for silly 29 29 errors. Look in your log files for obvious messages that tell … … 43 43 detail but may use too much disk space. 44 44 </p><p> 45 <a class="indexterm" name="id4 65442"></a>46 <a class="indexterm" name="id4 65448"></a>45 <a class="indexterm" name="id4"></a> 46 <a class="indexterm" name="id4"></a> 47 47 To set the debug level, use the <a class="link" href="smb.conf.5.html#LOGLEVEL">log level</a> in your 48 48 <code class="filename">smb.conf</code>. You may also find it useful to set the log 49 49 level higher for just one machine and keep separate logs for each machine. 50 50 To do this, add the following lines to your main <code class="filename">smb.conf</code> file: 51 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id4 65486"></a><em class="parameter"><code>log level = 10</code></em></td></tr><tr><td><a class="indexterm" name="id465498"></a><em class="parameter"><code>log file = /usr/local/samba/lib/log.%m</code></em></td></tr><tr><td><a class="indexterm" name="id465509"></a><em class="parameter"><code>include = /usr/local/samba/lib/smb.conf.%m</code></em></td></tr></table><p>51 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id4"></a><em class="parameter"><code>include = /usr/local/samba/lib/smb.conf.%m</code></em></td></tr></table><p> 52 52 and create a file <code class="filename">/usr/local/samba/lib/smb.conf.<em class="replaceable"><code>machine</code></em></code> where 53 53 <em class="replaceable"><code>machine</code></em> is the name of the client you wish to debug. In that file put any … … 62 62 <code class="constant">3</code>. Nearly all bugs can be tracked at a setting of <code class="constant">10</code>, but be 63 63 prepared for a large volume of log data. 64 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4 65615"></a>Debugging-Specific Operations</h3></div></div></div><p>65 <a class="indexterm" name="id4 65623"></a>66 <a class="indexterm" name="id4 65629"></a>67 <a class="indexterm" name="id4 65636"></a>68 <a class="indexterm" name="id4 65643"></a>64 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></a>Debugging-Specific Operations</h3></div></div></div><p> 65 <a class="indexterm" name="id4"></a> 66 <a class="indexterm" name="id4"></a> 67 <a class="indexterm" name="id4"></a> 68 <a class="indexterm" name="id4"></a> 69 69 Samba-3.x permits debugging (logging) of specific functional components without unnecessarily 70 70 cluttering the log files with detailed logs for all operations. An example configuration to 71 71 achieve this is shown in: 72 72 </p><p> 73 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id4 65660"></a><em class="parameter"><code>log level = 0 tdb:3 passdb:5 auth:4 vfs:2</code></em></td></tr><tr><td><a class="indexterm" name="id465672"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id465684"></a><em class="parameter"><code>log file = /var/log/samba/%U.%m.log</code></em></td></tr></table><p>73 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id4"></a><em class="parameter"><code>log file = /var/log/samba/%U.%m.log</code></em></td></tr></table><p> 74 74 </p><p> 75 75 This will cause the level of detail to be expanded to the debug class (log level) passed to … … 78 78 the functional areas as specified. The table shown in <a class="link" href="bugreport.html#dbgclass" title="Table 40.1. Debuggable Functions">Debuggable Functions</a> 79 79 may be used to attain very precise analysis of each SMB operation Samba is conducting. 80 </p><div class="table"><a name="dbgclass"></a><p class="title"><b>Table 40.1. Debuggable Functions</b></p><div class="table-contents"><table summary="Debuggable Functions" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Function Name</th><th align="center">Function Name</th></tr></thead><tbody><tr><td align="center">all</td><td align="center">passdb</td></tr><tr><td align="center">tdb</td><td align="center">sam</td></tr><tr><td align="center">printdrivers</td><td align="center">auth</td></tr><tr><td align="center">lanman</td><td align="center">winbind</td></tr><tr><td align="center">smb</td><td align="center">vfs</td></tr><tr><td align="center">rpc_parse</td><td align="center">idmap</td></tr><tr><td align="center">rpc_srv</td><td align="center">quota</td></tr><tr><td align="center">rpc_cli</td><td align="center">acls</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4 65810"></a>Internal Errors</h2></div></div></div><p>80 </p><div class="table"><a name="dbgclass"></a><p class="title"><b>Table 40.1. Debuggable Functions</b></p><div class="table-contents"><table summary="Debuggable Functions" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Function Name</th><th align="center">Function Name</th></tr></thead><tbody><tr><td align="center">all</td><td align="center">passdb</td></tr><tr><td align="center">tdb</td><td align="center">sam</td></tr><tr><td align="center">printdrivers</td><td align="center">auth</td></tr><tr><td align="center">lanman</td><td align="center">winbind</td></tr><tr><td align="center">smb</td><td align="center">vfs</td></tr><tr><td align="center">rpc_parse</td><td align="center">idmap</td></tr><tr><td align="center">rpc_srv</td><td align="center">quota</td></tr><tr><td align="center">rpc_cli</td><td align="center">acls</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4"></a>Internal Errors</h2></div></div></div><p> 81 81 If you get the message “<span class="quote"><span class="errorname">INTERNAL ERROR</span></span>” in your log files, 82 82 it means that Samba got an unexpected signal while running. It is probably a … … 92 92 possible. Please make this reasonably detailed. 93 93 </p><p> 94 <a class="indexterm" name="id4 65837"></a>94 <a class="indexterm" name="id4"></a> 95 95 You may also find that a core file appeared in a <code class="filename">corefiles</code> 96 96 subdirectory of the directory where you keep your Samba log 97 97 files. This file is the most useful tool for tracking down the bug. To 98 98 use it, you do this: 99 <a class="indexterm" name="id4 65852"></a>100 <a class="indexterm" name="id4 65858"></a>99 <a class="indexterm" name="id4"></a> 100 <a class="indexterm" name="id4"></a> 101 101 </p><pre class="screen"> 102 102 <code class="prompt">$ </code><strong class="userinput"><code>gdb smbd core</code></strong> 103 103 </pre><p> 104 104 </p><p> 105 <a class="indexterm" name="id4 65884"></a>106 <a class="indexterm" name="id4 65890"></a>105 <a class="indexterm" name="id4"></a> 106 <a class="indexterm" name="id4"></a> 107 107 adding appropriate paths to smbd and core so gdb can find them. If you 108 108 do not have gdb, try <strong class="userinput"><code>dbx</code></strong>. Then within the debugger, … … 110 110 problem occurred. Include this in your report. 111 111 </p><p> 112 <a class="indexterm" name="id4 65914"></a>112 <a class="indexterm" name="id4"></a> 113 113 If you know any assembly language, do a <code class="literal">disass</code> of the routine 114 114 where the problem occurred (if it's in a library routine, then … … 117 117 do not know assembly, including this information in the bug report can be 118 118 useful. 119 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4 65932"></a>Attaching to a Running Process</h2></div></div></div><p>120 <a class="indexterm" name="id4 65940"></a>121 <a class="indexterm" name="id4 65946"></a>122 <a class="indexterm" name="id4 65953"></a>119 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4"></a>Attaching to a Running Process</h2></div></div></div><p> 120 <a class="indexterm" name="id4"></a> 121 <a class="indexterm" name="id4"></a> 122 <a class="indexterm" name="id4"></a> 123 123 Unfortunately, some UNIXes (in particular some recent Linux kernels) 124 124 refuse to dump a core file if the task has changed UID (which smbd … … 146 146 <code class="prompt">root# </code> gdb /usr/local/samba/sbin/smbd 147 147 </pre><p> 148 <a class="indexterm" name="id4 66030"></a>148 <a class="indexterm" name="id4"></a> 149 149 then “<span class="quote">attach `pid'</span>” (of the spinning process), then type “<span class="quote">bt</span>” to 150 150 get a backtrace to see where the smbd is in the call path. 151 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4 66047"></a>Patches</h2></div></div></div><p>152 <a class="indexterm" name="id4 66054"></a>153 <a class="indexterm" name="id4 66061"></a>151 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4"></a>Patches</h2></div></div></div><p> 152 <a class="indexterm" name="id4"></a> 153 <a class="indexterm" name="id4"></a> 154 154 The best sort of bug report is one that includes a fix! If you send us 155 155 patches, please use <strong class="userinput"><code>diff -u</code></strong> format if your version of … … 157 157 you do the diff against a clean version of the source and let me know 158 158 exactly what version you used. 159 </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="problems.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href=" Appendix.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 39. Analyzing and Solving Samba Problems </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Part VI. Reference Section</td></tr></table></div></body></html>159 </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="problems.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="</td></tr></table></div></body></html>
Note:
See TracChangeset
for help on using the changeset viewer.
