This section describes problems that can occur during the transport phase of synchronization.
The messages in Table 17 are generated by the mkorder, mkreplica, shipping_server, and syncreplica commands.
The local host’s hosts file, hosts NIS map, or Domain Name Service must list one of the following hosts:
Note: If hosts in your network are known only by their IP addresses, you can use the IP addresses instead of host names.
In the absence of such entries, the shipping server fails, because it cannot determine where to deliver the packet. In this case, it writes error messages to its log file (UNIX) or the Windows Event Viewer.
If the destination host name was misspelled, use the mkorder command to create a new shipping order with the correct host name. If a host name is misspelled in a mkreplica –export command, the incorrect host name is recorded. Verify the error with lsreplica –long, and correct the spelling with chreplica.
In other cases, you may have to revise the host’s database of remote hosts. The sending host must be able to communicate with the receiving hosts through TCP/IP channels. Use the rcp command on the sending host to copy a file to the receiving host. If it fails, you have a setup or networking problem with your host. If the command succeeds, contact Rational Customer Support.
Each time the shipping server cannot deliver a packet to a valid destination host, it logs error messages:
If the problem is temporary (remote host is down, network connections are down, and so on), a subsequent invocation of shipping_server –poll will transmit the packet successfully. If the problem is not temporary, the shipping order may expire eventually.
If the shipping server at the receiving replica does not start or the connection is refused, check the albd_server log on the receiving host for an explanation of the failure.
A syntax error in the shipping.conf file on UNIX can cause the connection to be refused. For example, if there is an incorrect e-mail address in the file, the albd_server log displays an error like this:
If the shipping server finds that a shipping order has expired, it attempts to return the packet to the originating host. Also, it sends a mail message to one or more administrators on the original sending host, and sends another mail message when the packet is returned to the original sending host. On Windows, if e-mail notification is not enabled, the shipping server writes a message to the Windows Event Viewer.
Use the lspacket command to check the return bays on your host. The packet files may have been returned by store-and-forward. If so, try again to deliver the packet:
If the packet files are not in your host’s return bays, they may be in transit. Search for the files immediately, because a packet that cannot be returned to its home host within 14 days is deleted.