Centrify Express and Samba -- migrated to new domain
2 weeks ago
We have a server running Centrify Express and Samba. After migrating the server to a new domain (which ran with out any issues -- the server is happily a member of the new domain), winbindd crashes on start up with the following error: Could not fetch our SID - did we join?
-- log.winbindd Logs --
[2018/12/06 07:35:25.844382, 0] winbindd/winbindd.c:212(winbindd_sig_term_handler)
Got sig terminate (is_parent=1)
[2018/12/06 07:35:26, 0] winbindd/winbindd.c:1354(main)
winbindd version 3.6.22-cdc-4.5.7-403 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2018/12/06 07:35:26.318376, 0] winbindd/winbindd_cache.c:3169(initialize_winbindd_cache)
initialize_winbindd_cache: clearing cache and re-creating with version number 2
[2018/12/06 07:35:26.321088, 0] winbindd/winbindd_util.c:635(init_domain_list)
Could not fetch our SID - did we join?
[2018/12/06 07:35:26.321252, 0] winbindd/winbindd.c:1114(winbindd_register_handlers)
unable to initialize domain list
I was hoping someone might be able to point me in the right direction to fix this.
Solved! Go to Solution.
a week ago
Welcome to the Centrify forums.
Note that we provide our own IDMapper (adbindproxy) that allows samba resolve UNIX identity data supplied by our client.
Not being a samba expert, I can't tell you what's wrong with it (or why it's in use in your configuration), however I do know that if the system was running adbindproxy in a different domain before, it has to be re-configured.
Did you re-run the adbindproxy.pl script after moving to a new domain?