Hello, I just installed 398-ds on an Amazon Linux EC2. I performed a "typical" setup, with what I thought were completely "standard" choices during the set-up process. The directory server appears to be working... it's listening on the correct ports, it's responding to queries. That being said, I cannot connect to it using the Windows 389-ds console -- it gets stuck on "Initializing" and says "Cannot connect to the Directory Server" and lists the correct URL, or when I use Chrome to access the 9830 URL -- the first page renders, and I can open the Administration Express page, which shows the Administrative and Directory servers. But.. If I click on Server Info for either, I get an error. I have noted the following errors in the admin-server log... [Mon Apr 03 15:50:31 2017] [error] Could not bind as []: ldap error -1: Can't contact LDAP server [Mon Apr 03 15:50:31 2017] [error] Could not bind as []: ldap error -1: Can't contact LDAP server [Mon Apr 03 15:50:31 2017] [warn] Unable to bind as LocalAdmin to populate LocalAdmin tasks into cache. [Mon Apr 03 15:50:31 2017] [notice] Access Host filter is: *.mymobilitycentral.com [Mon Apr 03 15:50:31 2017] [notice] Access Address filter is: * [Mon Apr 03 15:50:32 2017] [notice] Apache/2.2.31 (Unix) configured -- resuming normal operations [Mon Apr 03 15:50:32 2017] [error] Could not bind as []: ldap error -1: Can't contact LDAP server [Mon Apr 03 15:50:32 2017] [error] Could not bind as []: ldap error -1: Can't contact LDAP server [Mon Apr 03 15:50:32 2017] [warn] Unable to bind as LocalAdmin to populate LocalAdmin tasks into cache. [Mon Apr 03 15:50:32 2017] [notice] Access Host filter is: *.mymobilitycentral.com [Mon Apr 03 15:50:32 2017] [notice] Access Address filter is: * Any idea what is going on? Thank you! _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
