LDAP Error: POA Log Shows Attempt to Connect to Loopback Address

  • 7019907
  • 04-Feb-2010
  • 29-Aug-2017

Environment

Reload (all versions)

Situation

When attempting to login to the Reload POA, I receive a message stating that there was an LDAP failure detected. When checking the Reload POA log, I see that it is trying to use the loopback address for the LDAP Authentication Server. How can I correct this so that LDAP works? 00:00:01 344   LDAP Settings: 00:00:01 344   LDAP Server Public Bind Login ID: cn=ProxyLDAP,ou=Resources,ou=ORGUNIT,o=ORGANIZATION 00:00:01 344   Inactive Connection Timeout: 30 secs 00:00:01 344   Disable LDAP Password Change: No 00:00:01 344   LDAP Pool Server Reset Timeout: 5 mins 00:00:01 344   LDAP Server Quarantine Threshold: 2 00:00:01 344   Current LDAP Authentication mode: Load Balance Pool 00:00:01 344  Load Balance Pool Configuration: 00:00:01 344  Server Pool: LDAP DOM-JCC PO-JCC 00:00:01 344   LDAP Authentication Server IP Address: 127.0.0.1 00:00:01 344   LDAP Server Port: 389 00:00:01 344   LDAP User Authentication Method: Bind RE

Resolution

When Reload does a backup of your post office, it pulls your LDAP settings from your post office configuration, specifically, the wphost.db file. If the LDAP Authentication Server IP Address has been set to the loopback address, Reload will mirror that and you will run into this issue. To correct the problem, you will want to change the LDAP server address to the actual IP address of the LDAP server. This can be done through Console One. Select your Groupwise System, then go to Tools | GroupWise System Operations | LDAP Servers. Change the address to the actual IP address of the LDAP server. Once you have made this change, it will be reflected in new backups done by Reload. If you want to access a previous backup with this problem, then you can simply copy over the wphost.db file to the appropriate backup directory. You should now see in the log that the POA is connecting to the correct address: 13:44:36 800 LDAP Settings: 13:44:36 800   LDAP Server Public Bind Login ID: cn=ProxyLDAP,ou=Resources,ou=ORGUNIT,o=ORGANIZATION 13:44:36 800   Inactive Connection Timeout: 30 secs 13:44:36 800   Disable LDAP Password Change: No 13:44:36 800   LDAP Pool Server Reset Timeout: 5 mins 13:44:36 800   LDAP Server Quarantine Threshold: 2 13:44:36 800   Current LDAP Authentication mode: Load Balance Pool 13:44:36 800  Load Balance Pool Configuration: 13:44:36 800  Server Pool: LDAP DOM-JCC PO-JCC 13:44:36 800   LDAP Authentication Server IP Address: 10.1.10.50 13:44:36 800   LDAP Server Port: 389 13:44:36 800   LDAP User Authentication Method: Bind

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 1631.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.