06-03-2016 08:12 AM
Hi, I am brand new to the SAS administration world so please forgive any ignorance on my part. I have no SAS programming background either. I do have other tool administration experience in the Linux world, so that is how I got volunteered to be the SAS admin.
I have recently installed SAS 9.4 on a Linux VM. The install went fine and I am able to run batch jobs with no problem.
However, when I try to connect using the SAS Management Console I get the following error:
Connection refused: connect
The application could not log on to the server "leustasas:8561". No server is available at that port on that machine.
From what I understand this message is telling me, I have not started the SAS server (listener?) and until I do that I will not be able to connect. This is where my research has fallen flat. I cannot figure out what command I need to run to start the server. I do struggle with how the SAS documentation is laid out, but there is talk of getting me some training. Soon, I hope...
Any guidance would be greatly appreciated.
06-03-2016 08:16 AM
this could be many things.
First, if you actually have a metadata server, as you daid, it could be that the sas service is not started.
Please go to your sas/Config/Lev1 and run ./sas.servers status.
Secondly, if it is started, and you still cannot log in:
1- try to run, from a command line: ping leustasas. If not working, then try with the full qualified name of leustasas. If this works, then on your connection you only need to replace the shortname by the full qualified hostname.
2- something else, as root, you can check (or ask your system admin) the iptables service (your linux firewall) if it is up and running, and if it is up and running you might need to check if you are actually able to connect, from the SAS Management Console computer, to the SAS Linux machine on the specified port.
06-03-2016 09:14 AM
06-03-2016 08:23 AM
Since you are able to run batch jobs, this means you have access to the UNIX commandline.
ps -ef|grep Meta
and you should get 3 processes, 2 shell scripts and the SAS process that runs the Metadata Server.
If not, as the user used during SAS installation, cd to
This should get the Metadata Server up and running
You will most probably have to repeat the same for the Object Spawner
06-03-2016 09:20 AM
Not looking good. Does not appear I have anything running, nor do I have that exact in order to start it.
[sas@leustasas /]$ ps -ef|grep Meta
sas 29214 23108 0 08:15 pts/0 00:00:00 grep --color=auto Meta
[sas@leustasas /]$ find . -name 'MetadataServer.sh*' 2>/dev/null
06-03-2016 09:24 AM
Did you go through the configuration phase of the installation process as well? In a multi-tier environment, you'll typically go through a process like this:
Metadata Server: Install software -> Configure Metadata server
Application Server: Install Software -> Configure App server
Middle Tier Server: Install Software -> Configure Midtier applications
OR, are there multiple servers for your SAS environment? Often you might have separate VMs for each tier, one for metadata, one for app tier, one for middle tier.
06-03-2016 09:24 AM
I Might be wrong, but I believe you have only SAS binaries, no metadata or object spawners yet.
When you are installing the software, you are prompted if you want to Install and/or Configure, and I believe you selected only Install
While you don;t have configured your software, you won;t have any service as Metadata or Application servers. Therefore, you cannnot connect with the SAS Management Console.
If you don't know how to configure SAS, pelase contact your SAS contact or you can read the guide: http://support.sas.com/documentation/cdl/en/biig/69172/PDF/default/biig.pdf
06-03-2016 09:47 AM
06-06-2016 06:36 AM