# 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-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
>>
>
>