Article ID: 114921, created on Oct 9, 2012, last review on Jan 9, 2016

  • Applies to:
  • Operations Automation

Symptoms

Qmail related tasks fail in POA with the error message "Can't contact LDAP server" like in the example below:

Task name    Add mailname 'john' for domain 'customer.com', hosting #3
Task description    Add mailname 'john' for domain 'customer.com', hosting #3
Last execution output    LDAP returned error code -1, saying Can't contact LDAP server

Cause

The LDAP server used in Qmail hosting is down or unreachable from the POA Management Node.

Resolution

Check if the LDAP server is up and running.

  1. Log into POA Provider Control Panel

  2. Go to Service Director > Shared Hosting Manager > Qmail Services

  3. Find the IP address of the LDAP server(s) in the LDAP server address field

  4. Log into the LDAP server using SSH as root

  5. Check status of the LDAP service:

    # /etc/init.d/ldap status
    
  6. If you see that LDAP service is stopped - start it:

    # /etc/init.d/ldap start
    

Refer to the Odin Knowledgebase article if LDAP server cannot start due to corrupted database.

If the LDAP service is up and running check if POA can connect to the LDAP server:

  1. Log into POA Management Node (MN) using SSH or RDP

  2. Check connectivity from the POA MN to the port 389 of LDAP server using e.g. the telnet utility:

    telnet LDAP_SERVER_P 389
    

Replace LDAP_SERVER_IP in the command above with the actual IP address of the LDAP server which you found in the POA Provider Control Panel.

If the POA Management Node cannot connect to the port 389 of LDAP server then check firewall and routing settings in the network infrastructure.

In case slapd.log is absent - configure it, using this guide.

Search Words

qmail task fails

Syncing Internal IP Resolver Database with external data source

Can't contact LDAP server

qmail task fails: cannot contact ldap server

LDAP returned error code -1

LDAP server

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF