Facing intermittent issue with 1 PSM server. Getting "This session could not be established securely" error

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Facing intermittent issue with 1 PSM server. Getting "This session could not be established securely" error

L3 Networker

We have PSMs behind a LB. I changed the PSM ID for the platform to another server and it worked. SO, only 1 PSM has this issue

 

PSM COnsole log

 

[07/08/2019 | 01:24:11] | :: | PSMSR178E Failure occurred while refreshing configuration. PSMSR182E Failed to retrieve configuration file from Vault [Safe: PVWAConfig, Folder: Root, File: Policies.xml] (Error: ITACM062S Communication error (Diagnostic information: 562) ) (Codes: -1, -1)

[07/08/2019 | 01:25:11] | :: | PSMIN136W An error occurred while handling the messaging server client. Error: PSMSR891E Failed to handle the session logon request. Diagnostic information: 2, Reason: PSMSR983E The session [acfc77e9-46d7-4294-8b7a-364e55748008] is being stopped because the Protocol Provider didn't run.

[07/08/2019 | 01:25:31] | :: | PSMIN136W An error occurred while handling the messaging server client. Error: PSMSR891E Failed to handle the session logon request. Diagnostic information: 1, Reason: PSMSR873E Failed to read parameters from vault file. Reason: PSMSR870E Failed to open vault file. Reason: PSMSR875E Open vault file operation failed (Diagnostic information: Safe=PSMSessions, Folder=Root, Object=80bde68ad3dc92f2ee60e370fb2ce379717d0590). Reason: ITACM062S Communication error (Diagnostic information: 562)

 

Seems like some communication error. But not sure what it is? Anyone have any pointers for this issue?

3 REPLIES 3

L5 Sessionator

are you able to resolve LB dns ? you've mentioend you are able to connect to one target when directly pointing in the platfrom, have you tried the other servers (Pointing PSM ID of problamatic server in the platfrom and test it)? is 3389 is open from the machine where you testing and the problmatic psm server? is the respective is open from problmatic psm server to target?

I tried mentioning specific servers in the PSM ID and it worked except the problematic server. Also, i am not sure how this LB is setup. When I RDP to this LB IP address, it takes me to the problematic server (checked hostname after RDP).

 

Also, this issue happens intermittently. 1st time it did connect with the problematic PSM but the 2nd time , it did not work.

Check with your LB team and they have to look into this issue. Have you not settup psm health monitor? if you correctly settup this one, this problamatic server will be removed from the LB queue automatically..

 

PSM Health Montoring capability is detailed here, please have a look and speak to you LB team ..

https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PSM/psm_healthcheck.htm?Highl...

  • 965 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!