PSMP Installation for ISPSS fails with no clear 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

PSMP Installation for ISPSS fails with no clear error

L2 Linker

We have done successful PSMP installation in lower environment without any errors but when performing the same installation on similarly configured PROD server, we encounter the following error:

***** Please Enter Privilege Cloud Install User Password and press ENTER *****

*****(Optional) Would you like to validate the entered credentials? this will require you to input your Privilege Cloud Portal URL & Make sure FW is open on 443 [Y/N] y

Making API call to: https://dummy.privilegecloud.cyberark.cloud/passwordvault/api

Will timeout in 20s if doesn't reach Portal on 443...

Validation Passed!

Command ended successfully

 

 

***** Primary RPM Installation, This may take some time...*****

***** Installing: CARKpsmp-infra-14.1.3.2.x86_64.rpm

***** RPM package install successful: CARKpsmp-infra-14.1.3.2.x86_64.rpm

 

***** Installing: CARKpsmp-14.1.3.2.x86_64.rpm

***** Error: Failed to install RPM. Fix the errors and rerun wizard again.

cp: cannot stat '/tmp/temp/EnvManager.log': No such file or directory

***** Useful Logs:

***** /root/PrivilegedSessionManagerSSHProxy-RHELinux8-Intel64-Rls-v14.5.1/_psmpwizerror.log

***** /root/PrivilegedSessionManagerSSHProxy-RHELinux8-Intel64-Rls-v14.5.1/psmp_install.log

***** /root/PrivilegedSessionManagerSSHProxy-RHELinux8-Intel64-Rls-v14.5.1/EnvManager.log

 

***** Let's uninstall RPM packages since installation was not completed. *****

Removing PSMP Services

Unloading SELinux policy...

OpenSSH files are restored. Make sure to update OpenSSH default configuration if needed.

Service [sshd] is about to be restarted...

Service [sshd] was restarted successfully.

Starting post-uninstallation stage for 14.1.3-2

Removing logs folder...

Removing temporary files...

Removing cache files...

Removing user profile files...

Removing configuration files...

Reloading systemctl

Uninstall process is starting...

Uninstall process was completed successfully.

***** Clearing Credentials *****

 

Any assistance on this would be greatly appreciated

8 REPLIES 8

L7 Applicator

Hi @Pooja Salvi​ 

 

Some of the factors that can affect the installation are,

 

  • Not having enough free disk space in  /opt, /var or /tmp can prevent RPMs from extracting and installing.
  • The RPM package didn’t copied properly in Prod PSMP or it might got corrupted while copying
  • Not having enough permissions on Prod
  • cp: cannot stat '/tmp/temp/EnvManager.log': No such file or directory suggests issues with the  /tmp directory. It could be permission on the directory or , not available enough disk space, or even its disk mount could be not working property.
  • Please check the Installation logs under /var/tmp/psmp_install.log
  • Try installing using yum command

 

sudo yum install CARKpsmp-14.1.3.2.x86_64.rpm

 

And review system logs using following commands,

 

sudo journalctl -xe sudo /var/log/messages

 

sudo /var/log/syslog

 

Hope it helps !

Thank you @Malhar Vora​ 

 

I had used the psmpwiz automation script, which verifies disk space and other prerequisites. All pre-checks were successfully completed, and the error occurred only during the RPM installation step.

We then attempted a manual installation. While it didn’t fully succeed and still reported “installation completed with errors,” we were able to bring the services up with support from the Linux administrator. The following commands were executed:

systemctl unmask psmpsrv.service

systemctl enable psmpsrv.service

systemctl restart psmpsrv.service

 

 

To be honest, the errors we encountered weren’t very indicative of the root cause. The PSMPInstall.log primarily showed messages related to EnvManager.log, which didn’t clearly point to the issue.

However, upon further investigation, some of the OS-level logs revealed an error related to the user.cred file.

From what the Linux administrator shared, the Production servers are configured with stricter security compared to the lower environments. This likely explains why we didn’t encounter the same issue during the Pre-Production installation.

 

Thank you again for your inputs 🙂

L7 Applicator

Hi @Pooja Salvi​ 

 

I'm glad it helped you !

 

Yes, I've experienced it many times and usually Prod servers permissions are tightly controlled. In the Unix world, the permissions are controlled through granular file or directory level permissions and explicitly needs to be granted. Hence in my earlier response, I had recommended to check the permissions.

L0 Member

Hi,

 

we are facing the same issue, and the psmpwiz automation script has produced these logs:

 

 

Verifying...             ########################################

Preparing...             ########################################

Installation process is starting...

CARKpsmp-infra package version was verified

Updating / installing...

CARKpsmp-14.1.4-4           warning: group PSMInternalUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

warning: group PSMConnectUsers does not exist - using root

warning: group PSMShadowUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

warning: group PSMShadowUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

warning: group PSMShadowUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

warning: group PSMConnectUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

warning: group PSMConnectUsers does not exist - using root

warning: group PSMInternalUsers does not exist - using root

########################################

chown: invalid group: ‘root:PSMInternalUsers’

Reloading systemctl

Created symlink /etc/systemd/system/multi-user.target.wants/psmpsrv.service → /usr/lib/systemd/system/psmpsrv.service.

Created symlink /etc/systemd/system/psmpsrv.service.wants/psmpsrv-psmpserver.service → /usr/lib/systemd/system/psmpsrv-psmpserver.service.

Service [psmpsrv] is being stopped...

Service [sshd] is about to be restarted...

Service [sshd] was restarted successfully.

Unloading SELinux policy...

Machine hardening was completed successfully.

Installation process was completed with errors. For more information, refer to CyberArk documentation.

 

 

The server doesn't have any type of restriction policy, so I don't think it's a permission problem in my case.

Any ideas?

Is it mandatory to install the PSM connector first, maybe?

L7 Applicator

Hi @Andrea Emiliano​ 

 

Please ensure PSMP has connectivity to the Vault on port 1858.

 

Also verify the user.cred file used for the installation and the psmpappuser.cred file contain the correct credentails.  

 

Please create the required groups / users manually.

 

groupadd PSMConnectUsers

groupadd PSMShadowUsers

groupadd PSMInternalUsers

 

Then, please run the RPM package installation again with the force/repair option, which allows the installer to try and correct the existing failed installation.

 

rpm -Uvh --force CARKpsmp-<version>.rpm

 

Hope it helps !

L1 Bithead

Hi @Pooja Salvi​ ,

 

We are also receiving similar error after successful execution of the script. Could you please share what has happened next ? proceeded with manual installation?

 

Thanks,

Bhargav

L3 Networker

Any Solution to this @Bhargav Sai Chitta​ @Andrea Emiliano​  @poojas​ . We are facing the same

Hi @Amogh More​ ,

 

we observed that memory allocated to SELinux is insufficient. Due to that, we observed that issue. However, later we increased the memory size to 2 GB for SELinux and proceeded with installation.

 

Thanks,

Bhargav

  • 514 Views
  • 8 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!