Changing system to use /etc/network/interfaces did resolve this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690684
Title:
samba panic
To manage notifications about this bug go to:
https:/
# 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
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
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 se
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:aa10-aa12
On Mon, Sep 18, 2017 at 11:21 AM, Dan Gleeson
wrote:
> Still panics.
> ==
>
&g
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 pro
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 strin
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
wrote:
> Steps to reproduce would be best. For example, can I just apt install
> s
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 <
1690...@bugs.launchpad.net> wrote:
> I was looking for similar issues and it seems every now and then these
> issues (<~1 per year) get reported. All seem to
Public bug reported:
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".
0x7f901f1f254c in __libc_waitpid (pid=861,
s
