Validating error for SASAppVA Servers

[woo]

Hello, 

Trying to validating "SASAppVA Logical Pooled Workspace Server" and "SASAppVA Logical Stored Process Server" after login into SMC with "sasadm@saspw" but receives below error. 

The application could not log on to the server "server-name:8701". No Server is available at that port on that machine

Detail message at SMC shows connection refused. 

Tried validating with "sas" id (installed id) which is defined locally but still same message. We are using methods=pam with LDAP configuration. 

below command shows nothing is running on VA server 

netstat -an | grep 8701

netstat -an | grep 8601

any comments? 

[gwootton]

Sounds like the object spawner did not bind the port for these servers. The log for the Object Spawner when it first started will indicate why not. This could be because the password in metadata for sassrv is incorrect or another process was bound to the port when the Object Spawner started, or that the server is not assigned to that spawner.

[woo]

Thank you @ gwootton

Those ports are assigned to appropriate VA services, checked the console log. 

so then i might need to change the sassrv pwd following this doc 

https://documentation.sas.com/doc/en/bicdc/9.4/bisecag/p0kb2gtnuyjnrnn1hduu5by88u4f.htm

[gwootton · Accepted solution]

If the issue is with the credentials, the log will say so:

2021-07-30T16:38:01,629 INFO [00000030] :sas Audit.Authentication - Access denied.
2021-07-30T16:38:01,629 WARN [00000030] :sas App.ObjectSpawner - The credentials specified for the SASApp - Stored Process Server (A5RWD7FM.AZ00000B) server definition failed to authenticate. Therefore this server definition will not be included.
...
2021-07-30T16:38:01,651 WARN [00000030] :sas App.ObjectSpawner - The SASApp - Logical Stored Process Server (A5RWD7FM.AX000007) cluster does not contain any valid server definitions. Therefore this cluster definition will not be included.

You also won't see an "Activated listen..." message regarding the port:

[sas@trcv003 Logs]$ grep 8601 ObjectSpawner_2021-07-30_trcv003_8114.log
2021-07-30T16:38:01,612 INFO [00000030] :sas App - Reserved IPv6 port 8601 for server listen (connection 3).
[sas@trcv003 Logs]$ grep 8591 ObjectSpawner_2021-07-30_trcv003_8114.log
2021-07-30T16:38:01,650 INFO [00000030] :sas App - Reserved IPv6 port 8591 for server listen (connection 22).
2021-07-30T16:38:01,696 INFO [00000030] :sas App - Activated listen on IPv6 port 8591 (connection 22).
[sas@trcv003 Logs]$

[woo]

infect object spawner log for VA says that,

:sas - Access denied. 

:sas - The credentials specified for the SASAppVA - Pooled Workspace Server () server definition failed to authenticate. Therefore this server definition will not be included. 

:sas - Reserved IPv6 port 8601 for server listen (connection 5)

i am not quite sure why it is pointing to IPv6, where we have accepted default set up for "ipv4" when deployment happening. 

Also, if i grep for 8601 for that log, it says, 

:sas - Reserved IPv6 port 8601 for server listen (connection 5). 

grep for 8591

:sas - Reserved IPv6 port 8601 for server listen (connection 9). 

:sas - Activated listen on IPv6 port 8591 (connection 9). 

[woo]

so looks like its password issue then

[gwootton]

Yes, the issue is that the credentials you have configured for to start these servers are unable to authenticate. The IPv6 just means it's using a port/library that supports both IPv4 and IPv6.