1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 TITLE="SAMBA Project Documentation"
11 HREF="samba-howto-collection.html"><LINK
14 HREF="appendixes.html"><LINK
16 TITLE="Analysing and solving samba problems"
17 HREF="problems.html"></HEAD
28 SUMMARY="Header navigation table"
37 >SAMBA Project Documentation</TH
70 >Chapter 35. Reporting Bugs</H1
80 HREF="bugreport.html#AEN5125"
85 HREF="bugreport.html#AEN5135"
90 HREF="bugreport.html#AEN5141"
95 HREF="bugreport.html#AEN5162"
100 HREF="bugreport.html#AEN5176"
101 >Attaching to a running process</A
105 HREF="bugreport.html#AEN5184"
116 >35.1. Introduction</A
119 >The email address for bug reports for stable releases is <A
120 HREF="mailto:samba@samba.org"
124 Bug reports for alpha releases should go to <A
125 HREF="mailto:samba-technical@samba.org"
127 >samba-technical@samba.org</A
130 >Please take the time to read this file before you submit a bug
131 report. Also, please see if it has changed between releases, as we
132 may be changing the bug reporting mechanism at some time.</P
134 >Please also do as much as you can yourself to help track down the
135 bug. Samba is maintained by a dedicated group of people who volunteer
136 their time, skills and efforts. We receive far more mail about it than
137 we can possibly answer, so you have a much higher chance of an answer
138 and a fix if you send us a "developer friendly" bug report that lets
141 >Do not assume that if you post the bug to the comp.protocols.smb
142 newsgroup or the mailing list that we will read it. If you suspect that your
143 problem is not a bug but a configuration problem then it is better to send
144 it to the Samba mailing list, as there are (at last count) 5000 other users on
145 that list that may be able to help you.</P
147 >You may also like to look though the recent mailing list archives,
148 which are conveniently accessible on the Samba web pages
150 HREF="http://samba.org/samba/"
152 >http://samba.org/samba/</A
161 >35.2. General info</A
164 >Before submitting a bug report check your config for silly
165 errors. Look in your log files for obvious messages that tell you that
166 you've misconfigured something and run testparm to test your config
167 file for correct syntax.</P
169 >Have you run through the <A
170 HREF="diagnosis.html"
173 This is very important.</P
175 >If you include part of a log file with your bug report then be sure to
176 annotate it with exactly what you were doing on the client at the
177 time, and exactly what the results were.</P
185 >35.3. Debug levels</A
188 >If the bug has anything to do with Samba behaving incorrectly as a
189 server (like refusing to open a file) then the log files will probably
190 be very useful. Depending on the problem a log level of between 3 and
191 10 showing the problem may be appropriate. A higher level givesmore
192 detail, but may use too much disk space.</P
194 >To set the debug level use <B
201 >. You may also find it useful to set the log
202 level higher for just one machine and keep separate logs for each machine.
206 CLASS="PROGRAMLISTING"
208 log file = /usr/local/samba/lib/log.%m
209 include = /usr/local/samba/lib/smb.conf.%m</PRE
215 >/usr/local/samba/lib/smb.conf.<VAR
223 > is the name of the client you wish to debug. In that file
227 > commands you want, for example
231 > may be useful. This also allows you to
232 experiment with different security systems, protocol levels etc on just
242 is synonymous with the entry <B
246 used in older versions of Samba and is being retained for backwards
255 > value is increased you will record
256 a significantly increasing level of debugging information. For most
257 debugging operations you may not need a setting higher than 3. Nearly
258 all bugs can be tracked at a setting of 10, but be prepared for a VERY
259 large volume of log data.</P
267 >35.4. Internal errors</A
270 >If you get a "INTERNAL ERROR" message in your log files it means that
271 Samba got an unexpected signal while running. It is probably a
272 segmentation fault and almost certainly means a bug in Samba (unless
273 you have faulty hardware or system software).</P
275 >If the message came from smbd then it will probably be accompanied by
276 a message which details the last SMB message received by smbd. This
277 info is often very useful in tracking down the problem so please
278 include it in your bug report.</P
280 >You should also detail how to reproduce the problem, if
281 possible. Please make this reasonably detailed.</P
283 >You may also find that a core file appeared in a <TT
287 subdirectory of the directory where you keep your samba log
288 files. This file is the most useful tool for tracking down the bug. To
289 use it you do this:</P
296 >adding appropriate paths to smbd and core so gdb can find them. If you
297 don't have gdb then try <KBD
300 >. Then within the debugger use the
304 > to give a stack trace of where the problem
305 occurred. Include this in your mail.</P
307 >If you known any assembly language then do a <KBD
311 where the problem occurred (if its in a library routine then
312 disassemble the routine that called it) and try to work out exactly
313 where the problem is by looking at the surrounding code. Even if you
314 don't know assembly then incuding this info in the bug report can be
323 >35.5. Attaching to a running process</A
326 >Unfortunately some unixes (in particular some recent linux kernels)
327 refuse to dump a core file if the task has changed uid (which smbd
328 does often). To debug with this sort of system you could try to attach
329 to the running process using <KBD
345 > to continue and try to cause the core dump
346 using the client. The debugger should catch the fault and tell you
347 where it occurred.</P
358 >The best sort of bug report is one that includes a fix! If you send us
359 patches please use <KBD
362 > format if your version of
363 diff supports it, otherwise use <KBD
367 your do the diff against a clean version of the source and let me know
368 exactly what version you used. </P
376 SUMMARY="Footer navigation table"
396 HREF="samba-howto-collection.html"
411 >Analysing and solving samba problems</TD
417 HREF="appendixes.html"