NW 11 setup throwing internal error after new deployment

[GayathriPulla]

Hi All, 
We have deployed NW 11 as new fresh instance before implementing into production, but it showing the following while I click on any new tab as shown in below screenshot. 

[JoshRandall]

Hi Gayathri,

You'll usually see this "internal-error” message if you log in to the UI before all of the background services have fully started up.  While the login screen will be available nearly immediately upon appliance bootup, all the background services generally take a bit longer (maybe 5-10 minutes) to fully startup.

[GayathriPulla]

Hi Joshua, 
Still I am facing the same error, it has been hours since the server started. 

do u have any idea, what services have to be checked on the server?

[JoshRandall]

If you can SSH into the appliance and run "top,” you'll get an idea which processes are using the most resources.  If any java processes are taking up large amounts of CPU, that is one of the better indicators that the UI is still in the process of starting up.

Since enough time has passed that this should no longer be the case, I'd suggest trying to use a different browser, clearing the browser cache, or checking that javascript is enabled in the browser.

If none of those help, then from your SSH session you can try restarting the UI service (nginx) with the following command:

# systemctl stop nginx

# systemctl start nginx

You can check for proper startup of nginx with:

# systemctl status nginx

If you see any errors or warnings in that status printout, please let us know.

[GayathriPulla]

No error reported in the status but in the console same error is being shown

[i_bugti]

Hello Team I am facing the same issue.  Need support to resolve this issue. But in my situation I did not upgrade to any version. It appears suddenly. .

[JohnSnider]

Is this on our hardware, or is it virtual, or on third party hardware?  How much memory does the box have?

[JohnKisner]

i_bugti, 

If you are having an issue I highly suggest opening a support case in the Case Portal here in RSA Link to allow our Support team to take a closer look at what you are experiencing. Given this thread was originally opened in 2018 it is unlikely that you are having the same issue with the current versions of NetWitness as was seen in this thread.

[JulieBurgoyne]

Have you opened a case with the NetWitness support team. We'd be happy to assist you further and troubleshoot the issue.

[i_bugti]

Hi, problem had been resolved after restarting the Jetty service.