1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN">
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.76b+
11 TITLE=
"SAMBA Project Documentation"
12 HREF=
"samba-howto-collection.html"><LINK
15 HREF=
"appendixes.html"><LINK
17 TITLE=
"Samba and other CIFS clients"
18 HREF=
"other-clients.html"><LINK
20 TITLE=
"Diagnosing your samba server"
21 HREF=
"diagnosis.html"></HEAD
32 SUMMARY=
"Header navigation table"
41 >SAMBA Project Documentation
</TH
49 HREF=
"other-clients.html"
76 NAME=
"BUGREPORT">Chapter
25. Reporting Bugs
</H1
82 NAME=
"AEN3309">25.1. Introduction
</H1
84 >The email address for bug reports for stable releases is
<A
85 HREF=
"samba@samba.org"
89 Bug reports for alpha releases should go to
<A
90 HREF=
"mailto:samba-technical@samba.org"
92 >samba-technical@samba.org
</A
95 >Please take the time to read this file before you submit a bug
96 report. Also, please see if it has changed between releases, as we
97 may be changing the bug reporting mechanism at some time.
</P
99 >Please also do as much as you can yourself to help track down the
100 bug. Samba is maintained by a dedicated group of people who volunteer
101 their time, skills and efforts. We receive far more mail about it than
102 we can possibly answer, so you have a much higher chance of an answer
103 and a fix if you send us a
"developer friendly" bug report that lets
106 >Do not assume that if you post the bug to the comp.protocols.smb
107 newsgroup or the mailing list that we will read it. If you suspect that your
108 problem is not a bug but a configuration problem then it is better to send
109 it to the Samba mailing list, as there are (at last count)
5000 other users on
110 that list that may be able to help you.
</P
112 >You may also like to look though the recent mailing list archives,
113 which are conveniently accessible on the Samba web pages
115 HREF=
"http://samba.org/samba/"
117 >http://samba.org/samba/
</A
125 NAME=
"AEN3319">25.2. General info
</H1
127 >Before submitting a bug report check your config for silly
128 errors. Look in your log files for obvious messages that tell you that
129 you've misconfigured something and run testparm to test your config
130 file for correct syntax.
</P
132 >Have you run through the
<A
133 HREF=
"Diagnosis.html"
137 This is very important.
</P
139 >If you include part of a log file with your bug report then be sure to
140 annotate it with exactly what you were doing on the client at the
141 time, and exactly what the results were.
</P
148 NAME=
"AEN3325">25.3. Debug levels
</H1
150 >If the bug has anything to do with Samba behaving incorrectly as a
151 server (like refusing to open a file) then the log files will probably
152 be very useful. Depending on the problem a log level of between
3 and
153 10 showing the problem may be appropriate. A higher level givesmore
154 detail, but may use too much disk space.
</P
156 >To set the debug level use
<B
163 >. You may also find it useful to set the log
164 level higher for just one machine and keep separate logs for each machine.
168 CLASS=
"PROGRAMLISTING"
170 log file = /usr/local/samba/lib/log.%m
171 include = /usr/local/samba/lib/smb.conf.%m
</PRE
177 >/usr/local/samba/lib/smb.conf.machine
</TT
179 "machine" is the name of the client you wish to debug. In that file
180 put any smb.conf commands you want, for example
184 > may be useful. This also allows you to
185 experiment with different security systems, protocol levels etc on just
195 is synonymous with the entry
<B
199 used in older versions of Samba and is being retained for backwards
200 compatibility of smb.conf files.
</P
205 > value is increased you will record
206 a significantly increasing level of debugging information. For most
207 debugging operations you may not need a setting higher than
3. Nearly
208 all bugs can be tracked at a setting of
10, but be prepared for a VERY
209 large volume of log data.
</P
216 NAME=
"AEN3342">25.4. Internal errors
</H1
218 >If you get a
"INTERNAL ERROR" message in your log files it means that
219 Samba got an unexpected signal while running. It is probably a
220 segmentation fault and almost certainly means a bug in Samba (unless
221 you have faulty hardware or system software)
</P
223 >If the message came from smbd then it will probably be accompanied by
224 a message which details the last SMB message received by smbd. This
225 info is often very useful in tracking down the problem so please
226 include it in your bug report.
</P
228 >You should also detail how to reproduce the problem, if
229 possible. Please make this reasonably detailed.
</P
231 >You may also find that a core file appeared in a
"corefiles"
232 subdirectory of the directory where you keep your samba log
233 files. This file is the most useful tool for tracking down the bug. To
234 use it you do this:
</P
241 >adding appropriate paths to smbd and core so gdb can find them. If you
242 don't have gdb then try
"dbx". Then within the debugger use the
243 command
"where" to give a stack trace of where the problem
244 occurred. Include this in your mail.
</P
246 >If you known any assembly language then do a
"disass" of the routine
247 where the problem occurred (if its in a library routine then
248 disassemble the routine that called it) and try to work out exactly
249 where the problem is by looking at the surrounding code. Even if you
250 don't know assembly then incuding this info in the bug report can be
258 NAME=
"AEN3352">25.5. Attaching to a running process
</H1
260 >Unfortunately some unixes (in particular some recent linux kernels)
261 refuse to dump a core file if the task has changed uid (which smbd
262 does often). To debug with this sort of system you could try to attach
263 to the running process using
"gdb smbd PID" where you get PID from
264 smbstatus. Then use
"c" to continue and try to cause the core dump
265 using the client. The debugger should catch the fault and tell you
266 where it occurred.
</P
273 NAME=
"AEN3355">25.6. Patches
</H1
275 >The best sort of bug report is one that includes a fix! If you send us
276 patches please use
<B
279 > format if your version of
280 diff supports it, otherwise use
<B
284 your do the diff against a clean version of the source and let me know
285 exactly what version you used.
</P
293 SUMMARY=
"Footer navigation table"
304 HREF=
"other-clients.html"
313 HREF=
"samba-howto-collection.html"
322 HREF=
"diagnosis.html"
332 >Samba and other CIFS clients
</TD
338 HREF=
"appendixes.html"
346 >Diagnosing your samba server
</TD