Bug#652679: Winbind authentication and wbinfo -i user no longer work after uprading to 3.6.1

Quoting Dale Schroeder ():

Robert,

Same problem here, and I have not seen anyone mention this on the
Samba list. Systems are fully updated and testparm does not return
any errors. idmap backend is rid notated in the new format. All
deprecated parameters have been removed.

On my systems, I have found that full functionality returns after a
reboot; however, if samba/winbind processes are restarted for any
reason, AD authentication again no longer works. As with you,
wbinfo -u/-g continues to work, as does getent passwd. getent group
only returns linux groups. Another reboot will return winbind once
again to full functionality.

Even at log level 10, error messages have been hard to find among
the many winbind logs. At the time of failure, the one I
consistently find is in syslog:
winbindd[4186]: ads_ranged_search failed with: Time limit exceeded.

Hello Dale,

Thanks for the followup.

I'll probably forward the bug upstream, as discussed with
Robert.unless someone does it beforehand (which would be a better
idea if this is someone who experiences this bug). My only problem in
this is that I'll have less time in the upcoming weeks because of
Christmas/New Year holidays. But forwarding the bug is anyway in my
TODO pile. Just feel free to do it (and mention upstream's bug here)
if you can do it before I do.









To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

On Tue, Dec 20, 2011 at 11:10 PM, Christian PERRIER wrote:

Hello Dale,

Thanks for the followup.

I'll probably forward the bug upstream, as discussed with
Robert.unless someone does it beforehand (which would be a better
idea if this is someone who experiences this bug). My only problem in
this is that I'll have less time in the upcoming weeks because of
Christmas/New Year holidays. But forwarding the bug is anyway in my
TODO pile. Just feel free to do it (and mention upstream's bug here)
if you can do it before I do.

I bisected the code and the problem was introduced in this commit:
commit a9523f17ea2cd85a130e081f3a89cffbee1fdc06
Author: Volker Lendecke
Date: Tue Jun 22 15:59:44 2010 +0200

s3: Fix a winbind crash

nss_get_info_cached might have invalidated "ads" deep inside.

So something in that patch is causing our problem.

As an aside I have to say the bisect feature of git is awesome. It is the
first time I've used it and it would have been easier on something not so
large, but it worked.

Robert


<div class="gmail_quote">On Tue, Dec 20, 2011 at 11:10 PM, Christian PERRIER <span dir="ltr">&lt;<a href="mailto:"></a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello Dale,<br>
<br>
Thanks for the followup.<br>
<br>
I&#39;ll probably forward the bug upstream, as discussed with<br>
Robert.unless someone does it beforehand (which would be a better<br>
idea if this is someone who experiences this bug). My only problem in<br>
this is that I&#39;ll have less time in the upcoming weeks because of<br>
Christmas/New Year holidays. But forwarding the bug is anyway in my<br>
TODO pile. Just feel free to do it (and mention upstream&#39;s bug here)<br>
if you can do it before I do.<br>

<br></blockquote><div><br></div><div>I bisected the code and the problem was introduced in this commit:</div><div>commit a9523f17ea2cd85a130e081f3a89cffbee1fdc06</div><div>Author: Volker Lendecke &lt;<a href="mailto:"></a>&gt;</div>
<div>Date:   Tue Jun 22 15:59:44 2010 +0200</div><div><br></div><div>    s3: Fix a winbind crash</div><div>    </div><div>    nss_get_info_cached might have invalidated &quot;ads&quot; deep inside.</div><div><br></div><div>
So something in that patch is causing our problem.</div><div><br></div><div>As an aside I have to say the bisect feature of git is awesome. It is the first time I&#39;ve used it and it would have been easier on something not so large, but it worked.</div>
<div><br></div><div>Robert </div></div>




To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact