I have Samba 2.2.3a and Winbind running with an NT 4.0 PDC and seems to be working great with the exception of 1 or 2 problems. 1) I can assign NT global group ownership to a file or directory and everything works fine. However, when I assign local linux group ownership to the file or directory, add the NT domain global group to the local linux group then I lose my rights to the file or directory. getent passwd and getent group list both local and domain users and groups, however, wbinfo -u and -g list only NT domain users and groups. 2) My winbindd daemon crashes about once per day. It stays resident in memory but stops working. If I kill it and rerun it then all is well again. Any help would sure be appreciated. Doug
DICKENS,CARY (HP-Loveland,ex2)
2002-Feb-11 15:15 UTC
[Samba] local linux groups and winbindd dies
> Doug wrote: > > 1) I can assign NT global group ownership to a file or directory and > everything works fine. However, when I assign local linux > group ownership to > the file or directory, add the NT domain global group to the > local linux > group then I lose my rights to the file or directory. getent > passwd and > getent group list both local and domain users and groups, > however, wbinfo -u > and -g list only NT domain users and groups.As far as I'm aware, wbinfo -ug is returning what it is supposed to. I don't think this is the problem. Someone please correct me if I'm wrong.> 2) My winbindd daemon crashes about once per day. It stays resident in > memory but stops working. If I kill it and rerun it then all > is well again.Mine are doing the same thing. Can you check the running size when you start it and also as it gets older? winbindd grows over time (looks like a leak, but I'm not willing to say that yet). I'm looking into why, but have no answers. If someone has an idea about what this might be, I'd be happy to chat with you and do what I can to help find this. Cary
There is a horrbile memory leak in winbind with 2.2.2 but this has been fixed in 2.2.3. However, something else has been unfixed as I have been getting the same problem as Doug with winbindd simply dying on its feet. The absence of replies to my postings (see Sunday's) implied that no one else was getting this so I am pleased (sorry Doug) that Doug is also having the same problem. If I switch back to using the winbindd/wbinfo binaries from 2.2.2 then authntication works fine and I just have to auto-restart winbindd once a day when it grows too big. 2.2.3a just gives up though. Doug, what are you getting in your log.winbindd ? I get a decent period of nothing which is good and then start to get complaints about being unable to get the sid for the domain. Noel> 2) My winbindd daemon crashes about once per day. It stays resident in > memory but stops working. If I kill it and rerun it then all > is well again.Mine are doing the same thing. Can you check the running size when you start it and also as it gets older? winbindd grows over time (looks like a leak, but I'm not willing to say that yet). I'm looking into why, but have no answers. If someone has an idea about what this might be, I'd be happy to chat with you and do what I can to help find this. Cary -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Hi there Noel, It's funny your having the same problems. I was thinking that 2.2.3 fixed the Winbindd memory leak problems too. But when I upgraded to Samba 2.2.3 the whole configuration started to behave funny (first joining to the domain correctly and then later complaining that the sid was no good etc. etc.) I tried to get things running for an hour or two, but still nothing. So now I'm back to Samba 2.2.2... But the funny thing is: Winbindd has not died on me yet since I did the 2.2.2 -> 2.2.3 -> 2.2.2 switch. Something must have changed, but I have not figured out what that is for now (no time). I think it's the PAM library though... (not sure) Anyway, I'm "glad" that I'm not th eonly one having the problems... Sincerely, Martijn Tigchelaar. -----Original Message----- From: Noel Kelly [mailto:nkelly@tarsus.co.uk] Sent: Tuesday, February 12, 2002 7:24 AM To: 'DICKENS,CARY (HP-Loveland,ex2)'; 'Doug Aldridge' Cc: samba@lists.samba.org Subject: RE: [Samba] local linux groups and winbindd dies There is a horrbile memory leak in winbind with 2.2.2 but this has been fixed in 2.2.3. However, something else has been unfixed as I have been getting the same problem as Doug with winbindd simply dying on its feet. The absence of replies to my postings (see Sunday's) implied that no one else was getting this so I am pleased (sorry Doug) that Doug is also having the same problem. If I switch back to using the winbindd/wbinfo binaries from 2.2.2 then authntication works fine and I just have to auto-restart winbindd once a day when it grows too big. 2.2.3a just gives up though. Doug, what are you getting in your log.winbindd ? I get a decent period of nothing which is good and then start to get complaints about being unable to get the sid for the domain. Noel> 2) My winbindd daemon crashes about once per day. It stays resident in > memory but stops working. If I kill it and rerun it then all is well > again.Mine are doing the same thing. Can you check the running size when you start it and also as it gets older? winbindd grows over time (looks like a leak, but I'm not willing to say that yet). I'm looking into why, but have no answers. If someone has an idea about what this might be, I'd be happy to chat with you and do what I can to help find this. Cary -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Yes I have found that you can simply insert the 2.2.2 winbindd/wbinfo binaries into a running 2.2.3a system (ie leaving the the PAM library from 2.2.3a in place) and it all works fine - bar the memory leak of course..... I am going to persist with the 2.2.3a winbindd for the moment though and reload it automatically when it dies (about 2-3 times a day). Noel -----Original Message----- From: m.o.tigchelaar@kpn.com [mailto:m.o.tigchelaar@kpn.com] Sent: 12 February 2002 10:31 To: nkelly@tarsus.co.uk Cc: samba@lists.samba.org Subject: RE: [Samba] local linux groups and winbindd dies Hi there Noel, It's funny your having the same problems. I was thinking that 2.2.3 fixed the Winbindd memory leak problems too. But when I upgraded to Samba 2.2.3 the whole configuration started to behave funny (first joining to the domain correctly and then later complaining that the sid was no good etc. etc.) I tried to get things running for an hour or two, but still nothing. So now I'm back to Samba 2.2.2... But the funny thing is: Winbindd has not died on me yet since I did the 2.2.2 -> 2.2.3 -> 2.2.2 switch. Something must have changed, but I have not figured out what that is for now (no time). I think it's the PAM library though... (not sure) Anyway, I'm "glad" that I'm not th eonly one having the problems... Sincerely, Martijn Tigchelaar. -----Original Message----- From: Noel Kelly [mailto:nkelly@tarsus.co.uk] Sent: Tuesday, February 12, 2002 7:24 AM To: 'DICKENS,CARY (HP-Loveland,ex2)'; 'Doug Aldridge' Cc: samba@lists.samba.org Subject: RE: [Samba] local linux groups and winbindd dies There is a horrbile memory leak in winbind with 2.2.2 but this has been fixed in 2.2.3. However, something else has been unfixed as I have been getting the same problem as Doug with winbindd simply dying on its feet. The absence of replies to my postings (see Sunday's) implied that no one else was getting this so I am pleased (sorry Doug) that Doug is also having the same problem. If I switch back to using the winbindd/wbinfo binaries from 2.2.2 then authntication works fine and I just have to auto-restart winbindd once a day when it grows too big. 2.2.3a just gives up though. Doug, what are you getting in your log.winbindd ? I get a decent period of nothing which is good and then start to get complaints about being unable to get the sid for the domain. Noel> 2) My winbindd daemon crashes about once per day. It stays resident in > memory but stops working. If I kill it and rerun it then all is well > again.Mine are doing the same thing. Can you check the running size when you start it and also as it gets older? winbindd grows over time (looks like a leak, but I'm not willing to say that yet). I'm looking into why, but have no answers. If someone has an idea about what this might be, I'd be happy to chat with you and do what I can to help find this. Cary -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba