TrueSight Presentation Server (TSPS) is taking a long time to start and there are performance issues with TSPS as well as excessive memory being used. For example, occasionally it is not possible to login to the TrueSight console and performing any operations in the console are sluggish/slow. |
The TSPS Server stores the policies applied on PATROL Agent configuration in the PostgreSQL database table patrolagent_pcfgtl. The default count for all versions < 11.3.04 is 10 historical configurations. In 11.3.04 the default is 3. In large environments with many PATROL Agents and large pconfig variables, this can cause performance issues due to the size of that table which has to be loaded into memory. The number of configurations to be stored should be changed from 10 to 3 only if the version is < 11.3.04. If TSPS is HA, stop the secondary (standby) TSPS first by executing command 'tssh server stop' and execute the below steps 1 to 4 on the primary (active) TSPS. 1. Take a backup of the PostgreSQL database by executing command: tssh database startbackup 2. Change the number of configurations to 3 by executing command: tssh properties set cma.agent.configuration.history.total.records 3 3. Verify the above change by executing: Windows - tssh properties list | findstr cma.agent.configuration.history.total.records Linux - tssh properties list | grep cma.agent.configuration.history.total.records 4. Truncate the patrolagent_pcfgtl table:
If you do not remember the PostgreSQL Database admin user, you can verify the username in your ...TrueSightPServer/truesightpserver/data/pgsql/pg_hba.conf file, as demonstrated in the video below.
Note: Users can check the size of patrolagent_pcfgtl table with the following query: SELECT pg_size_pretty( pg_total_relation_size('PATROLAGENT_PCFGTL') ); If TSPS is HA, once the primary TSPS is active (confirmed with command 'tssh ha status'), start the secondary TSPS. If the version is 11.3.04, the stale entries in patrolagent_pcfgtl table should be deleted. If TSPS is HA, stop the secondary (standby) TSPS first by executing command 'tssh server stop' and execute the below steps on the primary (active) TSPS.
If you do not remember the PostgreSQL Database admin user, you can verify the username in your ...TrueSightPServer/truesightpserver/data/pgsql/pg_hba.conf file, as demonstrated in the video below.
If TSPS is HA, once the primary TSPS is active (confirmed with command 'tssh ha status'), start the secondary TSPS. The following video demonstrates the procedure for versions prior to 11.3.04 as well as 11.3.04: |