Article ID: 114265, created on Jul 2, 2012, last review on Dec 29, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

OBAS cannot perform any operation related to external systems such as payment processing centers, domain registrars and/or SSL certificate vendors.

The error messages can be different for different operations (due to different plug-ins used).

Payment transactions can fail with the error:

 A communication error occurred while connecting to the server.

Domains registration/renewal through the eNom registrar can fail with an error:

Error occurred during renewal. Error: eNom communication level error: ApplicationError: Application error occurred, contact provider for details.

In general, errors inform of communication problems.

Cause

OBAS cannot connect to na external system because it cannot resolve its hostname to IP address.

Resolution

To make sure that the problem is related to DNS resolving please perform the simplest test:

  1. Get hostname of the external system in OBAS PCC in domain or payment plug-in settings, e.g. it may be hostname of the eNom registrar reseller.enom.com or www.paypal.com for payments through PayPal.
  2. Log into OPBAS server by SSH as root
  3. Get the IP address of a name server from the /etc/resolv.conf file, let it be 192.168.1.101
  4. Try to resolve the hostname of an external system you found on step 1 using the DNS server from the /etc/resolv.conf file with the dig utility:
    # dig reseller.enom.com @192.168.1.101

Replace 192.168.1.101 in the command above with the actual IP address from the /etc/resolv.conf file on OBAS Management Node.

If you see an error message and cannot resolve hostname to IP address it means that the DNS server used by OBAS is broken. As a result, OBAS cannot resolve hostname of any external system and cannot connect to it to perform provisioning operation.

E.g. the error message can be as follows:

 dig reseller.enom.com @192.168.1.101

 ;; global options:  printcmd

 ;; connection timed out; no servers could be reached

Fix the problem with the DNS server configured in the /etc/resolv.conf file on OBAS server or put IP address of a working server into the file.

Restart OBAS backend:

# service hspcd restart

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF