Intermittent issue with PSM sessions

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

Intermittent issue with PSM sessions

L3 Networker

Hi All,

We have users reporting a "Timeout has expired. User is being disconnected" error while using PSM. I had to restart PSM service on all PSMs and then it went away. Also, checked PSM Trace file and found the below errors. Any help would be appreciated! Thanks!

 

Trace errors:

 

PSMSR913E Failure occurred while handling session. PSMSC050E Failed to get user token of TS session [42] (System error [2]: The system cannot find the file specified.) (Codes: -1, -1)

 

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=dbb938f802869c091b7964368637f0534c551835). Reason: ITATS053E Object dbb938f802869c091b7964368637f0534c551835 doesn't exist.

1 accepted solution

Accepted Solutions

L6 Presenter

Timeour Expire generally come with below given scenarios-

  • unable to communicate to Vault
  • Number of total connections through PSM have reached it's limit of allocated CALs. So if 5 CALs are assigned to PSM and 5 concurrent connections are already established, 6 connection will result in time out error as yours

 

If PSM service is restarting then perhaps no problem with Vault connectivity, since you restart the service, it disconnects all existing connections and hence you are able to establish new connections, I suspect absence of RDS licenses. Check with your Wintel team.

View solution in original post

31 REPLIES 31

L3 Networker

Also, found these entries in the PSMCOnsole log

 

 :: | PSMSR948W [84816a89-e931-4680-a4af-d06387ac7d3e] Session keeper did not logoff the session. The session will be forcefully logged off. (Session id: 43). Reason: 946E [84816a89-e931-4680-a4af-d06387ac7d3e] Session keeper logoff timeout reached while waiting for the session to logoff. (Session id: 43)

[27/06/2019 | 06:35:04] | :: | PSMSR948W [7e0f396c-0ea3-4095-9d11-6937e2e2b300] Session keeper did not logoff the session. The session will be forcefully logged off. (Session id: 34). Reason: PSMSR508E An error occurred while waiting for the SessionKeeper process to shutdown (Code: 1073807364).

 :: | PSMSR948W [839a0fa2-49ab-4807-96fd-d9201d40d009] Session keeper did not logoff the session. The session will be forcefully logged off. (Session id: 93). Reason: 946E [839a0fa2-49ab-4807-96fd-d9201d40d009] Session keeper logoff timeout reached while waiting for the session to logoff. (Session id: 93)

 

L4 Transporter

Hi @Rohan Rajwade​ ,

 

The logs mention the vault file. That is the vault.ini file you can find on each CyberArk component. There you can find the ip address of the vault. Apparently the psm wasn't able to read the parameters of that file.

 

Kind regards,

Jelle

Hi Jelle,

Thanks for your reply. So could this be a connectivity issue? as its happening intermittently?

Hi @Rohan Rajwade​ ,

 

It's not an issue, it's a security configuration on that machine.

Could you test the following.

Open putty on your desktop and try to logon to the unix machine with the root user.

This way you are using the ssh protocol instead of logging on the server through the console.

 

Kind regards,

Jelle

Hi @Jelle Verreth​ 

 

Didn't get you. You mean it is a security config thing on the PSM server? i am able to retrieve password and RDP directly to the target machine. However, the issue occurs when trying to connect to the target Windows box via PSM. PSM connection using PSM-SSH component works fine even when ther is a issue with the RDP component

Hi @Rohan Rajwade​ ,

 

Ignore my last post, it was meant somewhere else. 😉

Is the vault.ini file filled in correctly?

Also check your italog.log on the vault to see if there are any locked users.

 

Kind regards,

Jelle

L3 Networker

@Rohan Rajwade​ Are you still getting this error? i also getting same issue.

 

Np 🙂

Yeah vault.ini has correct prim Vault IP and no locked users in italog

@Naveen Krishnappa​ 

Yup still trying to troubleshoot this. haven't found a solution yet. Are you facing the exact same error?

yes, I am trying to restart the PSM server? did you try restarting?

 

L6 Presenter

Timeour Expire generally come with below given scenarios-

  • unable to communicate to Vault
  • Number of total connections through PSM have reached it's limit of allocated CALs. So if 5 CALs are assigned to PSM and 5 concurrent connections are already established, 6 connection will result in time out error as yours

 

If PSM service is restarting then perhaps no problem with Vault connectivity, since you restart the service, it disconnects all existing connections and hence you are able to establish new connections, I suspect absence of RDS licenses. Check with your Wintel team.

L4 Transporter

Timeour Expire generally come with below given scenarios-

  • unable to communicate to Vault
  • Number of total connections through PSM have reached it's limit of allocated CALs. So if 5 CALs are assigned to PSM and 5 concurrent connections are already established, 6 connection will result in time out error as yours

 

If PSM service is restarting then perhaps no problem with Vault connectivity, since you restart the service, it disconnects all existing connections and hence you are able to establish new connections, I suspect absence of RDS licenses. Check with your Wintel team.

Yes. Restarting the PSM service does fix the problem for some time.

Hi @Rohan Rajwade​ ,

 

Already tried to restart the psm service?

 

Kind regards,

Jelle

  • 1 accepted solution
  • 6982 Views
  • 31 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!