[Starlingx-discuss] Is LDAP required?
Hi all, Trying to install a simplex server and I’m running in to LDAP issues. Specifically the fact that it seems to be timing out trying to connect to the server itself. This can be seen when I run “sudo bash”, which eventually reports “Can’t contact LDAP server” and authenticates me against the passwd file. slapd is definitely not running on start up. I can run “systemctl start slapd” and then see it running, but I still get this timeout error. I could remove ldap from the nsswitch.conf file but I don’t know how that will break the StarlingX insallation. Any thought or suggestions? Martin
On 2020-02-24 08:08 AM, Ward, Martin wrote:
Hi all,
Trying to install a simplex server and I’m running in to LDAP issues.
Specifically the fact that it seems to be timing out trying to connect to the server itself. This can be seen when I run “sudo bash”, which eventually reports “Can’t contact LDAP server” and authenticates me against the passwd file.
slapd is definitely not running on start up. I can run “systemctl start slapd” and then see it running, but I still get this timeout error.
I could remove ldap from the nsswitch.conf file but I don’t know how that will break the StarlingX insallation.
In a successful deployment, a ldap "admin" user is created. (not in OS users files). But I don't think this user is used by any services. So I would think it won't break anything if it's removed. Andy
Any thought or suggestions?
Martin
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr
In a successful deployment, a ldap "admin" user is created. (not in OS users files). But I don't think this user is used by any services. So I would think it won't break anything if it's removed.
Thanks Andy, perhaps the devs might want to think about removing the LDAP software, at least from the simplex controller. The less complication the better, I think. I did work out why it was failing, dodgy network settings were the issue. If anyone else comes across this issue then my solution was to start all over again and ensure that network interfaces all came up correctly and with the correct IP addresses once the VM had started up but before I configured the localhost.yml file. I basically replaced step 3 with manual commands to configure the interfaces, assign their IPs and make sure that they all worked.
participants (2)
-
Andy Ning
-
Ward, Martin