-
Title
Sybase RS agent is not reading or located the interfaces / sql.ini file -
Description
Sybase RS agent fails to monitor as not able to read or find the "interfaces" or "sql.ini" file. The following messages may be present in the agent logs:
Either interfaces (on UNIX)or sql.ini (on Windows) File Does Not Exist
Replication Server Name has no mapping in the sql.ini file
com.quest.glue.core.agent.AgentInstance - Failed to start data collection
java.lang.RuntimeException: java.lang.RuntimeException: Failed to Initialize Agent. Excption:
For input string: "hostname" -
Cause
CAUSE 1
Connection file (sql.ini / interfaces) is not present on the Foglight Agent Manager (FglAM) host.
CAUSE 2
Invalid characters prevent the file from being read.
CAUSE 3
Incorrect file format.
CAUSE 4For Linux, there more than one space between values of the server connection parameters in the interfaces file.
CAUSE 5
The addition of a ssl field in a line of the interfaces file cannot be read
By default, the agent can read the interfaces file(Sybase in Linux) with the format like:RSFOG2master tcp ether SERVERNAME16 11753query tcp ether SERVERNAME16 11753
It will read the first hostname(SERVERNAME16) and port(11753) to build a profile and set into a map with key 'serverName'(RSFOG2).If the format is:RSFOG2master tcp ether SERVERNAME16 11754 ssl="CN=SERVERNAME16"query tcp ether SERVERNAME16 11754 ssl="CN=SERVERNAME16"
CAUSE 6
The Interfaces files contains TLS entries such asSYBASE_SERVER query tli tcp /dev/tcp \x000213880a3ee71c0000000000000000 master tli tcp /dev/tcp \x000213880a3ee71c0000000000000000 -
Resolution
RESOLUTION 1The sql.ini or interfaces connection file must be present in a path that is local to the FglAM host running the Sybase RS agent.
RESOLUTION 2
Invalid hidden characters in the file will cause issues when attempting to read. This can be confirmed by using a text editor with the option to see hidden symbols.
RESOLUTION 3
The connections file format (interfaces or sql.ini) should match the one for the Operating System of the FglAM host.
UNIX:
SAMPLE_RS master tcp ether 10.0.0.1 11752 query tcp ether 10.0.0.1 11752Windows:
[SAMPLE_RS] master=nlwnsck,10.0.0.1,11752 query=nlwnsck,10.0.0.1,11752RESOLUTION 4
Verify if from the entries in the interfaces files there is any with more than one "space" character between any of its values. For example, two spaces between "master" and "tcp" will cause 'For input string: "hostname"' type errors when the agent tries to convert the string to a numerical value.
Change to:# Fails with 'For input string: "hostname"' SAMPLE_RS master tcp ether hostname 11752 query tcp ether hostname 11752
RESOLUTION 5SAMPLE_RS master tcp ether hostname 11752 query tcp ether hostname 11752Defect ID FOM-771 was logged to recognize interface file lines with SSL settings. This has been fixed in the 5.9.7.10 and higher releases of the Sybase SAP ASE cartridge.
RESOLUTION 6In previous years this was the way to define an entry in the interfaces file. To translate these to the usual non-hex notation follow this simple method:
- Take the hex-number from the 5th position to the 8th. In this case the number is 1388. Use your favorite calculator to convert it to decimal. The output should be 5000. That's the port number.
- To determine the IP-address take the next 4 pieces of 2 bytes. In this case 0A, 3E, E7 and 1C. Convert it into decimal, the result should be 10, 62, 231 and 28. These 4 numbers are the IP address: 10.62.231.28
- Use nslookup (or dig) to get the hostname.
The new entry in the interfaces file should then be:
SYBASE_SERVER query tcp ether <hostname> 5000 master tcp ether <hostname> 5000 -
Defect ID
FGDBSYB-I-4 -
Additional Information
Enhancement request FOG-5670 was created to improve debug logging when reading interfaces or INI files.