Chapter 40. Reporting Bugs

+ + Please report bugs using Samba's Bugzilla 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. @@ -12,9 +12,9 @@ we can possibly answer, so you have a much higher chance of a response and a fix if you send us a “developer-friendly” bug report that lets us fix it fast.

- - - + + + 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 @@ -24,7 +24,7 @@ that list who may be able to help you. You may also like to look though the recent mailing list archives, which are conveniently accessible on the Samba Web pages at http://samba.org/samba/. -

General Information

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 @@ -42,13 +42,13 @@ 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.

- - + + To set the debug level, use the log level in your smb.conf. 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 smb.conf file: -

log level = 10

log file = /usr/local/samba/lib/log.%m

include = /usr/local/samba/lib/smb.conf.%m

log level = 10

log file = /usr/local/samba/lib/log.%m

include = /usr/local/samba/lib/smb.conf.%m

and create a file /usr/local/samba/lib/smb.conf.machine where machine is the name of the client you wish to debug. In that file put any smb.conf commands you want; for example, log level may be useful. This also allows @@ -61,23 +61,23 @@ As the log level value is in debugging information. For most debugging operations, you may not need a setting higher than 3. Nearly all bugs can be tracked at a setting of 10, but be prepared for a large volume of log data. -

Debugging-Specific Operations

- - - - +

Debugging-Specific Operations

+ + + + 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:

log level = 0 tdb:3 passdb:5 auth:4 vfs:2

max log size = 0

log file = /var/log/samba/%U.%m.log

log level = 0 tdb:3 passdb:5 auth:4 vfs:2

max log size = 0

log file = /var/log/samba/%U.%m.log

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 log level of 0 means turn off all unnecessary debugging except the debug classes set for the functional areas as specified. The table shown in Debuggable Functions may be used to attain very precise analysis of each SMB operation Samba is conducting. -

Table 40.1. Debuggable Functions

Function Name	Function Name
all	passdb
tdb	sam
printdrivers	auth
lanman	winbind
smb	vfs
rpc_parse	idmap
rpc_srv	quota
rpc_cli	acls

Internal Errors

Table 40.1. Debuggable Functions

Function Name	Function Name
all	passdb
tdb	sam
printdrivers	auth
lanman	winbind
smb	vfs
rpc_parse	idmap
rpc_srv	quota
rpc_cli	acls

Internal Errors

If you get the message “INTERNAL ERROR” 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 @@ -91,35 +91,35 @@ include it in your bug report. You should also detail how to reproduce the problem, if possible. Please make this reasonably detailed.

- + You may also find that a core file appeared in a corefiles 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: - - + +

 $ gdb smbd core

- - + + adding appropriate paths to smbd and core so gdb can find them. If you do not have gdb, try dbx. Then within the debugger, use the command where to give a stack trace of where the problem occurred. Include this in your report.

- + If you know any assembly language, do a disass 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. -

Attaching to a Running Process

- - - +

Attaching to a Running Process

+ + + 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 @@ -145,15 +145,15 @@ of the spinning process and type:

 root#  gdb /usr/local/samba/sbin/smbd

- + then “attach `pid'” (of the spinning process), then type “bt” to get a backtrace to see where the smbd is in the call path. -

Patches

- - +

Patches

+ + The best sort of bug report is one that includes a fix! If you send us patches, please use diff -u format if your version of diff supports it; otherwise, use diff -c4. Make sure you do the diff against a clean version of the source and let me know exactly what version you used. -

Prev	Up	Next
Chapter 39. Analyzing and Solving Samba Problems	Home	Part VI. Reference Section