Open wouterhummelink opened 1 year ago
thanks for reporting it!
I've seen this issue before as well. I found that this line 'set autologut 15' also appears to cause issues.
One server had these lines:
TMOUT=900 export TMOUT readonly TMOUT set autologout 15
The symptom was the variable autologout was somehow replacing 'start, stop, status' in the failing script with 'autologout' .
script start|stop|status
became
script autologout | autologout | autologout
Commenting out 'set autologout' and 'readonly TMOUT' resolved the issue. Strange indeed.
Yes, I have also noticed this issue with multiple customers. Anything that has "set" meaning that it is setting a custom variable in the profile, which causes the installation to fail.
the issue due to installation calls . /etc/profile
to get environment variables.
https://github.com/microsoft/SCXcore/issues/164 also due to the calling script failed.
On our hardened instances of RHEL the postinstallation script embedded in scx fails, which causes the SSL certs to not be properly generated, or even existing certificates being removed during upgrades.
We work around it for upgrades by removing the file
/etc/opt/omi/ssl/.omi_cert_marker
that the scx script is looking for. Removing the readonly TMOUT is not an option as it is required by our security policy.I've observed this behavior on all supported versions of RHEL. I've verified the script exits at sourcing /etc/profile by extracting it and running the script manually using
sh -x