MS OMI will not start if PAMSC is started/running before OMI - After upgrade of PAMSC

Products

• CA Privileged Access Manager - Server Control (PAMSC)

Issue/Introduction

PAMSC RHEL agent has been upgraded to fix the OMI memory issue / satisfy the kernel version with PAMSC 
Monitored and found spikes in memory and it was suggested to reboot the servers post PAMSC upgrade. 
Reboot of servers were done 

Post reboot of test servers, started seeing new issue where in OMI was not coming up. 
Microsoft was engaged. Did troubleshooting and it was identified that OMI is not starting if PAMSC is started before OMI. Logs have been shared with MS to analyze the issue as to why OMI is not starting when PAMSC is started before OMI.  

Environment

Release : 14.1

Cause

MS OMI services run a sudo command inside a script. The sudo command was crashing in the script background causing an issue with the OMI services. Further diagnostics showed corruption in the PAMSC folder and file rights on several PAMSC scripts.

Resolution

Client reinstalled the PAMSC endpoint which resolved the underlying issues.