During the installation of SCOM agent on RHEL servers I encountered the following error message during the process of signing agent's certificate:
Exception message: Unable to create certificate context
; {ASN1 bad tag value met.
}
The message quite unusual - apart from one previous case I could not find any other reference to this problem associated in any way with SCOM.
Exception message: Unable to create certificate context
; {ASN1 bad tag value met.
}
The message quite unusual - apart from one previous case I could not find any other reference to this problem associated in any way with SCOM.
Resolution:
The only suggested solution - a firewall problem has been ruled out in first place. After trying several approaches it turned out, that during certificate signing process, SCOM agent was trying to use the older versions of two particular libraries, that the ones present on the system, and failed due to this. The workaround applied was creation of the symbolic links named as the old library file pointing to the new files with the following commands and manually re-initiating certificate signing process:
cd /usr/lib
sudo ln -s libcrypto.so.1.0.1e libcrypto.so.1.0.0
sudo ln -s libssl.so.1.0.1e libssl.so.1.0.0
sudo /opt/microsoft/scx/bin/tools/scxsslconfig -f -v
sudo ln -s libcrypto.so.1.0.1e libcrypto.so.1.0.0
sudo ln -s libssl.so.1.0.1e libssl.so.1.0.0
sudo /opt/microsoft/scx/bin/tools/scxsslconfig -f -v
Following up on the threads suggesting this approach (even though for a different problem) I figured out, that the problems reported to have been fixed with that script were mitigated with the release of next Cumulative Update for Management Pack for UNIX and Linux Operating Systems. After verification it turned out, that the agent binaries were taken from SCOM 2012 R2 Sp1 iso and didn't contain the latest fixes applied to the Management Pack. After downloading the latest version of the binaries the "ASN1 bad tag value" problem disappeared for all the Linux servers
