BookmarkSubscribeRSS Feed
Dylan_ketcher
Calcite | Level 5

Good day, 

 

I am having a problem with Validating some servers after the config. We deployed Lev1 on our server and I'm following the instruction.html for the post config. It tells me that i need to validate the Logical Pooled Workspace Server but when I do it I get this error.

[8/30/18 1:25 PM] INFO: Starting extended validation for Pooled Workspace server (level 1) - Making a connection
[8/30/18 1:25 PM] SEVERE: Connection refused
[8/30/18 1:25 PM] SEVERE: The application could not log on to the server "Server:8701". No server is available at that port on that machine.

 

I did a grep command and I cant even find that port. We do have a few older deployments of this server though all the services are stopped, but once I go on the new deployment and do a server status check on the Pooled Workspace Server it just come back blank and cant start or stop it. How can I check what is using this port to I can stop those servers or what? 

 

I'm also trying to use the Schedule Manager but is it saying the "Unable to connect to the scheduling server 'SAS Distributed In-Process Services Scheduling Server'."

 

I don't know if this has something to do will the Validation as well i'm just asking 

 

We are running version 9.4M5. 

Thank you very much. 

3 REPLIES 3
Kurt_Bremser
Super User

Pooled and non-pooled workspace servers, as well as stored process servers are started by the object spawner. The object spawner is the process that needs to listen on the relevant ports, and it reads the ports from metadata; that's why you won't find them in any configuration file.

So you need to check if the object spawner is up and running, if the servers have been configured into the object spawner, and the object spawner log to see if it experienced a problem when setting up a specific server. If you have more pooled servers (pooled WS and stored process) defined than default, you may have to increase the available PortBank connections for the workspace server.

Dylan_ketcher
Calcite | Level 5

The Object Spawner is started, I took a look at the logs and this is what I am receiving. 

 

2018-08-30T13:59:22,500 INFO [00000030] :sasinst - Reserved IPv6 port 8581 for administrator listen (connection 2).
2018-08-30T13:59:22,500 INFO [00000030] :sasinst - Reserved IPv6 port 8451 for server listen (connection 3).
2018-08-30T13:59:22,501 INFO [00000030] :sasinst - Reserved IPv6 port 8701 for server listen (connection 4).
2018-08-30T13:59:22,515 INFO [00000030] :sasinst - Access denied.
2018-08-30T13:59:22,516 WARN [00000030] :sasinst - The credentials specified for the SASApp - Pooled Workspace Server (A52YC7IP.AY000007) server definition failed to authenticate. Therefore this server definition will not be included.
2018-08-30T13:59:22,516 INFO [00000030] :sasinst - Reserved IPv6 port 8601 for server listen (connection 5).
2018-08-30T13:59:22,516 INFO [00000030] :sasinst - Reserved IPv6 port 8611 for server listen (connection 6).
2018-08-30T13:59:22,516 INFO [00000030] :sasinst - Reserved IPv6 port 8621 for server listen (connection 7).
2018-08-30T13:59:22,516 INFO [00000030] :sasinst - Reserved IPv6 port 8631 for server listen (connection 8).
2018-08-30T13:59:22,526 INFO [00000030] :sasinst - Access denied.
2018-08-30T13:59:22,526 WARN [00000030] :sasinst - The credentials specified for the SASApp - Stored Process Server (A52YC7IP.AY000008) server definition failed to authenticate. Therefore this server definition will not be included.
2018-08-30T13:59:22,526 INFO [00000030] :sasinst - Reserved IPv6 port 8591 for server listen (connection 9).
2018-08-30T13:59:22,527 INFO [00000030] :sasinst - Reserved IPv6 port 43797 for launched server connect back listen (connection 10).
2018-08-30T13:59:22,527 INFO [00000030] :sasinst - Activated listen on IPv6 port 43797 (connection 10).
2018-08-30T13:59:22,527 WARN [00000030] :sasinst - The SASApp - Logical Pooled Workspace Server (A52YC7IP.AW000005) cluster does not contain any valid server definitions. Therefore this cluster definition will not be included.
"ObjectSpawner_2018-08-30_server_837.log" 51L, 6394C

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 3083 views
  • 1 like
  • 2 in conversation