Hi Giri
It looks like you're using a FIPS compliant encryption key. Please go ahead and use the workaround below:
1. Open $clarity/.setup/scripts/commondeploy.xml with text editor
2. Scroll down to Line 454 <!-- Standard beacon properties -->
3. Now look in section starting at line 475, it should look like this:
<when value="wrapper.java.classpath">
<proputil file="@{config.file}">
<property name="wrapper.java.classpath" autoIncrementName="true" fileValue="${install.dir}/bin/wrapper.jar" comment="Java Classpath"/>
<property name="wrapper.java.classpath" autoIncrementName="true" fileValue="${install.dir}/lib/nsa.jar" />
[…]
4. Add the following three lines at the end of the list (line 488):
<property name="wrapper.java.classpath" autoIncrementName="true" fileValue="${install.dir}/lib/cryptojce.jar" />
<property name="wrapper.java.classpath" autoIncrementName="true" fileValue="${install.dir}/lib/cryptojcommon.jar" />
<property name="wrapper.java.classpath" autoIncrementName="true" fileValue="${install.dir}/lib/jcmFIPS.jar" />
5. Save
6. Now run the following commands:
service stop remove beacon
service add beacon
service deploy beacon
service start beacon
This should work to bring the beacon up.
Hope this helps -Nika