Samba smb_panic (samba-3.0.23c-1.fc5)

[Solomoriah]

I'm getting a mess of smb_panic failures with stack traces in my /var/log/messages file. I'm suspicious that the Samba update I received overnight is bad; I'm going to try to remove it and install an earlier release. Just thought I'd pass the word along.

[Solomoriah]

Okay, just downgraded to the 3.0.23a version, seems to be working.

[Mester]

How can you downgrade from 3.0.23c to 3.0.23a?

[Solomoriah]

I Googled for an FC5 repository and downloaded the previous version (all three files, samba, samba-client and samba-common). I then did:

/etc/init.d/smb stop
rpm --nodeps --erase samba samba-client samba-common

to remove the "bad" version, and then did

rpm --install samba-*

(in the directory where I downloaded the rpm's) to install the older version. Finally, I restored the smb.conf and smbusers files (which had been backed up as smb.conf.rpmsave and smbusers.rpmsave) and did:

/etc/init.d/smb start

You also should disable yum automatic updates, if you enabled them.

[Solomoriah]

I guess I should note that I have two FC5 systems, and one malfunctions badly with 3.0.23c while the other hasn't had a problem. I'm assuming something in the smb.conf of the former is tripping a bug in the software, which isn't affected by the smb.conf of the latter. Whatever. I'm going to hold on until someone else figures it out...

[mps2006]

I have the same problem:

================================================== =============
[2006/09/29 16:49:04, 0] lib/fault.c:fault_report(42)
INTERNAL ERROR: Signal 11 in pid 2437 (3.0.23c-1.fc5)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2006/09/29 16:49:04, 0] lib/fault.c:fault_report(44)

From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2006/09/29 16:49:04, 0] lib/fault.c:fault_report(45)
================================================== =============
[2006/09/29 16:49:04, 0] lib/util.c:smb_panic(1614)
PANIC (pid 2437): internal error
[2006/09/29 16:49:04, 0] lib/util.c:log_stack_trace(1721)
BACKTRACE: 20 stack frames:
#0 smbd(log_stack_trace+0x2d) [0x52e8ad]
#1 smbd(smb_panic+0x5d) [0x52e9dd]
#2 smbd [0x51a51a]
#3 [0x110420]
#4 /lib/libc.so.6(__strdup+0x1f) [0xbf8893]
#5 /lib/libnsl.so.1(nis_list+0x5d2) [0xb83b5f]
#6 /lib/libnss_nisplus.so.2(_nss_nisplus_setnetgrent+0x8f) [0x23262e]
#7 /lib/libc.so.6(innetgr+0xb2) [0xc73d05]
#8 smbd(user_in_netgroup+0x65) [0x3651e5]
#9 smbd(token_contains_name_in_list+0x23d) [0x367bdd]
#10 smbd(is_share_read_only_for_token+0x98) [0x367ed8]
#11 smbd(change_to_user+0x442) [0x3a65b2]
#12 smbd [0x3c5b38]
#13 smbd(make_connection+0x194) [0x3c6fa4]
#14 smbd(reply_tcon_and_X+0x21d) [0x38a8ed]
#15 smbd [0x3c20e0]
#16 smbd(smbd_process+0x7ab) [0x3c321b]
#17 smbd(main+0xbd0) [0x5dcf90]
#18 /lib/libc.so.6(__libc_start_main+0xdc) [0xba44e4]
#19 smbd [0x34d701]
[2006/09/29 16:49:04, 0] lib/fault.c:dump_core(173)
dumping core in /var/log/samba/cores/smbd


I get this accessing a share from both a windows client and a linux FC5 client.

It only occurs on some shares though. This is the smb.conf section for two shares that it does occur on:

[bibliotheque]
comment = Bibliotheque electronique CEDAMM
path = /ShareRoot/bibliotheque
public = yes
read only = yes
write list = @biblio
force group = biblio
force user = malc

[admin]
comment = Shared administrative files
path = /ShareRoot/admin
public = no
valid users = malc Max kath
writeable = yes
read only = no
write list = @admin
force group = admin
force user = malc
create mask = 0770
directory mask =0770

and this is one that it still works fine:

[public files]
comment = Open to everyone to share documents
path = /ShareRoot/public
writeable = yes
browseable = yes
guest ok = yes
force group = public
force user = malc


Going to try following your instructions to revert!!

malcolm

[Mester]

I found the the @ sign cause the problem. With the following lines in a share it doesn't work:

valid users = @groupname
printer admins = @groupname
writelist = @groupname

If I replace @groupname with the complet user list of the group spearated by comas it works fine.

[Duli]

Hi guys, it seems that version 3.0.23c-1.fc5 has a problem.

I would appreciate if someone could help to fix the problem without having to downgrade samba.

Cheers.
Duli

[paulez]

You may consider the solution given by Mester, I had the same problem and his solution worked.
But I hope this problem will be fixed soon, because it isn't very easy to modify each line of smb.conf instead of adding or deleting an user of a group.

[Mester]

But for me replacing with users list is not a solution. I have more than 10 groups some of them have more than 100 users.

How can I use the patch?

[mps2006]

I followed Solomoraih's instruction for 'downgrading' and all works fine now - took less than 5 minutes to resolve.

thanks Solomoraih!

[Mester]

While removing samba I lost all my domain group assigments. Can someone tell me where these infos are stored? I speak about the assigments made by the "net groupmap add" command.

Did anyone else had the same problem while downgrading?

[Duli]

Mester, I received a message saying the patch has nothing to do with this problem...

For a while, I think your solution about the "@" is the best one.

In fact, I removed all the @ and it worked. Thanks a lot for the help.

Cheers


-----------

New solution found:

Try to use +groupname instead of @groupname in smb.conf.

According to Volker Lendecke, from samba.org, if you´re not using NIS it should lead to the same results.

https://bugzilla.samba.org/show_bug.cgi?id=4145

It workd for me.

Cheers.
Duli

[irie111]

Yeah... I upgraded to 3.0.23c last night using Yum... I was spinning my wheels for awhile trying to figure out what was going on... This is definitely a major inconvenience for servers with large user databases and multiple groups... ... For now I downgraded to 3.0.23a until someone figures out another way to add groups to the valid users option or until a new version of Samba fixes this issue... Thank you for the forum... I was very pleased to find out I wasn’t the only one with a cursed Samba box... ... Continue to post any new info as you get it and I will do the same...

[Duli]

Hello all,

I´ve filed a bug report at Red Hat bugzilla

https://bugzilla.redhat.com/bugzilla....cgi?id=208718

Let´s hope someone fixes the problem as soon as possible!


Cheers
Duli