TRS

kotak TRSUI issue and sol(FAQ)

• the above doc contains following issue from 1st msi to the latest (2.1.10.19)

• Check OCM if your profile pic is updated.
• OCM->template-template features -> faceauth URL is appropriate one or not. change it if the logs in remote security folder under ml.logs say  connection api failed.
• you can also disable liveness detection for timebeing to check if that is the issue .

1. TRS_CLIENT_WS_URL is set in environment variable, it picked correctly from environment variable
2. While trying to connect it must have failed. You can see that in TRS.Log file from %AppData%/Remotesecurity/Logs.
The log will be like below
"Connecting to WS URL: wss://aggregator.kbprvmla00754.kbank.kotakgroup.com/mux". You can see whether its closed or connected.
3. Another way we can directly check without seeing in log is replace ws with http, replace mux with ping and try that url(for example: https://aggregator.kbprvmla00754.kbank.kotakgroup.com/ping) from browser the response in the browser should be like this "OK 2021-03-30 00:18:20".

• login to 10.22.135.242
• cd /logs/trsserver/secured/Uploads
• df -h
• ls
• cd TRS_kmblID
• cd zip
• sudo rm -f trslogs_*
• do this for all 178 + agents the space will clear on its own

• Ping all the services in citrix cmd ( ping 10.22.135.244/245/246/247/242/243/248/250)
• Docker stop $(docker ps -a -q)
• Docker start $(docker ps -a -q)
• Sudo systemctl status tetherfi-media-server.service (in 248/250)
• docker stop tcis_docker_management-center_1(242/243)

• restart the system so as to get windows update , so that the bus drivers and camera drivers are updated
• check if the camera being used by other application has trs-multicamera selected.
• delete pipleline.json and relaunch the application .

• IT has to restart the services
• restriction caused by AV on C drive
• check if BCP is connected to agents system properly.
• Unable to find TRSUI to login

• check the build to be the latest 4th msi (2.1.10.19) which has incorporated fix .
• check if the users home directory keeps changing , if it is inform IT to stop the changes else use the following fix.
• open  edit environment variables
• wait for the first time for the cache to build up normally.
• copy the directory path of remotesecurity->opencl as following
• C:\Users\Sankalpa TTF\AppData\Roaming\RemoteSecurity\opencl
• add the key OPENCV_OPENCL_CACAHE_DIR and add the above value . issue fixed

• issue is caused by proxy being set in network configuration.
• disable the proxy set
• internet explorer-> ALT +X-> internet options-> connection->Lan Settings it should be blank

• check for the agent if the rules assigned does contain screen lock enabled or not .
• redis -cli
• auth tetherfi
• keys *role
• hkeys “urn:tmc_agg:rules:role”
• ICC_Agents
• hdel “ICC_Agents” ICC_Agents
•  hdel “urn:tmc_agg:rules:role”  “ICC_Agents

• clear cache and try , if this doesn't work then we need to use redis.
• redis -cli
• auth tetherfi
• hkeys "urn:tmc_agg:trs:sessions"
• hdel “urn:tmc_agg:trs:sessions/hashset”  urn:tmc_agg:session:kmbl_ID

• check error in UI logs and find error related to access denied
• Delete files from %temp% upto 10k or more depending on the files present here

1. TRS_CLIENT_WS_URL is set in an environment variable, from TRSUI SETTING page check if it is picked correctly from an environment variable.
2. In case, if TRSUI failed to connect to the TRS server. We can see in the TRS.Log file from %AppData%/Remotesecurity/Logs. The log will be as follows. "Connecting to WS URL: wss://<domainname>:55656/mux". You can see whether it's closed or connected.
3. Another way we can directly check without seeing in log is to replace ws(s) with HTTP(s), replace mux with ping and try connecting that URL (for example https://<domainname>:55656/ping) in the browser. Response in the browser should be like this "OK 2021-03-30 00:18:20".