- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
11-30-2020 02:57 AM
Hello,
I'm stuck to install PSM SSH Proxy - impossible to start Proxy after install.
Here is the message i get on PSMPConsole.log.
PSMPPS037E PSM SSH Proxy has been terminated. (Diagnostic information: PSMPAP160E Failed to get configuration file [Safe: PSMPConf, Folder: Root, File: syntaxparser-conf.json.1.0]. The file could not be retrieved from the Vault and does not exist in the configuration cache from previous usages Reason: PSMPAP043E Failed to get gid of PSMInternalUsers, 1)
The mentioned safe and the files are present on the Vault.
I don't find anything on the KBs around this.
I try to disable SELinux for tests, UsePAM is set to yes with rights options.
If someone has a idea to help me, don't hesitate 😉 thank you
11-30-2020 03:19 AM
Just to add some info, here is my basic_psmpconf file
PSMPServerVaultFile="/etc/opt/CARKpsmp/vault/vault.ini"
PSMPServerCredFile="/etc/opt/CARKpsmp/vault/psmpappuser.cred"
PSMPServerGWCredFile="/etc/opt/CARKpsmp/vault/psmpgwuser.cred"
LogsFolder="/var/opt/CARKpsmp/logs"
LocalParmsFileFolder="/var/opt/CARKpsmp"
TempFolder="/var/opt/CARKpsmp/temp"
PSMPConfigurationSafe="PVWAConfig"
PSMPConfigurationFolder="Root"
PSMPPVConfigurationFileName="PVConfiguration.xml"
PSMPPoliciesConfigurationFileName="Policies.xml"
PSMPServerId="PSMPServer"
PSMPTempFolder="/var/opt/CARKpsmp/temp"
Safe: PSMPConf, Folder: Root, File: syntaxparser-conf.json.1. is not mentioned inside.
03-16-2021 08:59 AM
Hi,
I solved it today.
The actual issue is there are two safes missing
1.PSMPLivesessions
2.PSMPConf
and one json file which is suppose to be there in PSMPCONF safe.
Created above two safes with permissions like PSMPLivesession as of PSMLivesessions and PSMPConf as of PVWAConf
Started the psmp service alone and its up
tested it couple of times by stop and start and it works great
03-16-2021 09:02 AM
forgot another step.
you need add a file in PSMPConf safe,
after installation on below location you will find file syntaxparser-conf.json
/var/opt/CARKpsmp/temp
you need to take that file out of PSMP server and copy it to PCMPConf safe and rename it as syntaxparser-conf.json.1.1
now start your PSMP service.
i have no requirement to turn on adbridging so just for information.
07-21-2022 06:17 AM
Hi Everyone,
We got this issue fixed in our environment. PFB findings which helped us to fix this issue
for PSMPv12.2.
If SElinux is enabled it can interfere when the sshd is using the PSMP pam to authorize the user. It is sometimes necessary to run a few commands after installing psmp in integrated mode to get it working.
For RHEL 7:
semodule -i /etc/opt/CARKpsmp/selinux/psmp_integrated_rhel7.pp
for RHEL 8:
semodule -i /etc/opt/CARKpsmp/selinux/psmp_integrated.pp
semanage fcontext -a -t system_dbusd_var_lib_t '/var/opt/CARKpsmp/temp/syntaxparser-conf.json.1.1
vaultuser@targetuser@targetaddress@PSMPaddress
Hope it helps. !!
Thanks
08-21-2022 03:46 AM
Hello Nupur, after running semanage fcontext -a -t system_dbusd_var_lib_t '/var/opt/CARKpsmp/temp/syntaxparser-conf.json.1.1 it waits for some input. What should it be?
11-01-2022 12:06 AM
Hi 1_Irura
We didn't get any prompt or asked to provide any input, can you please elaborate or share the snapshot for the same.
Thanks
03-21-2023 03:23 AM
That's because the command is not complete, it should be:
semanage fcontext -a -t system_dbusd_var_lib_t '/var/opt/CARKpsmp/temp/syntaxparser-conf.json.1.1'
Most likely the trailing single quote was lost in space due to copy/paste error ...
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!

