The Samba 'panic action'

[lucas toni]

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007f634df2d07a in __GI___waitpid (pid=5836, stat_loc=stat_loc@entry=0x7ffe40614a10, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29
#0 0x00007f634df2d07a in __GI___waitpid (pid=5836, stat_loc=stat_loc@entry=0x7ffe40614a10, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29
#1 0x00007f634dea5fbb in do_system (line=line@entry=0x55fd84f5f1e0 "/usr/share/samba/panic-action 5823") at ../sysdeps/posix/system.c:148
#2 0x00007f634dea639a in __libc_system (line=line@entry=0x55fd84f5f1e0 "/usr/share/samba/panic-action 5823") at ../sysdeps/posix/system.c:184
#3 0x00007f63509518d1 in smb_panic_s3 (why=<optimized out>) at ../source3/lib/util.c:802
#4 0x00007f63516c4f1f in smb_panic (why=why@entry=0x7f6351708ab8 "internal error") at ../lib/util/fault.c:166
#5 0x00007f63516c5136 in fault_report (sig=<optimized out>) at ../lib/util/fault.c:83
#6 sig_fault (sig=<optimized out>) at ../lib/util/fault.c:94
#7 <signal handler called>
#8 smbXsrv_session_create (conn=conn@entry=0x55fd84f5d470, now=now@entry=132028410914413440, _session=_session@entry=0x7ffe406153b0) at ../source3/smbd/smbXsrv_session.c:1158
#9 0x00007f6351256643 in reply_sesssetup_and_X (req=req@entry=0x55fd84f5db70) at ../source3/smbd/sesssetup.c:953
#10 0x00007f6351292e67 in switch_message (type=<optimized out>, req=req@entry=0x55fd84f5db70) at ../source3/smbd/process.c:1649
#11 0x00007f6351294bb3 in construct_reply (deferred_pcd=0x0, encrypted=false, seqnum=0, unread_bytes=0, size=76, inbuf=0x0, xconn=0x55fd84f5d470) at ../source3/smbd/process.c:1685
#12 process_smb (xconn=xconn@entry=0x55fd84f5d470, inbuf=<optimized out>, nread=76, unread_bytes=0, seqnum=0, encrypted=<optimized out>, deferred_pcd=0x0) at ../source3/smbd/process.c:1932
#13 0x00007f635129621c in smbd_server_connection_read_handler (xconn=0x55fd84f5d470, fd=38) at ../source3/smbd/process.c:2531
#14 0x00007f634f5e4917 in run_events_poll (ev=0x55fd84f43d90, pollrtn=<optimized out>, pfds=0x55fd84f5cf80, num_pfds=4) at ../source3/lib/events.c:257
#15 0x00007f634f5e4b77 in s3_event_loop_once (ev=0x55fd84f43d90, location=<optimized out>) at ../source3/lib/events.c:326
#16 0x00007f634e22ed3d in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#17 0x00007f634e22eedb in tevent_common_loop_wait () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#18 0x00007f6351297578 in smbd_process (ev_ctx=0x55fd84f43d90, msg_ctx=<optimized out>, sock_fd=38, interactive=<optimized out>) at ../source3/smbd/process.c:4032
#19 0x000055fd84191e12 in smbd_accept_connection (ev=0x55fd84f43d90, fde=<optimized out>, flags=<optimized out>, private_data=<optimized out>) at ../source3/smbd/server.c:646
#20 0x00007f634f5e4917 in run_events_poll (ev=0x55fd84f43d90, pollrtn=<optimized out>, pfds=0x55fd84f5cf80, num_pfds=6) at ../source3/lib/events.c:257
#21 0x00007f634f5e4b77 in s3_event_loop_once (ev=0x55fd84f43d90, location=<optimized out>) at ../source3/lib/events.c:326
#22 0x00007f634e22ed3d in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#23 0x00007f634e22eedb in tevent_common_loop_wait () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#24 0x000055fd84190099 in smbd_parent_loop (parent=0x55fd84f4bc70, ev_ctx=0x55fd84f43d90) at ../source3/smbd/server.c:1011
#25 main (argc=<optimized out>, argv=<optimized out>) at ../source3/smbd/server.c:1663
A debugging session is active.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

[Andreas Hasenack (ahasenack)]

This may be https://bugzilla.samba.org/show_bug.cgi?id=13315, found also in https://bugzilla.samba.org/show_bug.cgi?id=13315, but we don't even have the crash file and I can't reproduce it at the moment by just connecting using SMB1: it won't crash.