unable to take the GUI of SA Server after initial configuration

[DeepanshuSood1]

Hi,

As in my new project i m facin one issue with the RSA SA Server, after the initial configuration on the sa server and other components, now I am not able to take the console of the security analytic server, below is the error message what i am getting while tryin to take the console.

I have checked the all services on by SA server by takin the ssh of it.

please suggest what could be issue with it and also i had restarted the jettysrv service even tough, but still it's not working.

Regards,

Deepanshu Sood.

[CindyCelata]

check these:

[root@saserver ~]# service rsa-im status

RSA Security Analytics Incident Management :: Server is running (2548).

[root@saserver ~]# service rsa-sms status

RSA NetWitness SMS :: Server is running (2697).

also mcollective, rabbitmq-server, ruby, cas.

if one process fails to kick off at boot time, it can cause a domino affect.  if you have not done so already reboot the box.

if it still fails to start, gather /var/lib/netwitness/uax/logs/sa.log and the latest threaddump.log and most current stderrout.log from /opt/rsa/jetty9/logs and open a support case.  u will also want to advise if you attempted to change the hostname after you performed the intial start up, because that also prevents jetty from kicking off.

[DeepanshuSood1]

Hi Cindy,

Actually I had done the above mentioned success but no success.

Now I thinkin to update it to 10.5.1.0, and then will check how it will work.

Thanks for your support.

Regards,

Deepanshu Sood.

[DavidPoirier]

Hi,

Can you try one thing for me on that SA Head unit?

sed -i
's/java-1.8.0-openjdk-1.8.0.51-1.b16.el6_7.x86_64\/jre/jre-1.8.0-openjdk.x86_64/g'
/etc/puppet/modules/rsa-java/manifests/init.pp

This is a one line command.

David

[DavidPoirier]

Hi,

Is this version 10.5?

Thank you

David

[DeepanshuSood1]

Yeah. 10.5.0

Thanks,

Deepanshu Sood

Consultant (Info Sec) - Professional Services

+91 995-377-0806

[DeepanshuSood1 · Accepted solution]

Hi All,

The issue get resolved by changing the hostname of the SA server.

I was initially putting the name of the SA server, i.e., RSA_SA.

But SA doesn't support alaphanumeric characters, so I changed the name to RSASA and then rebooted the server and the problem get resolved just by changing the name of it.

Thanks all for your responses.

Best Regards,

Deepanshu Sood.

[DavidPoirier]

Hi Deepanshu,

Nice work!

David

[DeepanshuSood1]

Thanks David.

Regards,

Deepanshu Sood