|Applies To||RSA Security Analytics|
RSA Security Analytics 10.3
RSA Security Analytics Server
|Issue||503 error when accessing the RSA Security Analytics 10.3 UI after changing the HOSTNAME parameter in /etc/sysconfig/network on the SA server.|
Unable to start the jettysrv service.
The following error is seen in /var/lib/netwitness/uax/logs/sa.log when attempting to start the jettysrv service, noting that where indicated in RED below, "SAHost" is the current hostname of the Security Analytics server, for which the parameter HOSTNAME was manually modified in configuration file /etc/sysconfig/network and/or /etc/hosts:
This issue occurred because the OS configuration files /etc/syconfig/network and /etc/hosts were manually edited in an attempt to change the hostname of the SA server.
While a hostname change was the desired result, attempting to perform this change by simply manually modifying /etc/hosts and/or /etc/sysconfig/network to reflect the new hostname will not change other configuration data associated with the webcontainer jetty. You must use NwConsole to make a hostname change. Failure to do so will result in rendering jetty to be inoperatable until NwConsole is run. In this example, the HOSTNAME parameter was changed in /etc/sysconfig/network, and also in /etc/hosts. This will not update jetty to reflect the new hostname. As a repercussion of this incorrect change, jetty is not functional.
To change the hostname of the RSA Security Analytics server, login to the SA server as root. Then from the command line, run the following command, noting the following example names used in syntax below for demonstration purposes. Adjust the administrative user, password and hostname values accordingly:
admin = SA administrative user, password1! = admin users password SAHost= the new hostname that the SA server will be called:
NwConsole -c login localhost:50006 admin password1! -c appliance hostname=SAHost <hit return>
NOTE: The N and the C must be specified as upper case when using the NwConsole command. UNIX is case sensitive, and failure to use the correct case will result in "command not found" when attempting to execute if not properly specified.
|Notes||For additional information on how to use NwConsole to change other appliance configuration data, click here to see How to set up the network configuration on an RSA Security Analytics appliance using NwConsole|
|Legacy Article ID||a67111|