Hey list,
Having a strange issue on a new File server. This system is running the
64-bit version of Fedora 5 running kernel 2.6.20-1.2300.fc5 and version
3.0.24-1.fc5 of Samba.
This system is functioning as a backup to a primary system that is
configured the same way. Same OS, hardware, etc. After moving data over
and setting up the users and groups, I moved over the smb.conf file as
well. In the file under the primary share, I have the valid users line
set up as follows:
valid users = @cs,@it,@sales...
Using this, I add the appropriate groups that I want to give access to.
Has always worked before.
On this new system, I set it up the same way. Give access to the same
groups. Start up Samba and attempt to mount from a workstation (which
are all running WinXP Home BTW). The drive mounting hangs and eventually
fails with a permissions error. Looking at the error log on the server
shows this:
smbd[2792]:
============================================================== smbd[2792]:
[2007/03/21 14:55:53, 0] lib/fault.c:fault_report(42)
smbd[2792]: INTERNAL ERROR: Signal 11 in pid 2792 (3.0.24-1.fc5)
smbd[2792]: Please read the Trouble-Shooting section of the Samba3-HOWTO
smbd[2792]: [2007/03/21 14:55:53, 0] lib/fault.c:fault_report(44)
smbd[2792]:
smbd[2792]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
smbd[2792]: [2007/03/21 14:55:53, 0] lib/fault.c:fault_report(45)
smbd[2792]:
============================================================== smbd[2792]:
[2007/03/21 14:55:53, 0] lib/util.c:smb_panic(1621)
smbd[2792]: PANIC (pid 2792): internal error
smbd[2792]: [2007/03/21 14:55:53, 0] lib/util.c:log_stack_trace(1728)
smbd[2792]: BACKTRACE: 20 stack frames:
smbd[2792]: #0 smbd(log_stack_trace+0x1c) [0x5555557585dc]
smbd[2792]: #1 smbd(smb_panic+0x43) [0x5555557586c3]
smbd[2792]: #2 smbd [0x5555557468a2]
smbd[2792]: #3 /lib64/libpthread.so.0 [0x2aaaab8b60b0]
smbd[2792]: #4 /lib64/libc.so.6(strlen+0x30) [0x2aaaac324cb0]
smbd[2792]: #5 /lib64/libc.so.6(__strdup+0x16) [0x2aaaac3249e6]
smbd[2792]: #6 /lib64/libnsl.so.1(nis_list+0x529) [0x2aaaabf98469]
smbd[2792]: #7
/lib64/libnss_nisplus.so.2(_nss_nisplus_setnetgrent+0x8a) [0x2aaab041703a]
smbd[2792]: #8 /lib64/libc.so.6(innetgr+0xcf) [0x2aaaac3993ff]
smbd[2792]: #9 smbd(user_in_netgroup+0x6a) [0x5555555c604a]
smbd[2792]: #10 smbd(token_contains_name_in_list+0x205) [0x5555555c85c5]
smbd[2792]: #11 smbd(user_ok_token+0x84) [0x5555555c8994]
smbd[2792]: #12 smbd [0x55555561c123]
smbd[2792]: #13 smbd(make_connection+0x168) [0x55555561d358]
smbd[2792]: #14 smbd(reply_tcon_and_X+0x1fe) [0x5555555e8f7e]
smbd[2792]: #15 smbd [0x555555618fe2]
smbd[2792]: #16 smbd(smbd_process+0x720) [0x555555619ff0]
smbd[2792]: #17 smbd(main+0xa0b) [0x5555557ed44b]
smbd[2792]: #18 /lib64/libc.so.6(__libc_start_main+0xf4)
[0x2aaaac2cd784]
[2792]: #19 smbd [0x5555555b1ca9]
[2792]: [2007/03/21 14:55:53, 0] lib/fault.c:dump_core(173)
smbd[2792]: dumping core in /var/log/samba/cores/smbd
Every time something tries to connect, this entire string of errors
shows up and the machine fails to map.
After some trial and error, I changed the valid users line to comma
separated names instead of groups. Restart Samba and try again and
everything works fine.
So now I'm a bit perplexed. I can't seem to control my shares by group,
but instead need to add each and every user. Any ideas on what could be
causing this problem?
Our smb.conf file is only slightly modified from the default settings.
Name changes of course, and the primary share is set up with the
following settings:
[Share]
comment = Share
path = /Share
valid users = @Group
dos filetimes = true
writeable = yes
printable = no
create mask = 770
directory mask = 770
Again, changing the 'valid users = @Group' line to 'valid users
bob,george' fixes the problem, even though Bob and George and members of
Group.
Global options are all the default, but if need by I can post them up as
well. There are only a bunch of WinXP Home systems that connect to it,
so very little needs to be set up for things to work.
Thanks!