SAS VA ERROR

[japsas100]

Hi All, 

I am unable to open the SAS VA hub page after root the linux server. I alredy started the sas services. I am able to connect sas EG to sas serves.

SAS Web Infrastructure Data Server is UP
SAS Metadata Server 1 is UP
SAS Object Spawner 1 is UP
SAS DIP Job Runner 1 is UP
SAS Information Retrieval Studio Server is UP
SAS JMS Broker is UP
SAS Cache Locator Service ins_41415 is UP
SAS Web Server is NOT up
SAS Web App Server SASServer1_1 is UP
SAS Environment Manager is UP
SAS Environment Manager Agent is UP

please advise?

[AndrewHowell]

[This sounds more like a Tech Support question than a Communities discussion, BTW.]

Some questions to help pinpoint the issue:

• Do you have all mid-tier apps (including VA) installed in the one WebApp Server SASServer1_1? (If so, curious wny?)
• Can you start other WebApps (Stored Process Web Application, SAS Studio, etc)?
• Can you at least access the Web Server home page?

Compare your list of "UP" servers/services against those listed in the $SASCONFIG/Lev1/Documents folder. (This will also show you the location of the log files you'll need to examine.)

[Anand_V]

SAS Cache Locator Service ins_41415 is UP
SAS Web Server is NOT up
SAS Web App Server SASServer1_1 is UP

Above clearly shows SAS WebServer is NOT UP, could you please verify if it's UP or not?

Thanks,
Anand!

[JuanS_OCS · Accepted solution]

Hello @japsas100,

indeed, as @Anand_V mentioned, we need to focus on "SAS Web Server is NOT up".

For now, you can stop the middle tier services with ./sas.server.mid stop.

I would recommend also to archive and delete the logs under Web/WebServer/logs, then you can start the web server/httpd (only) with Web/WebServer/bin/httpdctl start.

Once you do this, try http/s://yourserver.com[:port] (without /SASVisualAnalytics) and check if there is any error. You could also check Web/WebServer/logs/error_xxxxxxx.log. This should give you more details which most of them can be follwed up with Google search (don't forget, this is a normal httpd service), or SAS Technical Support.

FYI: the errors on the httpd service normally come from problems on the network or a misconfiguration on conf/httpd.conf, sas.conf or conf/extra/httpd-ssl.conf.

After each iteration of start - fix/change - stop, I recommend you, for readibility, to archive (important) and delete the logs.

And when you are finished, you can start the middle tier services with ./sas.server.mid start, or just restart all the sas services with ./sas.servers restart