Seen this winbindd core multiple times while stressing the samba. [2014/09/16 01:45:31.646623, 0] winbindd/winbindd.c:981(winbindd_listen_fde_handler) winbindd: Exceeding 400 client connections, no idle connection found [2014/09/16 03:54:24.541503, 0] winbindd/winbindd_dual.c:231(wb_child_request_done) removing 0x80305d2e0 from list 0x80305d160 [2014/09/16 03:54:27.104526, 0] winbindd/winbindd_dual.c:231(wb_child_request_done) removing 0x80305d2e0 from list 0x80305d2e0 [2014/09/16 04:16:48.938996, 0] winbindd/winbindd.c:212(winbindd_sig_term_handler) Got sig[15] terminate (is_parent=1) [New process 101254] [New Thread 8030021c0 (LWP 101254)] Core was generated by `winbindd'. Program terminated with signal 6, Aborted. #0 0x000000080272178c in kill () from /lib/libc.so.7 (gdb) bt #0 0x000000080272178c in kill () from /lib/libc.so.7 #1 0x000000080272058b in abort () from /lib/libc.so.7 #2 0x000000000054a611 in dump_core () at lib/fault.c:414 #3 0x000000000055a4af in smb_panic (why=<optimized out>) at lib/util.c:1133 #4 0x000000000054acb2 in fault_report (sig=<optimized out>) at lib/fault.c:53 #5 sig_fault (sig=11) at lib/fault.c:76 #6 <signal handler called> #7 0x000000000056b4a4 in tevent_queue_immediate_trigger (ev=<optimized out>, im=<optimized out>, private_data=<optimized out>) at ../lib/tevent/tevent_queue.c:143 #8 0x000000000056a030 in tevent_common_loop_immediate (ev=0x80301e110) at ../lib/tevent/tevent_immediate.c:139 #9 0x00000000005682f5 in run_events_poll (ev=0x80301e110, pollrtn=0, pfds=0x0, num_pfds=0) at lib/events.c:197 #10 0x0000000000568a19 in s3_event_loop_once (ev=0x80301e110, location=<optimized out>) at lib/events.c:331 #11 0x0000000000568e31 in _tevent_loop_once (ev=0x80301e110, location=0x8b48da "winbindd/winbindd.c:1491") at ../lib/tevent/tevent.c:494 #12 0x0000000000489b02 in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at winbindd/winbindd.c:1491 (gdb) f 7
Can you try and reproduce this against 4.1.latest please ? We did some fixes in this area, and if it doesn't fail there, then we can find out what got fixed and maybe help identify it for you. Jeremy.
(In reply to comment #1) > Can you try and reproduce this against 4.1.latest please ? We did some fixes in > this area, and if it doesn't fail there, then we can find out what got fixed > and maybe help identify it for you. > > Jeremy. HI Jeremy, Currently we are running SAMBA 3.6.12 as part of our product, and we are planning to upgrade 4.1 soon. In the mean time if there any fix available against 3.6.X would be really helpful.
closing, this is not an issue in more modern versions.