Chapter 35. Reporting Bugs

Jelmer R. Vernooij

The Samba Team

<jelmer@samba.org>

Someone; Tridge or Karl Auer perhaps?

27 June 1997

Table of Contents

Introduction
General info
Debug levels
Internal errors
Attaching to a running process
Patches

Introduction

Please report bugs using +Chapter 35. Reporting Bugs

Chapter 35. Reporting Bugs
Prev	Part V. Troubleshooting	Next

Chapter 35. Reporting Bugs

Jelmer R. Vernooij

The Samba Team

<jelmer@samba.org>

Andrew Tridgell

Samba Team

<tridge@samba.org>

27 June 1997

Table of Contents

Introduction
General info
Debug levels
Internal errors
Attaching to a running process
Patches

Introduction

Please report bugs using bugzilla.

Please take the time to read this file before you submit a bug report. Also, please see if it has changed between releases, as we @@ -20,7 +20,7 @@ that list that 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 info

Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that you've misconfigured something and run testparm to test your config @@ -32,42 +32,38 @@ This is very important. 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. -

Debug levels

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

-log level = 10
-log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m
-

+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

then 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 you to +log level may be useful. This also allows you to experiment with different security systems, protocol levels etc on just one machine.

-The smb.conf entry log level -is synonymous with the parameter debuglevel that has +The smb.conf entry log level +is synonymous with the parameter debuglevel that has been used in older versions of Samba and is being retained for backwards compatibility of smb.conf files.

-As the log level value is increased you will record +As the log level value is increased you will record a significantly increasing level of 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 VERY large volume of log data. -

Internal errors

If you get a INTERNAL ERROR message 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 @@ -80,13 +76,13 @@ 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
+
+$ gdb smbd core
 

 adding appropriate paths to smbd and core so gdb can find them. If you
 don't have gdb then try dbx. Then within the debugger
@@ -100,7 +96,7 @@ 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
 don't know assembly, including this info in the bug report can be
 useful. 
-

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 @@ -110,10 +106,10 @@ to the running process using Then use c to continue and try to cause the core dump using the client. The debugger should catch the fault and tell you where it occurred. -

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 34. Analysing and solving samba problems	Home	Part VI. Appendixes