General Information: AMD Athlon 64 X2 Dual Core Processor 4600+ Fedora Core 6 x86 (not x86_64) Samba Version 3.0.23c-2 Problem: I have a nfs mount mounted to /somemountpoint and I have created a samba share using the mountpoint /somemountpoint as the path. When I attempt to access the share I get the following error in /var/log/messages and a core dump. Exception: Dec 4 09:03:40 mdct-00is-new smbd[2454]: [2006/12/04 09:03:40, 0] lib/fault.c:fault_report(41) Dec 4 09:03:40 mdct-00is-new smbd[2454]: =============================================================== Dec 4 09:03:40 mdct-00is-new smbd[2454]: [2006/12/04 09:03:40, 0] lib/fault.c:fault_report(42) Dec 4 09:03:40 mdct-00is-new smbd[2454]: INTERNAL ERROR: Signal 11 in pid 2454 (3.0.23c-2) Dec 4 09:03:40 mdct-00is-new smbd[2454]: Please read the Trouble-Shooting section of the Samba3-HOWTO Dec 4 09:03:40 mdct-00is-new smbd[2454]: [2006/12/04 09:03:40, 0] lib/fault.c:fault_report(44) Dec 4 09:03:40 mdct-00is-new smbd[2454]: Dec 4 09:03:40 mdct-00is-new smbd[2454]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf Dec 4 09:03:40 mdct-00is-new smbd[2454]: [2006/12/04 09:03:40, 0] lib/fault.c:fault_report(45) Dec 4 09:03:40 mdct-00is-new smbd[2454]: =============================================================== Dec 4 09:03:40 mdct-00is-new smbd[2454]: [2006/12/04 09:03:40, 0] lib/util.c:smb_panic(1614) Dec 4 09:03:40 mdct-00is-new smbd[2454]: PANIC (pid 2454): internal error Dec 4 09:03:40 mdct-00is-new smbd[2454]: [2006/12/04 09:03:40, 0] lib/util.c:log_stack_trace(1721) Dec 4 09:03:40 mdct-00is-new smbd[2454]: BACKTRACE: 20 stack frames: Dec 4 09:03:40 mdct-00is-new smbd[2454]: #0 smbd(log_stack_trace+0x2d) [0x3ee25d] Dec 4 09:03:40 mdct-00is-new smbd[2454]: #1 smbd(smb_panic+0x5d) [0x3ee38d] Dec 4 09:03:40 mdct-00is-new smbd[2454]: #2 smbd [0x3d9d7a] Dec 4 09:03:40 mdct-00is-new smbd[2454]: #3 [0xf2e420] Dec 4 09:03:40 mdct-00is-new smbd[2454]: #4 /lib/libc.so.6(strlen+0x33) [0x8e62d3] Dec 4 09:03:40 mdct-00is-new smbd[2454]: #5 /lib/libc.so.6(__strdup+0x25) [0x8e6015] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #6 /lib/libnsl.so.1(nis_list+0x62f) [0x6d9c5f] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #7 /lib/libnss_nisplus.so.2(_nss_nisplus_setnetgrent+0x94) [0x6a57c4] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #8 /lib/libc.so.6(innetgr+0xb6) [0x9642e6] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #9 smbd(user_in_netgroup+0x65) [0x224a65] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #10 smbd(token_contains_name_in_list+0x23d) [0x22746d] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #11 smbd(user_ok_token+0x8f) [0x22789f] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #12 smbd [0x2851ff] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #13 smbd(make_connection+0x194) [0x286914] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #14 smbd(reply_tcon_and_X+0x217) [0x24a1d7] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #15 smbd [0x281a70] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #16 smbd(smbd_process+0x7ab) [0x282b9b] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #17 smbd(main+0xbd0) [0x49c8e0] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #18 /lib/libc.so.6(__libc_start_main+0xdc) [0x88ff2c] Dec 4 09:03:41 mdct-00is-new smbd[2454]: #19 smbd [0x20cfb1] Dec 4 09:03:41 mdct-00is-new smbd[2454]: [2006/12/04 09:03:41, 0] lib/fault.c:dump_core(173) Dec 4 09:03:41 mdct-00is-new smbd[2454]: dumping core in /var/log/samba/cores/smbd Dec 4 09:03:41 mdct-00is-new smbd[2454]: Other information: I can access other samba shares on the same system just fine. I am not sure how to include the core dump. If needed/wanted please explain. If you need more information please let me know.
From https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208718: ------------------- Changing the netgroup entry to "files" simply hides the bug and allows smbd to work on machines that use local files for group information. ------------------- This is a fedora bug. Either follow that advice or change "valid users = @somegroup" to "valid users = +somegroup". Alternatively, complain loudly to the Fedora guys, if you are really using FC6 then they chose to ignore this, it was already known in FC5. Closing as invalid as it's not our bug, re-open if the hints don't help. Volker