topic Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed in Administration and Deployment

Logical Pooled Workspace Server and Logical Stored Process Server validation failed

SAS_LuisBolivar — Sat, 26 Mar 2022 13:46:45 GMT

Good morning community.

I would like your help with the following problem.

In a sas environment composed of 1 Metadata server, 3 applications and 1 web, the following problem occurs:

Error when validating the Logical Pooled Workspace Server:

Error when validating the Logical Stored Process Server:

In the Objspawn log file we see the following:

2022-03-26T09:09:28,664 INFO [00000031] :sas - Processing parsed configuration results.
2022-03-26T09:09:28,664 INFO [00000031] :sas - Objspawn is proceeding with the configuration results processing utilizing the A5NQO0H3.AY000004 spawner definition.
2022-03-26T09:09:28,665 INFO [00000031] :sas - Reserved IPv6 port 8581 for administrator listen (connection 2).
2022-03-26T09:09:28,665 INFO [00000031] :sas - Reserved IPv6 port 8451 for server listen (connection 3).
2022-03-26T09:09:28,665 INFO [00000031] :sas - Reserved IPv6 port 8701 for server listen (connection 4).
2022-03-26T09:09:30,865 INFO [00000031] :sas - Access denied.
2022-03-26T09:09:30,865 WARN [00000031] :sas - The credentials specified for the SASApp - Pooled Workspace Server (A5NQO0H3.AY000008) server definition failed to authenticate. Therefore this server definition will not be included.
2022-03-26T09:09:30,865 WARN [00000031] :sas - The password obtained from the metadata indicates that it was obtained by a user that has unrestricted access. Please check your configuration.
2022-03-26T09:09:30,866 WARN [00000031] :sas - Unrestricted access can include being an unrestricted user, or being a member of the SAS Administrators group, or being a member of any group that has the role Metadata Server: User Administration.
2022-03-26T09:09:30,866 INFO [00000031] :sas - Reserved IPv6 port 8601 for server listen (connection 5).
2022-03-26T09:09:30,866 INFO [00000031] :sas - Reserved IPv6 port 8611 for server listen (connection 6).
2022-03-26T09:09:30,866 INFO [00000031] :sas - Reserved IPv6 port 8621 for server listen (connection 7).
2022-03-26T09:09:30,866 INFO [00000031] :sas - Reserved IPv6 port 8631 for server listen (connection 8).
2022-03-26T09:09:32,990 INFO [00000031] :sas - Access denied.
2022-03-26T09:09:32,990 WARN [00000031] :sas - The credentials specified for the SASApp - Stored Process Server (A5NQO0H3.AY000009) server definition failed to authenticate. Therefore this server definition will not be included.
2022-03-26T09:09:32,990 WARN [00000031] :sas - The password obtained from the metadata indicates that it was obtained by a user that has unrestricted access. Please check your configuration.
2022-03-26T09:09:32,990 WARN [00000031] :sas - Unrestricted access can include being an unrestricted user, or being a member of the SAS Administrators group, or being a member of any group that has the role Metadata Server: User Administration.
2022-03-26T09:09:32,991 INFO [00000031] :sas - Reserved IPv6 port 8591 for server listen (connection 9).
2022-03-26T09:09:32,991 INFO [00000031] :sas - Reserved IPv6 port 37179 for launched server connect back listen (connection 10).
2022-03-26T09:09:32,991 INFO [00000031] :sas - Activated listen on IPv6 port 37179 (connection 10).
2022-03-26T09:09:32,991 WARN [00000031] :sas - The SASApp - Logical Pooled Workspace Server (A5NQO0H3.AW000005) cluster does not contain any valid server definitions. Therefore this cluster definition will not be included.
2022-03-26T09:09:32,991 WARN [00000031] :sas - The SASApp - Logical Stored Process Server (A5NQO0H3.AW000006) cluster does not contain any valid server definitions. Therefore this cluster definition will not be included.
2022-03-26T09:09:32,991 INFO [00000031] :sas - Activated listen on IPv6 port 8591 (connection 9).
2022-03-26T09:09:32,991 INFO [00000031] :sas - Activated listen on IPv6 port 8451 (connection 3).
2022-03-26T09:09:32,991 INFO [00000031] :sas - Activated listen on IPv6 port 8581 (connection 2).
2022-03-26T09:09:33,001 INFO [00000005] :sas - SAS Object Spawner Daemon III is running under the user identity sas.
2022-03-26T09:09:33,001 INFO [00000005] :sas - SAS Object Spawner Daemon III has completed initialization.
2022-03-26T09:09:33,001 INFO [00000005] :sas - SAH021999I Server SAS Object Spawner Daemon III (8581), State, running

When validating the PoolerWorkSpace from the terminal with the sassrv user, it enters without problem.

Can you help me locate the problem, thank you very much.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

Sajid01 — Sat, 26 Mar 2022 22:35:56 GMT

Hello @SAS_LuisBolivar
From the log we see theerrors shown below. Therefore validation would obviously fail.

Make sure you have used a valid account for validating the workspace server / Stored Process server. (such as sassrv or sasdemo. The account should exist in the host . No internal account please.)

See here for details. (https://go.documentation.sas.com/doc/en/bicdc/9.4/biig/n05021intelplatform00install.htm)

Errors in the logs.

2022-03-26T09:09:28,665 INFO [00000031] :sas - Reserved IPv6 port 8701 for server listen (connection 4).
2022-03-26T09:09:30,865 INFO [00000031] :sas - Access denied.
2022-03-26T09:09:30,865 WARN [00000031] :sas - The credentials specified for the SASApp - Pooled Workspace Server (A5NQO0H3.AY000008) server definition failed to authenticate. Therefore this server definition will not be included.
2022-03-26T09:09:30,865 WARN [00000031] :sas - The password obtained from the metadata indicates that it was obtained by a user that has unrestricted access. Please check your configuration.

------------------

2022-03-26T09:09:32,990 INFO [00000031] :sas - Access denied.
2022-03-26T09:09:32,990 WARN [00000031] :sas - The credentials specified for the SASApp - Stored Process Server (A5NQO0H3.AY000009) server definition failed to authenticate. Therefore this server definition will not be included.

----------------------

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

SAS_LuisBolivar — Sun, 27 Mar 2022 14:39:32 GMT

Hello.

Validate the services with the sasdemo user and the same error is presented.

Verify that user the sastrust user does not have the admin role.

Validate by logging in to sas mc with the sassrv user that I have not been assigned any special permission. Everything is in order.

But the error still occurs.

It seems strange to me that the SAS object spawner can be validated without problems for two of the three Application servers.

On the third server it gives me the following error:

The service is up and is listening.

Thanks.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

SASKiwi — Sun, 27 Mar 2022 19:51:38 GMT

Normally you use the sassrv account for these servers and it is defined with the server properties in SMC. Is this the account you are using? Is this a first-time configuration of a SAS installation or was it previously working and now it is not?

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

SAS_LuisBolivar — Sun, 27 Mar 2022 19:54:21 GMT

Good afternoon. It is an initial configuration. Thanks.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

Sajid01 — Sun, 27 Mar 2022 21:21:50 GMT

Hello
If it is an initial configuration, perform a systematic shutdown and restart.
Hopefully everything should work.
Normally SAS installations with your configuration work out of the box.
Use sassrv or sasdemo or their corresponding accounts if you have named them differently.
If there is an issue please post the logs.
SAS Tech Support is very helpful. You can submit a ticket there too.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

SASKiwi — Sun, 27 Mar 2022 21:27:33 GMT

In that case you need to ensure that these servers are defined with an service account that is defined with the correct permissions both in Linux and in SAS metadata.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

SAS_LuisBolivar — Sun, 27 Mar 2022 21:37:38 GMT

Greetings, good afternoon. I need to validate the permissions on Linux, the user is part of the sas group. What are the correct permissions? Thanks

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

Sajid01 — Sun, 27 Mar 2022 22:26:54 GMT

Unlike in windows, Linux has no special requirements like login as batch as in windows.
Please check that you have created the required accounts.
The SAS documentation is clear and straightforward.
In your situation, I would first do a clean restart.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

SASKiwi — Mon, 28 Mar 2022 01:27:25 GMT

As far as metadata definitions are concerned, the service account sassrv should belong to the SAS users and SAS administrators metadata groups. I'm not familiar with the linux setup so would have to go searching in the documentation.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

Sajid01 — Mon, 28 Mar 2022 08:01:54 GMT

There is absolutely nothing to worry about Linux.
Linux is a simple operating system.
If you want to check the groups a user is in,
Just run id username in the shell.
It will display the groups a user is in.
Linux Admin can always be requested for help.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

gwootton — Mon, 28 Mar 2022 12:33:05 GMT

The stored process server and pooled workspace server are failing to validate because the SAS Trusted User account has been given the unrestricted or user administration roles (either directly or indirectly), which prevents it from retrieving the password:

2022-03-26T09:09:30,865 WARN [00000031] :sas - The credentials specified for the SASApp - Pooled Workspace Server (A5NQO0H3.AY000008) server definition failed to authenticate. Therefore this server definition will not be included.
2022-03-26T09:09:30,865 WARN [00000031] :sas - The password obtained from the metadata indicates that it was obtained by a user that has unrestricted access. Please check your configuration.
2022-03-26T09:09:30,866 WARN [00000031] :sas - Unrestricted access can include being an unrestricted user, or being a member of the SAS Administrators group, or being a member of any group that has the role Metadata Server: User Administration.

Given you have provided a screen shot of the SAS Trusted User memberships and it doesn't show these roles, I'd check the properties of those groups it is a member of to confirm none of them have the Metadata Server: Unrestricted or Metadata Server: User Administration roles.

Once you've removed the role wherever it is being assigned, restart the object spawner and it should bind to the ports to allow validation.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

SAS_LuisBolivar — Mon, 28 Mar 2022 19:40:26 GMT

I have managed to overcome the error.

Thanks to each of your comments.

He had a group with sasadministrator and sasusers roles.

But now I have the following error:

2022-03-28T12:17:35,568 ERROR [00000148] :sasadm - Objspawn was unable to launch the server SASApp - Stored Process Server (A5NQO0H3.AY000009) due to the server launch exceeding the specified wait time.

2022-03-28T12:17:35,568 ERROR [00000148] :sasadm - An error occurred while server (A5NQO0H3.AZ00000C_!A5NQO0H3.AY000004_@xxxxxxxxxxx) was starting. Now attempting a different server.

2022-03-28T12:17:35,568 ERROR [00000148] :sasadm - The Balance algorithm timed out before a server could be found. 2022-03-28T12:17:35,568 INFO [00000148] :sasadm - Failed to redirect client to available server in cluster SASApp - Logical Stored Process Server (A5NQO0H3.AW000006). Can you help me, please. Thanks.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

gwootton — Mon, 28 Mar 2022 19:45:57 GMT

Are you seeing any errors in the Stored Process Server log (<SASConfig>/Lev1/SASApp/StoredProcessServer/Logs)? It sounds like the Object Spawner is trying and failing to start the process.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

SAS_LuisBolivar — Mon, 28 Mar 2022 19:58:28 GMT

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

gwootton — Mon, 28 Mar 2022 20:09:34 GMT

Looks like the session is taking 2 minutes to start up (first datestamp line is 12:50, fourth is 12:52). I suspect this has something to do with it timing out while trying to resolve its hostname given where the delay is happening, so a DNS issue. You could increase the timeout to something greater than 2 minutes (this is in the properties for the logical server's "load balancing" tab) to allow validation to succeed. To fix the delay will likely mean looking into the host's DNS configuration to ensure the DNS server(s) respond quickly and can resolve the hostname of all the hosts in the environment, or that all the hosts in the environment are defined in a hosts file to circumvent the DNS server.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

SAS_LuisBolivar — Mon, 28 Mar 2022 20:31:23 GMT

Good afternoon.
If it seems to me that it could be that, at the operating system level, how do I validate the DNS?
Thanks.

Re: Logical Pooled Workspace Server and Logical Stored Process Server validation failed

gwootton — Mon, 28 Mar 2022 20:49:54 GMT

You can use commands like nslookup or dig to perform name queries against the DNS. The DNS settings are usually in resolv.conf.