Created attachment 8850 [details] Find attached an archive with my log.wb-{servername}, a coredump file, and the global part of my smb.conf. After I updated one of our file-/printserver to 3.6.14, winbind crashed 4 times in 2 minutes. After restarting, I had several winbind segfaults and core dumps, too in a short time. So I downgraded back to 3.6.13 and everything was fine again. [2013/05/05 21:39:48.537056, 0] lib/fault.c:51(fault_report) =============================================================== [2013/05/05 21:39:48.537099, 0] lib/util.c:1117(smb_panic) PANIC (pid 731): internal error [2013/05/05 21:39:48.540717, 0] lib/util.c:1221(log_stack_trace) BACKTRACE: 19 stack frames: #0 /usr/sbin/winbindd(log_stack_trace+0x1c) [0x7f4440e2fb2c] #1 /usr/sbin/winbindd(smb_panic+0x55) [0x7f4440e2fc2e] #2 /usr/sbin/winbindd(+0x18bb97) [0x7f4440e21b97] #3 /lib64/libc.so.6(+0x3491c32920) [0x7f443e6b4920] #4 /usr/sbin/winbindd(+0xd484a) [0x7f4440d6a84a] #5 /usr/sbin/winbindd(+0xdc698) [0x7f4440d72698] #6 /usr/sbin/winbindd(_wbint_LookupRids+0x78) [0x7f4440d8d53c] #7 /usr/sbin/winbindd(+0x100462) [0x7f4440d96462] #8 /usr/sbin/winbindd(winbindd_dual_ndrcmd+0xfb) [0x7f4440d8c503] #9 /usr/sbin/winbindd(+0xf5533) [0x7f4440d8b533] #10 /usr/sbin/winbindd(+0xf57ab) [0x7f4440d8b7ab] #11 /usr/sbin/winbindd(+0x1aa539) [0x7f4440e40539] #12 /usr/sbin/winbindd(tevent_common_loop_immediate+0x128) [0x7f4440e3f10c] #13 /usr/sbin/winbindd(run_events_poll+0x3c) [0x7f4440e3d57a] #14 /usr/sbin/winbindd(+0x1a7c99) [0x7f4440e3dc99] #15 /usr/sbin/winbindd(_tevent_loop_once+0x82) [0x7f4440e3e048] #16 /usr/sbin/winbindd(main+0xb84) [0x7f4440d668db] #17 /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f443e6a0cdd] #18 /usr/sbin/winbindd(+0xcdea9) [0x7f4440d63ea9] [2013/05/05 21:39:48.541123, 0] lib/util.c:1122(smb_panic) smb_panic(): calling panic action [/usr/local/bin/panic-action 731] [2013/05/05 21:39:48.548982, 0] lib/util.c:1130(smb_panic) smb_panic(): action returned status 0 [2013/05/05 21:39:48.549065, 0] lib/fault.c:372(dump_core) dumping core in /var/log/samba/cores/winbindd The libnss_winbind.so file was copied to /lib and ldconfig executed, like after every update. This server is member in a Samba 4.0.5 AD.
Can you get a debug level 10 log of this and install debug symbols, so that the backtrace contains line numbers? Thanks
In your smb.conf you have some panic action set. Can you do a "bt full" from that panic action script, or do a "sleep 9999" there, attach with gdb. The corefile is only useful on a system that matches yours 100%. Volker
Created attachment 8855 [details] log.wb-GENOME
Created attachment 8856 [details] gdb bt full output
Created attachment 8857 [details] Patch Can you try the attached patch?
Compiled with patch and running now since almost 1h without any segfaults. Looks good at the moment. But I'll give tomorrow a final feedback.
No more segfaults/panics appeared with your patch. Thanks.
Created attachment 8860 [details] Patch for master
(In reply to comment #8) > Created attachment 8860 [details] > Patch for master Looks good to me. I just pushed it to autobuild.
Created attachment 8867 [details] Patch for 3.6
Created attachment 8868 [details] Patch for 4.0
This is a defect that I would call a regression from 3.6.13 to 3.6.14.
Pushed to v3-6-test and autobuild-v4-0-test.
Samba 3.6.15 will be shipped today to address this defect.
Pushed to v4-0-test.
Samba 3.6.15 is out including the fix. Closing out bug report. Thanks a lot!
*** Bug 9847 has been marked as a duplicate of this bug. ***