File: bugreport.html

package info (click to toggle)
samba 2:3.6.6-6+deb7u7
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 160,976 kB
  • sloc: ansic: 1,764,536; xml: 114,867; python: 78,119; perl: 27,633; sh: 13,802; makefile: 4,704; asm: 3,281; cpp: 2,281; yacc: 1,949; exp: 1,784; ada: 1,681; pascal: 1,089; cs: 879; awk: 756; lex: 566; csh: 58; sed: 45; php: 6
file content (159 lines) | stat: -rw-r--r-- 16,384 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
<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.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.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="tdb.html" title="Chapter�41.�Managing TDB Files"></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="tdb.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter�40.�Reporting Bugs"><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">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</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">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</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">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</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#id447883">Introduction</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id447963">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#id448181">Debugging-Specific Operations</a></span></dt></dl></dd><dt><span class="sect1"><a href="bugreport.html#id448377">Internal Errors</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id448498">Attaching to a Running Process</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id448614">Patches</a></span></dt></dl></div><div class="sect1" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id447883"></a>Introduction</h2></div></div></div><p>
<a class="indexterm" name="id447891"></a>
<a class="indexterm" name="id447898"></a>
Please report bugs using Samba's <a class="ulink" href="https://bugzilla.samba.org/" target="_top">Bugzilla</a> facilities and take
the time to read this file before you submit a bug report. Also, check to see if it has changed between
releases, as we may be changing the bug reporting mechanism at some point.
</p><p>
Please do as much as you can yourself to help track down the
bug. Samba is maintained by a dedicated group of people who volunteer
their time, skills, and efforts. We receive far more mail than
we can possibly answer, so you have a much higher chance of a response
and a fix if you send us a <span class="quote">&#8220;<span class="quote">developer-friendly</span>&#8221;</span> bug report that lets
us fix it fast. 
</p><p>
<a class="indexterm" name="id447925"></a>
<a class="indexterm" name="id447932"></a>
<a class="indexterm" name="id447939"></a>
If you post the bug to the comp.protocols.smb
newsgroup or the mailing list, do not assume that we will read it. If you suspect that your 
problem is not a bug but a configuration problem, it is better to send 
it to the Samba mailing list, as there are thousands of other users on
that list who may be able to help you.
</p><p>
You may also like to look though the recent mailing list archives,
which are conveniently accessible on the Samba Web pages
at <a class="ulink" href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>.
</p></div><div class="sect1" title="General Information"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id447963"></a>General Information</h2></div></div></div><p>
Before submitting a bug report, check your config for silly
errors. Look in your log files for obvious messages that tell
you've misconfigured something. Run testparm to check your config
file for correct syntax.
</p><p>
Have you looked through <a class="link" href="diagnosis.html" title="Chapter�38.�The Samba Checklist">The Samba Checklist</a>? This is extremely important.
</p><p>
If you include part of a log file with your bug report, then be sure to
annotate it with exactly what you were doing on the client at the
time and exactly what the results were.
</p></div><div class="sect1" title="Debug Levels"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dbglvl"></a>Debug Levels</h2></div></div></div><p>
If the bug has anything to do with Samba behaving incorrectly as a
server (like refusing to open a file), then the log files will probably
be quite useful. Depending on the problem, a log level of between 3 and
10 showing the problem may be appropriate. A higher level gives more
detail but may use too much disk space.
</p><p>
<a class="indexterm" name="id448007"></a>
<a class="indexterm" name="id448014"></a>
To set the debug level, use the <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a> in your 
<code class="filename">smb.conf</code>. You may also find it useful to set the log 
level higher for just one machine and keep separate logs for each machine. 
To do this, add the following lines to your main <code class="filename">smb.conf</code> file:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id448052"></a><em class="parameter"><code>log level = 10</code></em></td></tr><tr><td><a class="indexterm" name="id448064"></a><em class="parameter"><code>log file = /usr/local/samba/lib/log.%m</code></em></td></tr><tr><td><a class="indexterm" name="id448076"></a><em class="parameter"><code>include = /usr/local/samba/lib/smb.conf.%m</code></em></td></tr></table><p>
and create a file <code class="filename">/usr/local/samba/lib/smb.conf.<em class="replaceable"><code>machine</code></em></code> where
<em class="replaceable"><code>machine</code></em> is the name of the client you wish to debug. In that file put any
<code class="filename">smb.conf</code> commands you want; for example, <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a> may be useful. This also allows
you to experiment with different security systems, protocol levels, and so on, on just one machine.
</p><p>
The <code class="filename">smb.conf</code> entry <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a> is synonymous with the parameter <a class="link" href="smb.conf.5.html#DEBUGLEVEL" target="_top">debuglevel</a> that has been used in older versions of Samba and is being retained for backward
compatibility of <code class="filename">smb.conf</code> files.
</p><p>
As the <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a> value is increased, you will record a significantly greater level of
debugging information. For most debugging operations, you may not need a setting higher than
<code class="constant">3</code>. Nearly all bugs can be tracked at a setting of <code class="constant">10</code>, but be
prepared for a large volume of log data.
</p><div class="sect2" title="Debugging-Specific Operations"><div class="titlepage"><div><div><h3 class="title"><a name="id448181"></a>Debugging-Specific Operations</h3></div></div></div><p>
<a class="indexterm" name="id448189"></a>
<a class="indexterm" name="id448196"></a>
<a class="indexterm" name="id448202"></a>
<a class="indexterm" name="id448209"></a>
	Samba-3.x permits debugging (logging) of specific functional components without unnecessarily
	cluttering the log files with detailed logs for all operations. An example configuration to 
	achieve this is shown in:
	</p><p>
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id448227"></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="id448238"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id448250"></a><em class="parameter"><code>log file = /var/log/samba/%U.%m.log</code></em></td></tr></table><p>
</p><p>
	This will cause the level of detail to be expanded to the debug class (log level) passed to
	each functional area per the value shown above. The first value passed to the <em class="parameter"><code>log level</code></em>
	of <code class="constant">0</code> means turn off all unnecessary debugging except the debug classes set for
	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>
	may be used to attain very precise analysis of each SMB operation Samba is conducting.
	</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" title="Internal Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id448377"></a>Internal Errors</h2></div></div></div><p>
If you get the message <span class="quote">&#8220;<span class="quote"><span class="errorname">INTERNAL ERROR</span></span>&#8221;</span> in your log files, 
it means that Samba got an unexpected signal while running. It is probably a
segmentation fault and almost certainly means a bug in Samba (unless
you have faulty hardware or system software).
</p><p>
If the message came from smbd, it will probably be accompanied by
a message that details the last SMB message received by smbd. This
information is often useful in tracking down the problem, so please
include it in your bug report.
</p><p>
You should also detail how to reproduce the problem, if
possible. Please make this reasonably detailed.
</p><p>
<a class="indexterm" name="id448404"></a>
You may also find that a core file appeared in a <code class="filename">corefiles</code>
subdirectory of the directory where you keep your Samba log
files. This file is the most useful tool for tracking down the bug. To
use it, you do this:
<a class="indexterm" name="id448419"></a>
<a class="indexterm" name="id448425"></a>
</p><pre class="screen">
<code class="prompt">$ </code><strong class="userinput"><code>gdb smbd core</code></strong>
</pre><p>
</p><p>
<a class="indexterm" name="id448451"></a>
<a class="indexterm" name="id448458"></a>
adding appropriate paths to smbd and core so gdb can find them. If you
do not have gdb, try <strong class="userinput"><code>dbx</code></strong>. Then within the debugger,
use the command <code class="literal">where</code> to give a stack trace of where the
problem occurred. Include this in your report.
</p><p>
<a class="indexterm" name="id448480"></a>
If you know any assembly language, do a <code class="literal">disass</code> of the routine
where the problem occurred (if it's in a library routine, then
disassemble the routine that called it) and try to work out exactly
where the problem is by looking at the surrounding code. Even if you
do not know assembly, including this information in the bug report can be
useful. 
</p></div><div class="sect1" title="Attaching to a Running Process"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id448498"></a>Attaching to a Running Process</h2></div></div></div><p>
<a class="indexterm" name="id448506"></a>
<a class="indexterm" name="id448513"></a>
<a class="indexterm" name="id448519"></a>
Unfortunately, some UNIXes (in particular some recent Linux kernels)
refuse to dump a core file if the task has changed UID (which smbd
does often). To debug with this sort of system, you could try to attach
to the running process using
<strong class="userinput"><code>gdb smbd <em class="replaceable"><code>PID</code></em></code></strong>, where you get
<em class="replaceable"><code>PID</code></em> from <span class="application">smbstatus</span>.
Then use <code class="literal">c</code> to continue and try to cause the core dump
using the client. The debugger should catch the fault and tell you
where it occurred.
</p><p>
Sometimes it is necessary to build Samba binary files that have debugging
symbols so as to make it possible to capture enough information from a crashed
operation to permit the Samba Team to fix the problem.
</p><p>
Compile with <code class="constant">-g</code> to ensure you have symbols in place. 
Add the following line to the <code class="filename">smb.conf</code> file global section:
</p><pre class="screen">
panic action = "/bin/sleep 90000"
</pre><p>
to catch any panics. If <code class="literal">smbd</code> seems to be frozen, look for any sleep
processes. If it is not, and appears to be spinning, find the PID
of the spinning process and type:
</p><pre class="screen">
<code class="prompt">root# </code> gdb /usr/local/samba/sbin/smbd
</pre><p>
<a class="indexterm" name="id448597"></a>
then <span class="quote">&#8220;<span class="quote">attach `pid'</span>&#8221;</span> (of the spinning process), then type <span class="quote">&#8220;<span class="quote">bt</span>&#8221;</span> to
get a backtrace to see where the smbd is in the call path.
</p></div><div class="sect1" title="Patches"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id448614"></a>Patches</h2></div></div></div><p>
<a class="indexterm" name="id448621"></a>
<a class="indexterm" name="id448628"></a>
The best sort of bug report is one that includes a fix! If you send us
patches, please use <strong class="userinput"><code>diff -u</code></strong> format if your version of 
diff supports it; otherwise, use <strong class="userinput"><code>diff -c4</code></strong>. Make sure 
you do the diff against a clean version of the source and let me know 
exactly what version you used. 
</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="tdb.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">�Chapter�41.�Managing TDB Files</td></tr></table></div></body></html>