Tags Tags

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

December 20th, 2011 - 05:50 pm ET by Dale Schroeder | Report spam
Help Create a new topic
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.


Dale





To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 2 repliesReplies Make a reply

Replies

#1 Christian PERRIER
December 21st, 2011 - 03:00 am ET | Report spam

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

Similar topics

Make your own search :