000019091 - Troubleshooting Primary or Replica Hostname resolution

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000019091
Applies ToRSA ACE/Server 5.0.1 (no longer supported as of 8-15-2004)
UNIX (AIX, HP-UX, Solaris)
IssueTroubleshooting Primary or Replica Hostname resolution
Error: "Primary can't connect to replica" in Primary log after installing RSA ACE/Server 5.0 Replica
Primary ACE/Server not connecting with new replica
Primary/Replica name resolution problems
CauseThis error is due to name resolution, not necessarily on your network, but could be due to a name that resolves differently on one of the individual ACE/Server boxes.
ResolutionCheck the following areas:
On both the primary and Replica, in ace/prog/, run "sdrepmgmt list"
Compare the output between the two.

Replica 0:  (fully qualified or short name?)
Replica 1:  (fully qualified or short name?)

Compare the "Replica Service Names:" and "Replica Service Port:"
Make sure the service names are in your /etc/services file correctly.  If the "Service Port Number:" shows "0", then run ace/prog/sdrepmgmt modify, enter the service name, and it should resolve out of the services file to the correct port.

In ace/prog on the Replica run sdinfo and compare the format of the names for "Primary Server" and "This Server".

The Primary Name should also follow the same format as the "Replica 0:"
entry in sdrepmgmt (short name, or long name).

The "This Server:" entry should match the format in sdrepmgmt for each of
the appropriate servers. If not, see: Primary does not communicate with replica. Activity monitor does not show messages.

Once these issues are resolved, see: Database synchronization errors between Primary and Replica servers in RSA ACE/Server to create and copy a new Replica's database package and copy it to the Replica.
Legacy Article IDa5911

Attachments

    Outcomes