samba panic

Dupping multiple bugs together to hope to find the common cause even after that much time

Status changed to 'Confirmed' because the bug affects multiple users.

I was looking for similar issues and it seems every now and then these issues (<~1 per year) get reported. All seem to be against Trusty's version of samba yet none of the stack traced seemed to point me directly to the reasons.

TL;DR all your samba is crashing for something - I hope by moving all the Dups together we can either:
a) find e.g. the config option you all have that triggers this
or
b) older reporters have found a fix/workaround in the meantime to share.

How reproducible is this for you as of today?

The steps to follow are usually installing samba-dbg to get more info on the next crash.
Please provide those, but more than that if you find some steps to recreate the issue on e.g. a fresh system/VM that would be great.

samba-dbg is installed.
This happens with every system reboot.
What can I send you?

On Mon, May 15, 2017 at 12:13 PM, ChristianEhrhardt <
<email address hidden>> wrote:

> I was looking for similar issues and it seems every now and then these
> issues (<~1 per year) get reported. All seem to be against Trusty's
> version of samba yet none of the stack traced seemed to point me
> directly to the reasons.
>
> TL;DR all your samba is crashing for something - I hope by moving all the
> Dups together we can either:
> a) find e.g. the config option you all have that triggers this
> or
> b) older reporters have found a fix/workaround in the meantime to share.
>
> How reproducible is this for you as of today?
>
> The steps to follow are usually installing samba-dbg to get more info on
> the next crash.
> Please provide those, but more than that if you find some steps to
> recreate the issue on e.g. a fresh system/VM that would be great.
>
> ** Changed in: samba (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1690684
>
> Title:
> samba panic
>
> Status in samba package in Ubuntu:
> Incomplete
>
> Bug description:
> The Samba 'panic action' script, /usr/share/samba/panic-action,
> was called for PID 744 (/usr/sbin/smbd).
>
>
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/
> libthread_db.so.1".
> 0x00007f901f1f254c in __libc_waitpid (pid=861, stat_loc=stat_loc@entry=0x7fff997eeb30,
> options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31
>
> $ lsb_release -rd
> Description: Ubuntu 14.04.5 LTS
> Release: 14.04
>
> $ apt-cache policy samba
>
> samba:
> Installed: 2:4.3.11+dfsg-0ubuntu0.14.04.7
> Candidate: 2:4.3.11+dfsg-0ubuntu0.14.04.7
> Version table:
> *** 2:4.3.11+dfsg-0ubuntu0.14.04.7 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main
> amd64 Packages
> 500 http://security.ubuntu.com/ubuntu/ trusty-security/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 2:4.1.6+dfsg-1ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64
> Packages
>
> System rebooted.
> Samba reports panic, via email, twice upon reboot.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/
> 1690684/+subscriptions
>

Steps to reproduce would be best. For example, can I just apt install samba and hit the issue? did you have some sort of special configuration or turn on some feature?

It would be even better if you could do it in a LXC container, e.g.:

lxc launch ubuntu-daily:trusty t
lxc exec t bash
...
(give me the steps you use to setup samba and reproduce the issue)

Hello,

sorry, I can't help you, because
- I've updated to ubuntu 16.04. xenial
- I did use now network-connect to my (ubuntu)server via nfs insted of
samba (because I havn't a windows pc any more)
So I can't reproduce the errors any more

Christoph Theuring
P.S.
Its a long time ago I reported this bug ...

Am 17.05.2017 um 23:45 schrieb Joshua Powers:
> Steps to reproqduce would be best. For example, can I just apt install
> samba and hit the issue? did you have some sort of special configuration
> or turn on some feature?
>
> It would be even better if you could do it in a LXC container, e.g.:
>
> lxc launch ubuntu-daily:trusty t
> lxc exec t bash
> ...
> (give me the steps you use to setup samba and reproduce the issue)
>

I installed the pkg.
I did configure it to my network.
It was working for months.
Now when I reboot I get the panic email.
Would you like the config file?
some logs?

On Wed, May 17, 2017 at 4:45 PM, Joshua Powers <email address hidden>
wrote:

> Steps to reproduce would be best. For example, can I just apt install
> samba and hit the issue? did you have some sort of special configuration
> or turn on some feature?
>
> It would be even better if you could do it in a LXC container, e.g.:
>
> lxc launch ubuntu-daily:trusty t
> lxc exec t bash
> ...
> (give me the steps you use to setup samba and reproduce the issue)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1690684
>
> Title:
> samba panic
>
> Status in samba package in Ubuntu:
> Incomplete
>
> Bug description:
> The Samba 'panic action' script, /usr/share/samba/panic-action,
> was called for PID 744 (/usr/sbin/smbd).
>
>
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/
> libthread_db.so.1".
> 0x00007f901f1f254c in __libc_waitpid (pid=861, stat_loc=stat_loc@entry=0x7fff997eeb30,
> options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31
>
> $ lsb_release -rd
> Description: Ubuntu 14.04.5 LTS
> Release: 14.04
>
> $ apt-cache policy samba
>
> samba:
> Installed: 2:4.3.11+dfsg-0ubuntu0.14.04.7
> Candidate: 2:4.3.11+dfsg-0ubuntu0.14.04.7
> Version table:
> *** 2:4.3.11+dfsg-0ubuntu0.14.04.7 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main
> amd64 Packages
> 500 http://security.ubuntu.com/ubuntu/ trusty-security/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 2:4.1.6+dfsg-1ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64
> Packages
>
> System rebooted.
> Samba reports panic, via email, twice upon reboot.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/
> 1690684/+subscriptions
>

> Would you like the config file?
> some logs?

As Christian mentioned in #3 you have two options:

1) You can attempt to installing samba-dbg to get more info on the next crash
2) Get us steps and configuration files that we can use to locally reproduce the crashes and attempt to triage the issue.

Thanks

> Now when I reboot I get the panic email.

Is it always a new email about a new panic, or could it be that you are getting the same email over and over? Just checking.

> Would you like the config file?

yes, and the logs from /var/log/samba/ and any core files you might have in there.

smb.cnf

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = COMCO1

# server string is the equivalent of the NT Description field
        server string = %h server (Samba, Ubuntu)

#dfg 11/11/16
netbios name = comco76
security = domain
realm =comco1.com <http://safco1.com/>

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
interfaces = 192.168.0.4/24 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d

####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = member server

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<<email address hidden>-...

Thanks for attaching these. I see a few potential issues:

a) Your /etc/samba/smb.conf has an invalid realm setting:
 realm = comco1.com <http://safco1.com/>
It should be just comco1.com and not have that url next to it

b) The reason you are getting panic seems to be because the smbd process cannot open sockets on the specified 192.168.0.4 IP:
        interfaces = 192.168.0.4/24 eth0

b.1) Is that network correctly setup on that box?
b.2) Have ou tried 192.168.0.0/24? That would tell samba to look for any local interfaces that are attached to that CIDR.

In fact, I can reproduce your panic action by setting "interfaces =" to a list of networks and interfaces that do not exist on my test box.

Still panics.
==================

The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 751 (/usr/sbin/smbd).

This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred. The Samba log
files may contain additional information about the problem.

If the problem persists, you are encouraged to first install the
samba-dbg package, which contains the debugging symbols for the Samba
binaries. Then submit the provided information as a bug report to
Ubuntu by visiting this link:
https://launchpad.net/ubuntu/+source/samba/+filebug

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fc23ec7595c in __libc_waitpid (pid=884,
stat_loc=stat_loc@entry=0x7fffe341f4e0,
options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31

On Mon, Jul 24, 2017 at 8:02 AM, Andreas Hasenack <email address hidden>
wrote:

> Thanks for attaching these. I see a few potential issues:
>
> a) Your /etc/samba/smb.conf has an invalid realm setting:
> realm = comco1.com <http://safco1.com/>
> It should be just comco1.com and not have that url next to it
>
> b) The reason you are getting panic seems to be because the smbd process
> cannot open sockets on the specified 192.168.0.4 IP:
> interfaces = 192.168.0.4/24 eth0
>
> b.1) Is that network correctly setup on that box?
> b.2) Have ou tried 192.168.0.0/24? That would tell samba to look for any
> local interfaces that are attached to that CIDR.
>
> In fact, I can reproduce your panic action by setting "interfaces =" to
> a list of networks and interfaces that do not exist on my test box.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1690684
>
> Title:
> samba panic
>
> Status in samba package in Ubuntu:
> Incomplete
>
> Bug description:
> The Samba 'panic action' script, /usr/share/samba/panic-action,
> was called for PID 744 (/usr/sbin/smbd).
>
>
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/
> libthread_db.so.1".
> 0x00007f901f1f254c in __libc_waitpid (pid=861, stat_loc=stat_loc@entry=0x7fff997eeb30,
> options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31
>
> $ lsb_release -rd
> Description: Ubuntu 14.04.5 LTS
> Release: 14.04
>
> $ apt-cache policy samba
>
> samba:
> Installed: 2:4.3.11+dfsg-0ubuntu0.14.04.7
> Candidate: 2:4.3.11+dfsg-0ubuntu0.14.04.7
> Version table:
> *** 2:4.3.11+dfsg-0ubuntu0.14.04.7 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main
> amd64 Packages
> 500 http://security.ubuntu.com/ubuntu/ trusty-security/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 2:4.1.6+dfsg-1ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64
> Packages
>
> System rebooted.
> Samba reports panic, via email, twice upon reboot.
>
> To manage notifications about this bug go to:
> https://bugs...

# ifconfig
eth0 Link encap:Ethernet HWaddr b8:ae:ed:78:6c:da
          inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:54780 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28204 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:79262120 (79.2 MB) TX bytes:2176619 (2.1 MB)
          Interrupt:20 Memory:aa100000-aa120000

On Mon, Sep 18, 2017 at 11:21 AM, Dan Gleeson <email address hidden>
wrote:

> Still panics.
> ==================
>
> The Samba 'panic action' script, /usr/share/samba/panic-action,
> was called for PID 751 (/usr/sbin/smbd).
>
> This means there was a problem with the program, such as a segfault.
> Below is a backtrace for this process generated with gdb, which shows
> the state of the program at the time the error occurred. The Samba log
> files may contain additional information about the problem.
>
> If the problem persists, you are encouraged to first install the
> samba-dbg package, which contains the debugging symbols for the Samba
> binaries. Then submit the provided information as a bug report to
> Ubuntu by visiting this link:
> https://launchpad.net/ubuntu/+source/samba/+filebug
>
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> 0x00007fc23ec7595c in __libc_waitpid (pid=884, stat_loc=stat_loc@entry=
> 0x7fffe341f4e0, options=options@entry=0) at ../sysdeps/unix/sysv/linux/wai
> tpid.c:31
>
> On Mon, Jul 24, 2017 at 8:02 AM, Andreas Hasenack <email address hidden>
> wrote:
>
>> Thanks for attaching these. I see a few potential issues:
>>
>> a) Your /etc/samba/smb.conf has an invalid realm setting:
>> realm = comco1.com <http://safco1.com/>
>> It should be just comco1.com and not have that url next to it
>>
>> b) The reason you are getting panic seems to be because the smbd process
>> cannot open sockets on the specified 192.168.0.4 IP:
>> interfaces = 192.168.0.4/24 eth0
>>
>> b.1) Is that network correctly setup on that box?
>> b.2) Have ou tried 192.168.0.0/24? That would tell samba to look for any
>> local interfaces that are attached to that CIDR.
>>
>> In fact, I can reproduce your panic action by setting "interfaces =" to
>> a list of networks and interfaces that do not exist on my test box.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1690684
>>
>> Title:
>> samba panic
>>
>> Status in samba package in Ubuntu:
>> Incomplete
>>
>> Bug description:
>> The Samba 'panic action' script, /usr/share/samba/panic-action,
>> was called for PID 744 (/usr/sbin/smbd).
>>
>>
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthre
>> ad_db.so.1".
>> 0x00007f901f1f254c in __libc_waitpid (pid=861, stat_loc=stat_loc@entry
>> =0x7fff997eeb30, options=options@entry=0) at
>> ../sysdeps/unix/sysv/linux/waitpid.c:31
>>
>> $ lsb_release -rd
>> Description: Ubuntu 14.04.5 LTS
>> Release: 14.04
>>
>> $ apt-ca...

Have you fixed (a)?

Have you tried (b.2)?

What happens if you leave just "eth0" in the interfaces line?

Is that 192.168.0.0/24 network perhaps brought up later in the boot process, so that when samba tries to start, it doesn't exist yet?

yes. realm = comco1.com

yes. interfaces = 192.168.0.0/24 eth0
Still panics.

=================

interfaces = eth0

 Still panics.
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 731 (/usr/sbin/smbd).

This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred. The Samba log
files may contain additional information about the problem.

If the problem persists, you are encouraged to first install the
samba-dbg package, which contains the debugging symbols for the Samba
binaries. Then submit the provided information as a bug report to
Ubuntu by visiting this link:
https://launchpad.net/ubuntu/+source/samba/+filebug

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007faee76c195c in __libc_waitpid (pid=892,
stat_loc=stat_loc@entry=0x7ffc23468ea0,
options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31

On Mon, Sep 18, 2017 at 12:55 PM, Andreas Hasenack <email address hidden>
wrote:

> Have you fixed (a)?
>
> Have you tried (b.2)?
>
> What happens if you leave just "eth0" in the interfaces line?
>
> Is that 192.168.0.0/24 network perhaps brought up later in the boot
> process, so that when samba tries to start, it doesn't exist yet?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1690684
>
> Title:
> samba panic
>
> Status in samba package in Ubuntu:
> Incomplete
>
> Bug description:
> The Samba 'panic action' script, /usr/share/samba/panic-action,
> was called for PID 744 (/usr/sbin/smbd).
>
>
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/
> libthread_db.so.1".
> 0x00007f901f1f254c in __libc_waitpid (pid=861, stat_loc=stat_loc@entry=0x7fff997eeb30,
> options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31
>
> $ lsb_release -rd
> Description: Ubuntu 14.04.5 LTS
> Release: 14.04
>
> $ apt-cache policy samba
>
> samba:
> Installed: 2:4.3.11+dfsg-0ubuntu0.14.04.7
> Candidate: 2:4.3.11+dfsg-0ubuntu0.14.04.7
> Version table:
> *** 2:4.3.11+dfsg-0ubuntu0.14.04.7 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main
> amd64 Packages
> 500 http://security.ubuntu.com/ubuntu/ trusty-security/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 2:4.1.6+dfsg-1ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64
> Packages
>
> System rebooted.
> Samba reports panic, via email, twice upon reboot.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/
> 1690684/+subscriptions
>

> Now when I reboot I get the panic email.

Is it possible that eth0 is not up when samba starts? How is eth0 brought up, is it via network manager in the GUI, or via /etc/network/interfaces?

Could you paste the contents of /etc/network/interfaces here please?

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

On Wed, Sep 20, 2017 at 2:50 PM, Andreas Hasenack <email address hidden>
wrote:

> > Now when I reboot I get the panic email.
>
> Is it possible that eth0 is not up when samba starts? How is eth0
> brought up, is it via network manager in the GUI, or via
> /etc/network/interfaces?
>
> Could you paste the contents of /etc/network/interfaces here please?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1690684
>
> Title:
> samba panic
>
> Status in samba package in Ubuntu:
> Incomplete
>
> Bug description:
> The Samba 'panic action' script, /usr/share/samba/panic-action,
> was called for PID 744 (/usr/sbin/smbd).
>
>
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/
> libthread_db.so.1".
> 0x00007f901f1f254c in __libc_waitpid (pid=861, stat_loc=stat_loc@entry=0x7fff997eeb30,
> options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31
>
> $ lsb_release -rd
> Description: Ubuntu 14.04.5 LTS
> Release: 14.04
>
> $ apt-cache policy samba
>
> samba:
> Installed: 2:4.3.11+dfsg-0ubuntu0.14.04.7
> Candidate: 2:4.3.11+dfsg-0ubuntu0.14.04.7
> Version table:
> *** 2:4.3.11+dfsg-0ubuntu0.14.04.7 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main
> amd64 Packages
> 500 http://security.ubuntu.com/ubuntu/ trusty-security/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 2:4.1.6+dfsg-1ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64
> Packages
>
> System rebooted.
> Samba reports panic, via email, twice upon reboot.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/
> 1690684/+subscriptions
>

Ok, your eth0 network interface is controlled by network manager then. This means that it only becomes available after you login on your Ubuntu desktop, and that's why samba is failing: the network interface you told it to use is not available when samba starts.

You have some options:
a) do not specify the interfaces line in /etc/samba/smb.conf. This is usually only needed when you have multiple interfaces and want to control where samba will listen. I'm not sure if samba will pick up eth0 once it becomes available, you should try it.

b) Specify the eth0 interface details in /etc/network/interfaces. See the interfaces manpage with "man interfaces". Then it will be brought up during boot, and will be ready for samba when it starts.

c) Workaround: configure samba to not start automatically. You would then start it manually after you login on your desktop and the network is available.

I suggest you try (a) first, unless you have multiple interfaces and really need samba to only use eth0. Or if samba doesn't pick up your eth0 network once it's up (after you login). If that doesn't work, then you should really treat this machine like a server and go for (b). (c) is a workaround.

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]

Changing system to use /etc/network/interfaces did resolve this issue.

Thanks for getting back to us with this information.

I'll mark this bug as "invalid" because it was a local configuration issue, as samba was told to listen on an interface that didn't exist yet.