[RHEL5] User can't log in winbind server.
Issue
- The customer uses winbind and Active Directory for user management.
- Some users couldn't log in winbind server during about 10:30 to 11:14 (smbd and winbindd restart) on October 10.
- And the following smbd.log messages are suspected as the cause because they were logged during the period of the phenomenon.
[2012/10/10 10:22:35.936827, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
[2012/10/10 10:27:35.936954, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
[2012/10/10 10:32:35.937275, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
[2012/10/10 10:37:35.937446, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
[2012/10/10 10:42:35.938742, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
[2012/10/10 10:47:35.939441, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
[2012/10/10 10:52:35.939431, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
[2012/10/10 10:57:35.940252, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
[2012/10/10 11:02:35.940226, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
[2012/10/10 11:07:35.941063, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
[2012/10/10 11:12:35.941892, 1] winbindd/winbindd_util.c:289(trustdom_recv)
Could not receive trustdoms
- The messages, "Could not receive trustdoms" relates to this phenomenon?
- If yes, what is the root cause of the messages?
Environment
- Red Hat Enterprise Linux 5.6
- samba3x-3.5.4-0.70.el5.x86_64
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.