Mike Brady
2008-Apr-23 22:53 UTC
[Samba] 3.0.28a winbind fails to resolve sid-to-gid for local groups
3.0.28a winbind fails to resolve sid-to-gid for local groups. This appears to be the root cause of the problems that I reported in previous posts with usrmgr. wbinfo -G for any local group works. wbinfo -s for any local group fails. This is occurring on Centos 5.1 x86_64 using Samba 2.0.28a RPMs built from a Fedora 7 source RPM. The same OS with the Centos supplied Samba 3.0.25b packages does not have this problem when using the exact same configuration file (except for the workgroup name) and usrmgr works. But, 3.0.25b has other problems which is why I was trying the latest release. I am happy to do further tests and provide logs if someone tells me what they need. In the meantime I will be trying some of the releases in between these two to see if there is one that works for me. Thanks Mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20080424/d5b54fda/attachment.bin
Mike Brady
2008-Apr-24 20:23 UTC
[Samba] Re: 3.0.28a winbind fails to resolve sid-to-gid for local groups
It looks like 3.0.28a may be the only release with these problems. 3.0.28 works fine. Although all releases are showing failed look ups for S-1-1-0 and S-1-5-2. Do these need to be added? I have opened Bug 5414. https://bugzilla.samba.org/show_bug.cgi?id=5414 On Thu, 2008-04-24 at 10:49 +1200, Mike Brady wrote:> 3.0.28a winbind fails to resolve sid-to-gid for local groups. > > This appears to be the root cause of the problems that I reported in > previous posts with usrmgr. > > wbinfo -G for any local group works. > wbinfo -s for any local group fails. > > This is occurring on Centos 5.1 x86_64 using Samba 2.0.28a RPMs built > from a Fedora 7 source RPM. > > The same OS with the Centos supplied Samba 3.0.25b packages does not > have this problem when using the exact same configuration file (except > for the workgroup name) and usrmgr works. But, 3.0.25b has other > problems which is why I was trying the latest release. > > I am happy to do further tests and provide logs if someone tells me what > they need. > > In the meantime I will be trying some of the releases in between these > two to see if there is one that works for me. > > Thanks > > Mike