Samba 'panic action' script internal error

[Bonnie]

Samba is intermittently throws a panic. However user are still able to get to shares.

Here is the email message received with the trace.

The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 23392 (/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".
0x00007f6065aad5cc in __libc_waitpid (pid=27679, stat_loc=stat_loc@entry=0x7fff2c5ae6d0, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31
#0 0x00007f6065aad5cc in __libc_waitpid (pid=27679, stat_loc=stat_loc@entry=0x7fff2c5ae6d0, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31
#1 0x00007f6065a321d2 in do_system (line=line@entry=0x7f606986f800 "/usr/share/samba/panic-action 23392") at ../sysdeps/posix/system.c:148
#2 0x00007f6065a3253a in __libc_system (line=line@entry=0x7f606986f800 "/usr/share/samba/panic-action 23392") at ../sysdeps/posix/system.c:184
#3 0x00007f6068b17235 in system (line=line@entry=0x7f606986f800 "/usr/share/samba/panic-action 23392") at pt-system.c:28
#4 0x00007f60673c7061 in smb_panic_s3 (why=<optimized out>) at ../source3/lib/util.c:798
#5 0x00007f60688efc6f in smb_panic (why=why@entry=0x7f60688fbb3b "internal error") at ../lib/util/fault.c:159
#6 0x00007f60688efe86 in fault_report (sig=<optimized out>) at ../lib/util/fault.c:77
#7 sig_fault (sig=<optimized out>) at ../lib/util/fault.c:88
#8 <signal handler called>
#9 smbd_smb2_request_reply (req=0x7f60698527e0) at ../source3/smbd/smb2_server.c:2412
#10 smbd_smb2_request_done_ex (req=req@entry=0x7f60698527e0, status=..., status@entry=..., body=..., dyn=dyn@entry=0x7f6069853fa0, location=location@entry=0x7f60686137b8 "../source3/smbd/smb2_server.c:2651") at ../source3/smbd/smb2_server.c:2584
#11 0x00007f60684f11ae in smbd_smb2_request_error_ex (req=req@entry=0x7f60698527e0, status=status@entry=..., info=0x7f6069853fa0, info@entry=0x0, location=location@entry=0x7f606861c3d0 "../source3/smbd/smb2_notify.c:122") at ../source3/smbd/smb2_server.c:2651
#12 0x00007f6068503480 in smbd_smb2_request_notify_done (subreq=0x0) at ../source3/smbd/smb2_notify.c:122
#13 0x00007f6065db5e14 in tevent_common_loop_immediate () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#14 0x00007f60673dcf7c in run_events_poll (ev=0x7f6069826380, pollrtn=0, pfds=0x0, num_pfds=0) at ../source3/lib/events.c:192
#15 0x00007f60673dd264 in s3_event_loop_once (ev=0x7f6069826380, location=<optimized out>) at ../source3/lib/events.c:303
#16 0x00007f6065db55ed in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#17 0x00007f60684df59a in smbd_process (ev_ctx=0x7f6069826380, msg_ctx=<optimized out>, sock_fd=<optimized out>, interactive=<optimized out>) at ../source3/smbd/process.c:3626
#18 0x00007f6068f53fa4 in smbd_accept_connection (ev=0x7f6069826380, fde=<optimized out>, flags=<optimized out>, private_data=<optimized out>) at ../source3/smbd/server.c:621
#19 0x00007f60673dd0ac in run_events_poll (ev=0x7f6069826380, pollrtn=<optimized out>, pfds=0x7f606983be00, num_pfds=5) at ../source3/lib/events.c:257
#20 0x00007f60673dd300 in s3_event_loop_once (ev=0x7f6069826380, location=<optimized out>) at ../source3/lib/events.c:326
#21 0x00007f6065db55ed in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#22 0x00007f6068f50b8b in smbd_parent_loop (parent=<optimized out>, ev_ctx=0x7f6069826380) at ../source3/smbd/server.c:943
#23 main (argc=<optimized out>, argv=<optimized out>) at ../source3/smbd/server.c:1577
A debugging session is active.

        Inferior 1 [process 23392] will be detached.

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

Here is the entries from the /var/log/samba/log.smbd from the time frame the email was sent:

[2015/01/14 06:46:24.886499, 3] ../source3/smbd/server.c:447(remove_child_pid)
  ../source3/smbd/server.c:447 Unclean shutdown of pid 23392
[2015/01/14 06:46:24.886590, 1] ../source3/smbd/server.c:456(remove_child_pid)
  Scheduled cleanup of brl and lock database after unclean shutdown
[2015/01/14 06:46:40.414555, 2] ../source3/smbd/server.c:437(remove_child_pid)
  Could not find child 27700 -- ignoring

[Launchpad Janitor (janitor)]

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

[padarjohn (john-meissen)]

I'm getting these several time per day.

[Christian Ehrhardt  (paelzer)]

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