Samba (@Precise 2:3.6.3-2ubuntu2.8) segfaults randomly

Bug #1256868 reported by castle.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu 12.04.03 64Bit
samba: 2:3.6.3-2ubuntu2.8

 *** 2:3.6.3-2ubuntu2.8 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages
        100 /var/lib/dpkg/status
     2:3.6.3-2ubuntu2 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

- Sambashares still work but i get this samba-panic-action script every 2-5 days

- Nothing at syslog

- Output of samba-panic-action script:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fd5a4f24c8e in waitpid () from /lib/x86_64-linux-gnu/libc.so.6
#0 0x00007fd5a4f24c8e in waitpid () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007fd5a4eaa29e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00007fd5a82fbc5c in smb_panic (why=<optimized out>) at lib/util.c:1123
#3 0x00007fd5a82ecef8 in fault_report (sig=11) at lib/fault.c:53
#4 sig_fault (sig=11) at lib/fault.c:76
#5 <signal handler called>
#6 0x00007fd5a4eee111 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7 0x00007fd5a82d1c7e in rep_strlcpy (d=0x7fff940b3454 "", s=0x0, bufsize=256) at ../lib/replace/replace.c:70
#8 0x00007fd5a83084d4 in connections_fetch_entry (mem_ctx=0x7fd5a94f39d0, conn=0x7fd5a94e5b10, name=0x0) at lib/conn_tdb.c:63
#9 0x00007fd5a7fea10c in yield_connection (conn=0x7fd5a94e5b10, name=0x0) at smbd/connection.c:37
#10 0x00007fd5a805eff3 in close_cnum (conn=0x7fd5a94e5b10, vuid=100) at smbd/service.c:1350
#11 0x00007fd5a801831d in reply_tdis (req=0x7fd5a94f3ab0) at smbd/reply.c:5105
#12 0x00007fd5a8059fd4 in switch_message (type=113 'q', req=0x7fd5a94f3ab0, size=39) at smbd/process.c:1574
#13 0x00007fd5a805a3eb in construct_reply (deferred_pcd=0x0, encrypted=false, seqnum=<optimized out>, unread_bytes=0, size=39, inbuf=0x0, sconn=0x7fd5a94cd5e0) at smbd/process.c:1610
#14 process_smb (sconn=0x7fd5a94cd5e0, inbuf=<optimized out>, nread=39, unread_bytes=0, seqnum=<optimized out>, encrypted=false, deferred_pcd=0x0) at smbd/process.c:1688
#15 0x00007fd5a805a803 in smbd_server_connection_read_handler (conn=0x7fd5a94cd5e0, fd=8) at smbd/process.c:2317
#16 0x00007fd5a830b91e in run_events_poll (num_pfds=3, pfds=0x7fd5a94d7470, pollrtn=<optimized out>, ev=0x7fd5a94cd520) at lib/events.c:286
#17 run_events_poll (ev=0x7fd5a94cd520, pollrtn=<optimized out>, pfds=0x7fd5a94d7470, num_pfds=3) at lib/events.c:184
#18 0x00007fd5a805bf72 in smbd_server_connection_loop_once (conn=0x7fd5a94cd5e0) at smbd/process.c:1017
#19 smbd_process (sconn=0x7fd5a94cd5e0) at smbd/process.c:3158
#20 0x00007fd5a856978f in smbd_accept_connection (ev=<optimized out>, fde=<optimized out>, flags=<optimized out>, private_data=<optimized out>) at smbd/server.c:511
#21 0x00007fd5a830b91e in run_events_poll (num_pfds=5, pfds=0x7fd5a94ed4f0, pollrtn=<optimized out>, ev=0x7fd5a94cd520) at lib/events.c:286
#22 run_events_poll (ev=0x7fd5a94cd520, pollrtn=<optimized out>, pfds=0x7fd5a94ed4f0, num_pfds=5) at lib/events.c:184
#23 0x00007fd5a830baba in s3_event_loop_once (ev=0x7fd5a94cd520, location=<optimized out>) at lib/events.c:349
#24 0x00007fd5a830c640 in _tevent_loop_once (ev=0x7fd5a94cd520, location=0x7fd5a876e497 "smbd/server.c:844") at ../lib/tevent/tevent.c:494
#25 0x00007fd5a7fda060 in smbd_parent_loop (parent=<optimized out>) at smbd/server.c:844
#26 main (argc=<optimized out>, argv=<optimized out>) at smbd/server.c:1326
A debugging session is active.

 Inferior 1 [process 26071] will be detached.

Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I've found previous reports of this bug, so have marked this as a duplicate.

It might be worth speaking to upstream about this in the existing upstream bug, since I don't think they could reproduce this bug reliably, and it seems you can.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.