RDBMS - CAST Storage Service - Service did not start syntax error in the file postgresql conf line 59 near token 194

This page will help you to troubleshoot CAST Storage Service issues that you may face  when you start the CSS services and when it fails with the error below:

In the  Event viewer logs you may also see:

 syntax error in the file "E:/Program Files/Cast/CastStorageService/db_data/postgresql.conf" line 59, near token".194"

1. Make sure that you are following the minimum system configuration requirements to run the CAST Storage Service: Deployment. Please refer CAST AIP for Dashboards
2. Go to CAST Storage Service  Installation folder >Program Files/Cast/CastStorageService/db_data/postgresql.conf

3. As per the event log error: file syntax error in the file is "<CastStorageService version number>/db_data/postgresql.conf" line 59, near token".194"

        The error occurred because of the wrong configuration of the Remote database connection,.

Please follow the below steps and reconfigure the file as per requirement: 

1. If your Cast Storage server is installed on a separate server, you need to change the default settings in the PostgreSQL.conf and pg_hba.conf files in the remote database.
   1. Change the listening address in the PostgreSQL.conf file.
      By default, PostgreSQL allows to listen for the localhost connection. It does not allow a remote TCP/IP connection.

   2. To allow a remote TCP/IP connection, add the following entry to the C:\NetIQ\idm\postgres\data\postgresql.conf file and choose among the below options as per your infrastructure requirement: 

      listen_addresses = '*' 

      1. # what IP address(es) to listen on;
      2.  # comma-separated list of addresses;
      3. # defaults to 'localhost'; use '*' for all
      4. # (change requires restart)                                 
   1. If you have multiple interfaces on the server, you can specify a specific interface to be listened to.

   2. Add a client authentication entry to the pg_hba.conf file.
      By default, PostgreSQL accepts connections only from the localhost. It refuses remote connections. This is controlled by applying an access control rule that allows a user to log in from an IP address after providing a valid password (the md5 keyword). To accept a remote connection, add the following entry to the C:\NetIQ\idm\postgres\data\pg_hba.conf file. 

      host all all 0.0.0.0/0 md5

      For example, 192.168.104.24/26 trust
      This works only for IPv4 addresses.                                                                                                                                                                                                                                                                                                                                         

   3. For IPv6 addresses, add the following entry: 

      host all all ::0/0 md5

      If you want to allow connection from multiple client computers on a specific network, specify the network address in the CIDR-address format in this entry.
      The pg_hba.conf file supports the following client authentication formats.

   • local database user authentication-method [authentication-option]
   • host database user CIDR-address authentication-method [authentication-option]
   • hostssl database user CIDR-address authentication-method [authentication-option]
   • hostnossl database user CIDR-address authentication-method [authentication-option]
     Instead of CIDR-address format, you can specify the IP address and the network mask in separate fields using the following format:
   • host database user IP-address IP-mask authentication-method [authentication-option]
   • hostssl database user IP-address IP-mask authentication-method [authentication-option]
   • hostnossl database user IP-address IP-mask authentication-method [authentication-option]
   4. Test the remote connection.
   1. Restart the remote PostgreSQL server.
   2. Log in to the server remotely using the username and password.

   5. Once you restart the services. You can verify it by running and checking if the result is what you expect. 

      SHOW listen_addresses;
      TABLE pg_hba_file_rules;

2. If the above points do not help you to solve the issue, contact CAST Technical Support and provide the following relevant input.