Didn't find the ldap server!

#1

NethServer Version: 7.8.2003 (final)

Users had login problems after I upgraded to the latest Nethserver version a couple of days ago, so I checked “Domain accounts” but got a “Could not connect to accounts provider!” message

Went to “Active Directory local accounts provider” and all the setting is there, it’s supposed to be running as ad.mydomain and with an IP for the Domain Controller I can’t reach with a ping (172.16.1.3)

I have to mention I use another host as DNS server.
I checked out nsdc and sssd services, both are running.

But:

net ads info -d3

[snip]
added interface bond0 ip=172.16.1.2 bcast=172.16.255.255 netmask=255.255.0.0
added interface br0 ip=172.16.1.5 bcast=172.16.255.255 netmask=255.255.0.0 
get_dc_list: preferred server list: ", nsdc-host.ad.domain"
resolve_hosts: Attempting host lookup for name nsdc-host.ad.domain<0x20>
resolve_hosts: getaddrinfo failed for name nsdc-host.ad.domain [Name or service not known]
ads_find_dc: falling back to netbios name resolution for domain 'MYDOMAIN' (realm 'AD.MYDOMAIN')
ads_connect: No logon servers are currently available to service the logon request.
[snip]

Didn't find the ldap server!
return code = -1

/etc/hosts:

172.16.1.2     host.mydomain host hostalias host.ad.mydomain
172.16.1.5     host.mydomain host hostalias host.ad.mydomain

Note there’s no line for ad.mydomain nor for 172.16.1.3 and interface vb-nsdc has no assigned IP…

I would like to know how to check ldap service and samba, which commands may be helpful?

TIA for your help.

#2

Here are some:

systemctl status -l nsdc
systemctl status -l sssd
systemctl status -l smwingsd
account-provider-test dump
journalctl  -M nsdc
#4

Hi,

I have no clue on how to debug this problem, nsdc seems to be working but without backend…

I dettached from domain controller with

config setprop sssd Provider none
signal-event nethserver-sssd-leave

Then I checked DNS with:

# host -t SRV _ldap._tcp.$(config getprop sssd Realm)

and I got:

Host _ldap._tcp.AD.MYDOMAIN not found: 3(NXDOMAIN)

Any help would be very appreciated.

#5

My mistake,

I was testing to use our LAN DNS, restoring it to 127.0.0.1 it works again.

I’m working now in rejoining.

#6

Solved. I don’t know how in the middle of the process after dettaching domain an re-attaching to it ldap began working.

Between those procedures sssd.conf became empty file I suppose ldap backend became available after that because some file invoked by sssd.conf was broken?

HTH someone else, greetings.