000016571 - 503 Error Displayed After Upgrading to RSA Security Analytics 10.3 SP3

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000016571
Applies ToRSA Security Analytics
RSA Security Analytics 10.3.3
RSA Security Analytics Server
RSA Security Analytics Broker
Issue503 Error Displayed After Upgrading to RSA Security Analytics 10.3 SP3.
Security Analytics 10.3.3 Web User Interface Post-upgrade Database Update.
After upgrading to RSA Security Analtyics 10.3.3 I encounter a 503 error when attempting to logon to the Security Analytics Web User Interface.
The Security Analytics Web User Interface fails to load after restarting the jettysrv service after upgrading to Security Analytics version 10.3.3.  The web user interface displays a 503 error when attempting to access the system through a web browser.
platform.h2.db error in the RSA Security Analytics Server.
CauseDuring the upgrade, invalid records are inserted into the platform.h2.db database used by jettysrv.  These entries prevent jettysrv from starting and must be removed using the following steps. This only happens when customers have had Security Analytics 10.0 or Security Analytics 10.1 installed on the appliance and have upgraded to Security Analytics 10.3.3. 
Resolution

Fix


 


Please note the following:


This issue has been resolved and will be available in the latest version of 10.3 SP3 slated tentatively to release on May 21st. If you have already downloaded & installed 10.3 SP3 prior to May 21st and have encountered the issue noted above, please proceed to use the workaround instructions posted below.


 


Required Tools


SSH client


Java database tool from http://repo1.maven.org/maven2/com/h2database/h2/1.2.147/h2-1.2.147.jar


Optional Tools


SCP client such as WinSCP. 


 


Overview of Steps


Use these steps to remove the invalid entries from the platform.h2.db and allow jettysrv to start.


1.       Open an ssh session to your SA Broker or SA Server.


2.       Logon as root.


3.       Get the database tool necessary to execute sql commands on the database. 


a.       If the server has internet access you can execute the command from the command prompt


b.      If the server does not have internet access you will need to download the tool from another workstation and copy it to the /var/lib/netwitness/uax/db folder. 


4.       Stop the jettysrv service.


5.       Change into the /var/lib/netwitness/uax/db folder.


6.       Backup the existing platform.h2.db file.


7.      Run the sql tool and execute the two sql delete commands. 


a.       At this point the Bash prompt will be replaced by the sql prompt.


b.      The results of sql commands are echoed to the console as soon as the command is executed.


8.       Exit from sql.


9.       Start the jettysrv service.


10.   Verify that the Security Web User Interface is responsive. 


 


Detailed Steps


1.       Open an ssh session to your SA Broker or SA Server.


2.       Logon as root.


3.       Get the database tool necessary to execute sql commands on the database.


wget http://repo1.maven.org/maven2/com/h2database/h2/1.2.147/h2-1.2.147.jar


4.       Stop the jettysrv service.


root@SA-Server-01 ~]# stop jettysrv {enter}


5.       Change into the /var/liv/netwitness/uax/db folder.


root@SA-Server-01 ~]# cd /var/lib/netwitness/uax/db {enter}


6.       Backup the existing platform.h2.db file.


root@SA-Server-01 ~]# cp platform.h2.db platform.h2.db.bad {enter}


7.       Run the sql tool and execute the two sql delete commands.


root@SA-Server-01 ~]# java -cp ./h2-1.2.147.jar org.h2.tools.Shell -url jdbc:h2:file:platform


sql> DELETE FROM QRTZ_TRIGGERS WHERE JOB_NAME = 'SystemUpdateStatus';


sql> DELETE FROM QRTZ_JOB_DETAILS WHERE JOB_NAME = 'SystemUpdateStatus';


8.       Exit from sql.


sql> quit


9.       Start the jettysrv service.


root@SA-Server-01 ~]# start jettysrv {enter}


10.   Verify that the Security Web User Interface is responsive. 


a.       Wait 3 to 7 minutes for jettysrv to fully load and then open a browser and logon to your Security Analytics Server or Broker and verify that the interface is fully functional.


 

WorkaroundSoftware upgrade from RSA Security Analytics from any version to RSA Security Analytics 10.3.3.
Legacy Article IDa65562

Attachments

    Outcomes