A description of common high availability errors and troubleshooting tips.
If the Containers in your Sybase CEP Server cluster cannot connect to the active Manager and trying to establish connection with the Manager alias (the name specified in the "ManagerURI" preference) by using the ping tool generates the following error message:
Ping request could not find host hostname . Please check the name and try again.
you may be experiencing one of the following problems:
The Manager process on Sybase CEP Server may not be running. Start the Sybase CEP Server instance on which the Manager process is installed and try connecting again.
The Manager may not be configured correctly. Double-check and correct the following settings:
Make sure that the Manager's host name is set to the actual name of the machine and includes the proper domain.
Make sure that the Manager's port number is set to the correct value.
If you are using multiple Managers, make sure that each Manager's "ManagerUri" preference is set to its Uniform Resource Identifier (URI), not to its actual host name.
Make sure that the Manager's"NodeUri" preference is set to its host name and port number, not to its URI alias.
The DNS server may not be working correctly. If multiple DNS servers are present (one "master" and one or more "slaves") the master may not be sending updates to the slave(s) promptly enough. Fix the problem and try connecting to the Manager again.
The plugin settings in the "ManagerFailoverDDNSPlugin" section of the c8-server.conf configuration file may be incomplete or incorrect. Correct the plugin settings and try again.
If one or more Containers fail almost immediately after starting, and generate a message like the following (the actual file name in your error message may differ from the one listed in this example):
Error: Can not rename file
'C:\Program Files\SybaseC8\Server\Storage\manager.xml.1155153553187500' to
'C:\Program Files\SybaseC8\Server\Storage\manager.xml'
('The file is busy (-5936,0)').
some of the Containers in your cluster may be incorrectly enabled as Managers. Follow the steps listed in Step 1 of "Preparing to Configure High Availability Features" for all the Containers in your cluster to resolve the problem.