Sybase RS agent is not reading or located the interfaces / sql.ini file (4311734)

The Sybase Replication Server (RS) agent fails to start or monitor the environment due to issues reading the connection file (interfaces on UNIX or sql.ini on Windows). The following errors may appear 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. Exception: For input string: "hostname"

• Cause 1
  The sql.ini or interfaces file is not present on the Foglight Agent Manager (FglAM) host.

• Cause 2
  The file contains invalid or hidden characters, preventing it from being parsed correctly.

• Cause 3
  The file format does not match the expected structure for the FglAM’s operating system.

• Cause 4
  In UNIX environments, multiple spaces between parameters in the interfaces file cause parsing errors.

• Cause 5
  SSL parameters in the interfaces file prevent the agent from interpreting connection details.

  Example of problematic format:

   

  RSFOG2 master tcp ether SERVERNAME16 11754 ssl="CN=SERVERNAME16" query tcp ether SERVERNAME16 11754 ssl="CN=SERVERNAME16"

• Cause 6
  Legacy interfaces entries use TLS hexadecimal notation, which the agent cannot parse directly.

  Example:

   

  SYBASE_SERVER query tli tcp /dev/tcp \x000213880a3ee71c0000000000000000 master tli tcp /dev/tcp \x000213880a3ee71c0000000000000000

• Resolution 1 – Ensure File Presence
  The sql.ini (Windows) or interfaces (UNIX) file must be present and accessible locally on the FglAM host where the Sybase RS agent is deployed.

• Resolution 2 – Remove Invalid Characters
  Open the file in a text editor that displays hidden or special characters. Remove any non-printable or corrupt characters and save the file again.

• Resolution 3 – Use Correct File Format
  Ensure the connection file matches the correct format based on the FglAM’s operating system:

  • UNIX Format:

     

    SAMPLE_RS master tcp ether 10.0.0.1 11752 query tcp ether 10.0.0.1 11752

  • Windows Format:

     

    [SAMPLE_RS] master=nlwnsck,10.0.0.1,11752 query=nlwnsck,10.0.0.1,11752

• Resolution 4 – Fix Extra Spaces in UNIX Interfaces File
  Ensure there is only one space between values.

  ❌ Incorrect (extra spaces):

   

  SAMPLE_RS master tcp ether hostname 11752

  ✅ Correct:

   

  SAMPLE_RS master tcp ether hostname 11752

• Resolution 5 – SSL Parameter Handling
  The ability to parse lines containing ssl="..." in the interfaces file was added in Sybase ASE cartridge version 5.9.7.10 and later.

  Defect ID: FOM-771
  Upgrade to version 5.9.7.10 or higher of the SAP ASE cartridge to support this syntax.

• Resolution 6 – Convert Legacy TLS Entries
  Legacy hexadecimal TLS notation can be converted as follows:

  1. From the string \x000213880a3ee71c0000000000000000:

     • Port number: Convert hex from position 5–8 (1388) → 5000

     • IP Address: Convert the next 4 pairs → 0A.3E.E7.1C → 10.62.231.28

  2. Use nslookup or dig to resolve the hostname from the IP.

  3. Update the file using the standard format:

      

     SYBASE_SERVER query tcp ether <hostname> 5000 master tcp ether <hostname> 5000