Panic or segfault in Samba

[Dirk]

The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 28386 (/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".
0x00007f514545607a in __GI___waitpid (pid=28387, stat_loc=stat_loc@entry=0x7ffd531d9260, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29
#0 0x00007f514545607a in __GI___waitpid (pid=28387, stat_loc=stat_loc@entry=0x7ffd531d9260, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29
#1 0x00007f51453cefbb in do_system (line=<optimized out>) at ../sysdeps/posix/system.c:148
#2 0x00007f5147e7a8d1 in smb_panic_s3 () from /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0
#3 0x00007f5148bedf1f in smb_panic () from /usr/lib/x86_64-linux-gnu/libsamba-util.so.0
#4 0x0000555be2ca7f04 in ?? ()
#5 0x00007f5146b0d917 in run_events_poll () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
#6 0x00007f5146b0db77 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
#7 0x00007f5145757d3d in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#8 0x00007f5145757edb in tevent_common_loop_wait () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#9 0x0000555be2ca6099 in main ()
A debugging session is active.

 Inferior 1 [process 28386] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]

[Andreas Hasenack (ahasenack)]

Thanks for filing this bug in Ubuntu.

Could you please attach more details to this ticket, like which Ubuntu version you are running, the samba package version, samba logs, config file, and what you were doing when the bug happened?

This command will perform many of the above tasks for you:

sudo apport-collect -p samba 1793480

Thanks

[Dirk (dbrans)]

OS ‪Ubuntu 16.04.5 LTS‬
Product Plesk Onyx
Versie 17.8.11 Update #21, laatste update op 2018-09-22 05:05

[Dirk (dbrans)]

Comand 'sudo apport-collect -p samba 1793480' does not work

[Andreas Hasenack (ahasenack)]

How does it fail?

You can alternatively manually attach the samba log files from /var/log/samba/log*, and provide the other information that was requested in comment #1

[Dirk (dbrans)]

Here is the complete log of samba

For a while we had no problems with the panic bug

[Andreas Hasenack (ahasenack)]

Thanks for the logs.

Your server seems to be out of memory. Your log.smbd.1.gz is full of errors like these:
...
   #10 /usr/sbin/smbd(_start+0x29) [0x56330c19b199]
[2018/09/23 22:27:32.935100, 0] ../source3/lib/util.c:801(smb_panic_s3)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 13702]
[2018/09/23 22:27:33.209251, 0] ../source3/lib/util.c:481(reinit_after_fork)
  messaging_reinit() failed: NT_STATUS_NO_MEMORY
[2018/09/23 22:27:33.209341, 0] ../source3/smbd/server.c:642(smbd_accept_connection)
  reinit_after_fork() failed
[2018/09/23 22:27:33.209362, 0] ../source3/lib/util.c:789(smb_panic_s3)
  PANIC (pid 13714): reinit_after_fork() failed
...

Or something else is preventing the fork() from succeeding. You could check dmesg from around that time, if it's still available, to see if the kernel logged something extra about these events.

[Launchpad Janitor (janitor)]

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