Lovely samba explosive error

[Paul Howarth]

On Thu, 2006-10-26 at 16:49 +0100, Scott van Looy wrote:
> I have various mounts set up as samba shares. From windows, I can access 
> some of them (the home directory ones) but not others (the explicit ones).
> 
> Here's some snippets of smb.conf
> 
> This appears to work:
> 
> [%U]
>     comment = %U's home
>     path = /home/%U
>     public = no
>     writable = yes
>     printable = no
>     write list = %u
> 
> These two don't:
> 
> [download]
>     comment = Downloads
>     path = /download
>     public = yes
>     read only = yes
>     write list = @users
>     force group=users
>     force user=nobody
> [Music]
>     comment = Music
>     path = /var/webs/mp3
>     public = yes
>     read only = yes
>     write list = @users
>     force group=users
>     force user=nobody
> 
> All three should work, and up until a few weeks ago did work fine...
> 
> This is first a correct connection and then the error:
> 
> [2006/10/26 16:30:11, 1] smbd/service.c:make_connection_snum(941)
>    192.168.0.2 (192.168.0.2) connect to service scott initially as user 
> scott (uid=500, gid
> =10) (pid 14425)
> [2006/10/26 16:37:38, 0] lib/fault.c:fault_report(41)
>    ===============================================================
> [2006/10/26 16:37:38, 0] lib/fault.c:fault_report(42)
>    INTERNAL ERROR: Signal 11 in pid 14425 (3.0.23c-2)
>    Please read the Trouble-Shooting section of the Samba3-HOWTO
> [2006/10/26 16:37:38, 0] lib/fault.c:fault_report(44)
> 
>    From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2006/10/26 16:37:38, 0] lib/fault.c:fault_report(45)
>    ===============================================================
> [2006/10/26 16:37:38, 0] lib/util.c:smb_panic(1614)
>    PANIC (pid 14425): internal error
> [2006/10/26 16:37:38, 0] lib/util.c:log_stack_trace(1721)
>    BACKTRACE: 21 stack frames:
>     #0 smbd(log_stack_trace+0x2d) [0xe8c25d]
>     #1 smbd(smb_panic+0x5d) [0xe8c38d]
>     #2 smbd [0xe77d7a]
>     #3 [0x547420]
>     #4 /lib/libc.so.6(strlen+0x33) [0x6a92d3]
>     #5 /lib/libc.so.6(__strdup+0x25) [0x6a9015]
>     #6 /lib/libnsl.so.1(nis_list+0x62f) [0x260c5f]
>     #7 /lib/libnss_nisplus.so.2(_nss_nisplus_setnetgrent+0x94) [0x2ea7c4]
>     #8 /lib/libc.so.6(innetgr+0xb6) [0x7272e6]
>     #9 smbd(user_in_netgroup+0x65) [0xcc2a65]
>     #10 smbd(token_contains_name_in_list+0x23d) [0xcc546d]
>     #11 smbd(is_share_read_only_for_token+0x98) [0xcc5768]
>     #12 smbd(change_to_user+0x442) [0xd03eb2]
>     #13 smbd [0xd234a8]
>     #14 smbd(make_connection+0x194) [0xd24914]
>     #15 smbd(reply_tcon_and_X+0x217) [0xce81d7]
>     #16 smbd [0xd1fa70]
>     #17 smbd(smbd_process+0x7ab) [0xd20b9b]
>     #18 smbd(main+0xbd0) [0xf3a8e0]
>     #19 /lib/libc.so.6(__libc_start_main+0xdc) [0x652f2c]
>     #20 smbd [0xcaafb1]
> [2006/10/26 16:37:38, 0] lib/fault.c:dump_core(173)
>    dumping core in /var/log/samba/cores/smbd

Does this go away if you change the "write list" parameter to a list of
users instead of a group reference?

Paul.