VA LASR services not starting

[woo]

we have sas 9.4, va 7.3 on Linux 6.8 VMs

when I try to start VA services "runsas.sh" from ".../usr/local/web/rmg/sasconfig/Lev1/Applications/SASVisualAnalytics/VisualAnalyticsAdministrator/VALIBLA" I see below error message. I tried removing PID, making sure nothing is running with "SAS" and restarting service but that is not helping.

ERROR: A connection to the LASR Analytic Server on 'company.com', port 10011, could not be made. Make sure that the host and port are correctly specified, that you are attempting to connect to a LASR Analytic Server of the correct vintage, and
that the server is still running.

visual analytics public server script "runsas.sh" throwing same error.

I checked "visual analytics lasr" and "visual analytics public server" library has not matching "server tag" + read some notes but not getting it right.

Any thoughts?

[JuanS_OCS]

Hello @woo,

can you check if there is a service already listening in that port with "netstat -naop | grep 10011" or the process is running with "ps -ef | grep VALIBLA".

If any, kill the process and try to run it again.

[woo]

thanks Juan, I checked that but there is no service listening there nor any processes running with VALIBLA.

however, if I try to run "runsas.sh" script from ".../Lev1/Applications/SASVisualAnalytics/VisualAnalyticsAdministrator"

this shows "autoload still running with specific pid" -> when I try to kill it (kill -9 pid> it says "no such process"

script under ".../Lev1/Applications/SASVisualAnalytics/VisualAnalyticsAdministrator" brings up port 10031 and script under ".../Lev1/Applications/SASVisualAnalytics/VisualAnalyticsAdministrator/VALIBLA" brings up port 10011.

when we run these scripts it creates new PIDs all the time.

Also, for server definitions, SMC, of these LASR Analytics -> services is defined as "http" where as "sas web application infrastructure definition for "sas va hub" is https.

[JuanS_OCS]

Hi again @woo

I am sorry, I am a bit confussed, I might need more information. In the first post you mention that VALIBLA AutoLoad cannot be started, but in your second post you say that it actually brings up the service. What am I understanding wrong?

Besides this little detail, what you mention is interesting, becasue metadata and scripts must be aligned: 

- first check in Web Infrastructure Platform your URLs, specially LASRAuthorization service. Check if it is http or https.

- Then, for the LASR server related, it is important that the URL for LAST authorization service should be same http, or https, and same port number.

[woo]

Thanks Juan.

I am sorry, I am a bit confussed, I might need more information. In the first post you mention that VALIBLA AutoLoad cannot be started, but in your second post you say that it actually brings up the service. What am I understanding wrong?

Actually, since those two scripts are not running we created customized script to start autoload job. Anyways, The error I posted in first post happens while trying VALIBLA script.

Besides this little detail, what you mention is interesting, becasue metadata and scripts must be aligned: 

- first check in Web Infrastructure Platform your URLs, specially LASRAuthorization service. Check if it is http or https.

config manager > sas app infrastructure

for LASR authorizations service,

    internal connection has - http/real host name/port123

    external connection has - https/alias for hostname/port456

- Then, for the LASR server related, it is important that the URL for LAST authorization service should be same http, or https, and

same port number.

under server manager, all server instaces, LASR Analytic server, public lasr, and model risk lasr has http/server host name/ 10011/10031/10121

so I see discrepancies there "config manager > sas app infrastructure" VS "server instance definition under server manager"

[JuanS_OCS]

Hello @woo,

what you need to check is the URL from the web app infrastructure, with the URL that appears in your LASR libraries. You will see the full URL to the LASR authorization service.

They need to point to the  internal one, and using the hostname instead of the external one (different IP).

The internal port and IP are very important because, the IP for external communication (probably reverse proxy) would have different rules in the firewall.

It is important to make a difference between the SASLASRAuthorization service, a web application (a REST API), and the LASR server itself.

The first one is clear, I think. The second one is just the sas.exe process that will load the data in memory. So port numbers are different by nature, don;t worry about it.