PSMP session getting closed automatically

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

PSMP session getting closed automatically

L3 Networker

Hi All,

PSMP session is getting terminated automatically soon after displaying " Your session is being recorded"

 

I could do SSH with same account&password successfully using below methods

  1. Direct SSH from my laptop
  2. PVWA-PSM
  3. Also SSH to target server is possible from both PSM and PSMP servers (i.e. no connectivity issue)

 

Any suggestion on what could be the issue?

 

I see below errors in the session log created under components folder (I have pasted only error messages)

[04/03/2021 | 20:01:52.313910] | :: | PSPIN001I PSM infrastructure library exception occurred. PSPIN054E Session configuration variable [IsSCPCommand] not found (Codes: -1, -1)

[04/03/2021 | 20:01:52.314161] | :: | PSPSHPSPIN054E Session configuration variable [IsSCPCommand] not found

[04/03/2021 | 20:01:52.314211] | :: | PSPIN001I PSM infrastructure library exception occurred. PSPIN054E Session configuration variable [IsSFTPCommand] not found (Codes: -1, -1)

[04/03/2021 | 20:01:52.314251] | :: | PSPSHPSPIN054E Session configuration variable [IsSFTPCommand] not found

[04/03/2021 | 20:01:52.314282] | :: | PSPIN001I PSM infrastructure library exception occurred. PSPIN054E Session configuration variable [IsSSHTerminalEnabled] not found (Codes: -1, -1)

[04/03/2021 | 20:01:52.314315] | :: | PSPSHPSPIN054E Session configuration variable [IsSSHTerminalEnabled] not found

[04/03/2021 | 20:01:52.314342] | :: | PSPIN001I PSM infrastructure library exception occurred. PSPIN054E Session configuration variable [SSHCommand] not found (Codes: -1, -1)

[04/03/2021 | 20:01:52.314401] | :: | PSPSHPSPIN054E Session configuration variable [SSHCommand] not found

 

[04/03/2021 | 20:01:52.320647] | :: | PSPPR056I Protocol message data has been serialized. Serialized data length: 0.

[04/03/2021 | 20:01:52.320674] | :: | PSPPR041I Encrypting the message before sending it. Total number of bytes to be encrypted: 7, Number of data bytes (without the message prefix): 0.

[04/03/2021 | 20:01:52.320745] | :: | PSPPR042I Message is being sent over the pipe channel (Pipe timeout: 500, Packet identifier: HELLO)

[04/03/2021 | 20:01:52.320772] | :: | 810E Failed to retrieve OS descriptor. See previous warnings messages

[04/03/2021 | 20:01:52.320870] | :: | PSPPR048I Waiting for the following expected packets: ACK

[04/03/2021 | 20:01:52.320910] | :: | PSPPR044I Waiting for a protocol packet (Current index: 1)

[04/03/2021 | 20:01:52.320943] | :: | 810E Failed to retrieve OS descriptor. See previous warnings messages

[04/03/2021 | 20:01:52.322215] | :: | PSPPR032I Protocol message factory is creating CPSMProtocolMessageBase object

[04/03/2021 | 20:01:52.322256] | :: | PSPPR059I Protocol packet index (1) is accepted. Current index: (1)

 

[04/03/2021 | 20:01:57.328660] | :: | PSPSH070I Parameter [SendRateValue] was initialized with the default value [50] due to an error in fetching the connection parameters configuration

[04/03/2021 | 20:01:57.328754] | :: | PSPSH071I No logon sequence was set in the connection parameters configuration

[04/03/2021 | 20:01:57.328858] | :: | PSPSH051I Sign-on sequence defined. Parsing prompts

[04/03/2021 | 20:01:57.328978] | :: | PSPSH054I Sign-on sequence is enabled. Disabling keyboard input and recording/audit capabilities

[04/03/2021 | 20:01:57.329064] | :: | PSPSH068I Finished InitPSPPlink, starting the plink

[04/03/2021 | 20:02:02.909961] | :: | PSPSH007I Parameter [Password] was initialized with value [****]

[04/03/2021 | 20:02:10.253608] | :: | PSPSH021E Authentication failure for user xxxxx. Program will be closed

[04/03/2021 | 20:02:10.253809] | :: | PSPSH069I Connection was terminated by plink. Reason: PSPSH021E Authentication failure for user xxxxx. Program will be closed.

[04/03/2021 | 20:02:10.254126] | :: | PSPSH016I PSPPlink is in cleanup section

[04/03/2021 | 20:02:10.254189] | :: | PSPSC001I [72731f26-7d24-11eb-9bc0-00155d851df4.SSH] Stopping PSM Text recording component. Records in buffer: 0

[04/03/2021 | 20:02:10.254279] | :: | PSPRC014I [72731f26-7d24-11eb-9bc0-00155d851df4.SSH] Stopping recording component

[04/03/2021 | 20:02:10.254498] | :: | PSPPR087I [72731f26-7d24-11eb-9bc0-00155d851df4] Sending [ReturnCode:1] to server

[04/03/2021 | 20:02:10.257069] | :: | PSPSH017I PSPPlink is about to be closed

 

Though i see error message as authentication failure for the account used to connect, i verifed multiple times the password in vault is correct and i could establish session using PVWA-PSM successfully.

 

Note the user i am trying to connect is authenticated via password (which is vaulted) and i haven't configured logon account as direct login is possible.

4 REPLIES 4

L3 Networker

I would check the logs on the target Linux server and see what the type of error message Linux is giving.

L4 Transporter

Set the PuTTY exit setting to Never & then you can capture the exact PSMP error message.

This way PuTTY window won't close automatically.

Hi,After updating exit setting in PUTTY I saw the same error message what is printed in session log file under components folder in PUTTY console also which doesn't seem to be the real cause. Because i could connect via PSM using same credentials!

 

Reason: PSPSH021E Authentication failure for user xxxxx. Program will be closed.

Were you able to fix the issue ? I am getting the same error. Can login from PVWA using PSM-SSH, can login manually. Authenticaion failure through PSMP . Same error code as above.

  • 1555 Views
  • 4 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!