<<Include(Debugging/Header)>>
||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position:  98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''<<BR>><<TableOfContents>>||

= Introduction =

Samba is a complex package, because it covers a wide range of use cases and provides lots of different binary packages.

Bugs relating to the ''samba'' source package typically fall into one of the following categories:
 1. User cannot connect to (or properly access files on) a remote share from his Ubuntu system. This falls under the category of '''samba as a client'''.
 1. Other systems cannot connect to (or properly access files on) an Ubuntu system providing samba shares. This may be an issue with '''samba as a server'''.
 1. '''Install/upgrade failures''' of the samba packages.
 1. '''libpam-smbpass''' specific issues. Sharing a folder from the GUI installs libpam-smbpass, which stacks a PAM module that maintains sync between system and samba passwords. Failure in libpam-smbpass may result in inability to login on the system.
 1. '''winbind''' specific issues. Winbind allows to get user/group info from a Windows DC. It is sometimes installed by unsuspecting users as a recommended package from Wine.

Also, it is a very good idea to have a look at the official Samba [[ http://samba.org/samba/docs/man/Samba-HOWTO-Collection|HOWTO ]]. You will find there not only a how-to, but also common errors.

= How to file =

## Useful for bug-filers and as a boiler-plate advice for triagers.  This is the minimum information required for a bug report.

First figure out if the bug falls under one of the generic categories:
 1. [[ #samba-client|samba as a client ]]
 1. [[ #samba-server|samba as a server ]]
 1. [[ samba-pkg-fail|install/upgrade failure ]]
 1. libpam-smbpass related
 1. winbind related

<<Anchor(samba-client)>>
=== Samba as a client ===

==== Is it a regression ? ====

Did this use to work properly with a previous release ?

==== What version of samba packages are used ? ====

Please give the output of:
{{{
dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba
}}}

==== How is the remote share accessed from the Ubuntu system? ====
 1. nautilus (or other GUI client)
 1. smbclient (from the command line)
 1. cifs filesystem mount (from /etc/fstab or a mount command)

==== If nautilus (or another GUI client) is used to access the remote share, can the share be accessed with the smbclient command line utility ? ====

To test:
 1. install the samba-client package
 1. try to connect to the remote system from the command line:
{{{
smbclient //remote_system/share_name
}}}
If the share requires a specific username/password, try using the "-U" parameter (for example, use "-U ntdomain\\user").

==== If a cifs mount is used ====

In that case please also provide:
 * the content of the file '''/etc/fstab''', or the command line used to mount the remote share if the share is manually mounted.
 * the content of the file '''/proc/fs/cifs/DebugData'''

==== What is the remote server ? ====

In all cases, please include the output of the following smbclient command:

{{{
smbclient -L //remote_system
}}}

This should give us the remote server version. Also include on what kind of machine the share is located (Windows 2003 Server, Ubuntu 8.04, NAS box model...)

<<Anchor(samba-server)>>
=== Samba as a server ===

==== Is it a regression ? ====

Did this use to work properly with a previous release ?

==== What version of samba packages are used ? ====

Please give the output of:
{{{
dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba
}}}

==== Which clients are failing to connect? ====

Include the operating system (Windows, Ubuntu) and version (XP, Vista, 8.04) of the client systems failing to connect to the share.

==== What is the error message produced on the client? ====

==== Other information to include ====
 * the content of the '''/etc/samba/smb.conf''' file 
 * log files found in '''/var/log/samba/'''
 * the output of the '''smbclient -L //server/'''
 * the output of '''testparm -s'''

<<Anchor(samba-pkg-fail)>>
=== Install/upgrade failure ===

==== Status of samba packages on the system ====

Please give the output of:
{{{
dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba
}}}

==== Other information to include ====

 * apt and dpkg log files: '''/var/log/dpkg.log''' and '''/var/log/apt/term.log'''.
 * '''/etc/samba/smb.conf''' (or absence thereof)

In the case of an upgrade was there a prompt for a modified configuration file? If so what steps were taken.

## = Debugging procedure =

## In depth debugging procedures for this particular package or subsystem.  This usually is information about the log files to gather and what to look for in them.

= How to Triage =

## Information that will facilitate the triaging of bugs for this package or subsystem.  Remind triagers of the bug tags in use for this particular package.

Identify if the bug falls in one of the generic categories above. If so make sure that the relevant information is available. If not ask for it using one of the stock replies.

=== Samba as a client ===

If nautilus fails to connect but smbclient can successfully connect, the bug is related to nautilus. Mark the samba task Invalid and open a new task for nautilus. 

If both nautilus and smbclient can not connect, the bug is related to samba.

If cifs cannot connect the bug might be related to CIFS kernelspace (package linux) or userspace (package samba). In doubt, leave it in samba. 

== Stock Reply ==

## A stock reply to be used for initial bug reports basically asking for the stuff in "How to file".  The Bugs/Responses page should include this reply.

## StockReplyStart

==== Samba as a client ====

Use this reply if an Ubuntu system cannot access a remote samba/windows share.

{{{
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. 

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-client.
}}}


==== Samba as a server ====

Use this reply if remote clients cannot access a share provided by an Ubuntu system.

{{{
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. 

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-server.
}}}

==== Install/upgrade failure ====

Use this reply if there is a package installation/upgrade failure on the Ubuntu system.

{{{
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. 

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-pkg-fail.
}}}

## StockReplyEnd

## == How to Forward ==

## In the event that the package or subsystem has an upstream bug tracker this section should contain detailed steps to forward a bug to that tracker.  Some packages may just link to the general "How to Forward" page for another bug tracker like Gnome's bugzilla or freedesktop.org's bug tracker.

## = Known bugs =

## Description of known bug reports that may receive duplicates and how to recognise them.  This information should be obtained by looking for bugs tagged as 'metabug'. 

## '''Open'''
## ||<rowbgcolor="#eeeeee"> '''Bug''' || '''Subject''' || '''Symptom''' ||
## || [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... ||

## '''Closed'''
## ||<rowbgcolor="#eeeeee"> '''Bug''' || '''Subject''' || '''Symptom''' ||
## || [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... ||

= Non-bugs =

## How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses.

=== Install/upgrade failure due to missing /etc/samba/smb.conf file ===

==== How to recognize it ====
This is a case of install/upgrade failure that results in the following error message (potentially translated):
{{{
package samba-common <version> failed to install/upgrade: subprocess post-installation script returned error exit status 1
}}}
The DpkgTerminalLog.gz (or /var/log/apt/term.log) contains the following message:
{{{
Not replacing deleted config file /etc/samba/smb.conf
chmod: cannot access `/etc/samba/smb.conf': No such file or directory
}}}
The user should not be able to provide any /etc/samba/smb.conf file, since it is missing.

==== Stock answer ====

{{{
Thank you for taking the time to report this bug and helping to make Ubuntu better.

It looks like you manually removed /etc/samba/smb.conf before reinstalling/upgrading samba packages. Configuration files are special files that should be purged by running "apt-get purge", not manually removed.

You can recover from this situation by restoring /etc/samba/smb.conf and restart pending package configuration:
$ sudo cp /usr/share/samba/smb.conf /etc/samba/smb.conf
$ sudo dpkg --configure -a

Alternatively, you can purge samba-common completely and attempt the install/upgrade again:
$ sudo apt-get purge samba-common

This bug will be marked as Invalid: please reopen it if the above steps do not resolve the situation for you. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!
}}}

Close the bug report as Invalid.

----
CategoryBugSquad
CategoryDebugging