XUA won't start after upgrading to v2.50

 export _RLD_LIB_PATH=<java-11-directory-of-libjvm.so>

 export _RLD_LIB_PATH=/usr/tandem/nssjava/jdk110_l11/lib/server

• Related Articles

• XMA: SLSENDER fails to start after upgrading to Merged Audit 2.65

  There is a known issue where SLSENDER will not start after upgrading to XMA 2.65. If the customer cannot start SLSENDER after upgrading, the post upgrade steps below can be used. If we know a customer will be upgrading to XMA 2.65, pre-upgrade steps ...

• XUA: No XUA audit records have been found since an FSE 43 occurred.

  After resolving the FSE 43, the XUA SEEP ($XUA) must be bounced to start auditing. Example: $SYSTEM XYGATEUA 4> XUA_SAFECOM_BOUNCE

• XS1 - Upgrading from Version 1.90 to Version 1.97

  Please review this entire KB before starting any upgrade from XS1 v1.90 to release 1.97. 1. Review the document "XS1 v1.97 Installation and Set Up Guide. It contains a section, "Upgrading from XS1 1.90 to 1.97" that contains steps to follow when ...

• XUA: How to stop XUA without logging on a Super.Super

  Use the following steps to create and run a program as Super.Super. 1)Create a program for stopping the $XUA process: STOPIT ?NOLIST ?SOURCE $SYSTEM.SYSTEM.EXTDECS0(STOP) ?LIST PROC testing MAIN; BEGIN INT a[0:3]; a ':=' "$XUA "; STOP (a); END; ...

• Errors starting XIC after upgrading to Version 1.30 from previous versions

  When upgrading to version 1.30 from a previous version, the following occurs: Rename the .ssh and .pem files as follows: XIC_EP.ssl to XIC_EP.ssl.bak XIC_PrivatePair.pem to XIC_PrivatePair.pem.bak XIC_PubKey.pem to XIC_PubKey.pem.bak XIC_XTR_EP.ssl ...