topic Re: Sas grid resource issue -validation issue in Administration and Deployment

Sas grid resource issue -validation issue

sathya66 — Thu, 06 Feb 2025 21:18:50 GMT

Hi all,

Trying to validate the grid server and workspace but I am getting below error.

ERROR [00000565] :sas - PROVIDER(Platform): Request from non-LSF host rejected
ERROR [00000565] :sas - An invalid grid resource was requested or the resource was not associated with any grid node.
ERROR [00000495]sas - An invalid grid resource was requested or the resource was not associated with any grid node.
ERROR [00000495] :sas - The launch of server SASApp - Workspace Server for user sas failed.
ERROR [00000495] :sas - The specified uuid DA4E-823F-8938AFF2B492 did not match any process managed by this spawner.

Workspace validation from SMC

INFO: Starting extended validation for Workspace server (level 1) - Making a connection
SEVERE: An invalid grid resource was requested or the resource was not associated with any grid node.
SEVERE: The launch of server SASApp - Workspace Server for user sasdemo failed.
SEVERE: Failed to start the server.
SEVERE: The application could not connect to any server in the cluster

SASApp resources are added in the lsf_cluster and shared and no luck

Thanks

Re: Sas grid resource issue -validation issue

gwootton — Thu, 06 Feb 2025 21:34:55 GMT

This error "Request from non-LSF host rejected" means the host submitted the request to the grid is not defined in LSF as a grid server or client. LSF does this check based on a reverse DNS lookup on the IP address, so assuming the host where the object spawner is running is configured as an LSF server, you may need to configure an LSF hosts file to match the IP address to the name as it is defined in the LSF configuration.

Re: Sas grid resource issue -validation issue

sathya66 — Thu, 06 Feb 2025 21:56:04 GMT

You mean in the /etc/hosts or in the hosts file in lsf conf directory?
We have done this . We just restarted only lsf and pm services. Do we need to restart all SAS services ( meta, compute) as well?

Re: Sas grid resource issue -validation issue

gwootton — Thu, 06 Feb 2025 21:54:07 GMT

LSF would use either. Ideally, this information would be in DNS, but you can provide it to /etc/hosts which is read when performing lookups as well. If you want this information to only be available to LSF, you can use the LSF hosts file.

What is needed is for LSF to be able to resolve the IP address making the request back to a configured LSF client.

Re: Sas grid resource issue -validation issue

doug_sas — Fri, 07 Feb 2025 14:40:03 GMT

In the grid server metadata under the Options tab would be a field named 'Required Resources'. If that field has a value in it (like 'SASApp'), then one of the hosts in the LSF cluster has to have that resource name associated with it as a boolean resource in the lsf.cluster.<cluster-name> file.

Re: Sas grid resource issue -validation issue

sathya66 — Thu, 13 Feb 2025 16:51:35 GMT

Everything looking good on setup wise. Looks like AES encryption ERROR. See below.
We have tested in TEST environment, it is working fine but issue is with PROD

2025-02-13T16:29:51,873 INFO [00000094] :sasdemo - New client connection (13) accepted from server port 8591 for user sasdemo. Encryption level is Everything using encryption algorithm AES. Peer IP address and port are [::ffff:11.87.120.33]:58440 for APPNAME=ConnectionService 904801.
2025-02-13T16:29:52,007 INFO [00000094] :sasdemo - Created process 486901 using credentials sasdemo (child id 0).
2025-02-13T16:29:58,773 ERROR [00000109] :sas - Encryption run-time execution error
2025-02-13T16:29:58,773 INFO [00000109] :sas - Client connection 13 for user sasdemo closed.
2025-02-13T16:29:58,913 INFO [00000111] :sas - Process 0 (originally 486901) for user sasdemo (child id 0) has ended.

Re: Sas grid resource issue -validation issue

gwootton — Fri, 14 Feb 2025 16:53:57 GMT

If you have FIPS openssl on your host you may need to add the -encryptfips option to your object spawner's usermods. For example in ObjectSpawner_usermods.sh adding:

USERMODS="$USERMODS -encryptfips "