topic Re: SAS EG Connection Issue in Administration and Deployment

SAS EG Connection Issue

japsas100 — Wed, 08 Mar 2017 10:18:38 GMT

Recently we have installed sas on linux . We are not able to connect sas app server via SAS EG .

I am login with default sasdemo user id.

ERROR : 'Unable to connect to the metadata server'

We alredy verified all the below points.

like telnet hostname 8561 > no problem

correct host name and port 8561 or 8591

No firewall blocking

both port listening against hostname

connection validated (sasapp logical workspace server) in sas metadata client

Please advise?

Please see below log of objectspawner

Re: SAS EG Connection Issue

JuanS_OCS — Wed, 08 Mar 2017 11:00:06 GMT

Hello @japsas100,

when you connect to the metadata with SAS Management Console, are you using the same user than with SAS EG, or another user, such as sasadm@saspw?

In other hand, did you checked the logs on the SAS Metadata Server?

Re: SAS EG Connection Issue

japsas100 — Wed, 08 Mar 2017 11:19:21 GMT

I tried with other user such as sasadm@saspw but getting the same error.

Please see below metadata log: -

Please see below metadata error: -
2017-03-08T10:12:04,405 INFO [00000008] :sas - Processor initialized.
2017-03-08T10:12:04,406 INFO [00000008] :sas - Reserved IPv6 port 8561 for server listen (connection 1).
2017-03-08T10:12:04,407 INFO [00000008] :sas - Allowed trusted SAS Peer client type: SAS
2017-03-08T10:12:04,407 INFO [00000008] :sas - Trusted SAS Peer username: All client usernames are trusted.
2017-03-08T10:12:04,407 INFO [00000008] :sas - Trusted SAS Peer address: All client machine IP addresses are trusted.
2017-03-08T10:12:04,407 INFO [00000008] :sas - Trusted SAS Peer support has been enabled.
2017-03-08T10:12:04,407 INFO [00000008] :sas - Activated listen on IPv6 port 8561 (connection 1).
2017-03-08T10:12:04,413 INFO [00000004] :sas - SAH001999I SAS Metadata Server (8561), State, running
2017-03-08T10:12:12,947 INFO [00000025] :sastrust@saspw - New client connection (2) accepted from server port 8561 for user sastrust@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:xxx.xxx.xx.xxxx]:44761 for APPNAME=SAS Object Spawner.
2017-03-08T10:12:12,948 INFO [00000025] :sastrust@saspw - Request made to cluster SASMeta - Logical Metadata Server (A57LP4MN.AX000001).
2017-03-08T10:12:12,948 INFO [00000025] :sastrust@saspw - Redirect client in cluster SASMeta - Logical Metadata Server (A57LP4MN.AX000001) to server SASMeta - Metadata Server (A57LP4MN.AZ000001) at xxxxxxxxxxxxxx :8561.

Re: SAS EG Connection Issue

Kurt_Bremser — Wed, 08 Mar 2017 11:52:21 GMT

Locate the logfile of the metadata server, and then do a tail on it immediately after you tried to connect, and then post the lines you get.

Edit: replaced "objectspawner" with "metadata server"

Re: SAS EG Connection Issue

Kurt_Bremser — Wed, 08 Mar 2017 11:35:27 GMT

@japsas100 wrote:

I tried with other user such as sasadm@saspw but getting the same error.

Please see below metadata log: -

Please see below metadata error: -
2017-03-08T10:12:04,405 INFO [00000008] :sas - Processor initialized.
2017-03-08T10:12:04,406 INFO [00000008] :sas - Reserved IPv6 port 8561 for server listen (connection 1).
2017-03-08T10:12:04,407 INFO [00000008] :sas - Allowed trusted SAS Peer client type: SAS
2017-03-08T10:12:04,407 INFO [00000008] :sas - Trusted SAS Peer username: All client usernames are trusted.
2017-03-08T10:12:04,407 INFO [00000008] :sas - Trusted SAS Peer address: All client machine IP addresses are trusted.
2017-03-08T10:12:04,407 INFO [00000008] :sas - Trusted SAS Peer support has been enabled.
2017-03-08T10:12:04,407 INFO [00000008] :sas - Activated listen on IPv6 port 8561 (connection 1).
2017-03-08T10:12:04,413 INFO [00000004] :sas - SAH001999I SAS Metadata Server (8561), State, running
2017-03-08T10:12:12,947 INFO [00000025] :sastrust@saspw - New client connection (2) accepted from server port 8561 for user sastrust@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:xxx.xxx.xx.xxxx]:44761 for APPNAME=SAS Object Spawner.
2017-03-08T10:12:12,948 INFO [00000025] :sastrust@saspw - Request made to cluster SASMeta - Logical Metadata Server (A57LP4MN.AX000001).
2017-03-08T10:12:12,948 INFO [00000025] :sastrust@saspw - Redirect client in cluster SASMeta - Logical Metadata Server (A57LP4MN.AX000001) to server SASMeta - Metadata Server (A57LP4MN.AZ000001) at xxxxxxxxxxxxxx :8561.

There is no error in there. That is the log of the moment the spawner started and used sastrust to read its own metadata.

Re: SAS EG Connection Issue

japsas100 — Wed, 08 Mar 2017 11:57:29 GMT

I have deleted the log file generated earlier but now there is no file under /opt/sas/config/Lev1/ObjectSpawner/Logs.

Re: SAS EG Connection Issue

Kurt_Bremser — Wed, 08 Mar 2017 12:10:09 GMT

Restart everything from scratch, so that new, current log files are created.

ERROR : 'Unable to connect to the metadata server'

(from your initial post)

This comes from the failed attempt of the Enterprise Guide to connect to the metadata server when EG starts and works through the connection profile. If that does not give you a line in the metadata server log with the username you used in the profile in it, then EG did not reach the metadata server at all. Check the servername and connection port (which should be 8561 if default values are used) in the connection profile.

Once you have verified that you can reach the metadata server and have SASApp in the EG server list, try to open that. Then you should get a matching line in the spawner log.

Re: SAS EG Connection Issue

Kurt_Bremser — Wed, 08 Mar 2017 12:12:51 GMT

@japsas100 wrote:

I have deleted the log file generated earlier but now there is no file under /opt/sas/config/Lev1/ObjectSpawner/Logs.

Never do that unless the corresponding process has been stopped (and you're positively sure).

I guess that the spawner is still happily writing to the file that still exists as an inode and physical data, but has no directory reference any longer.

Re: SAS EG Connection Issue

japsas100 — Wed, 08 Mar 2017 12:55:06 GMT

Still am not able to connect to metadata. Any suggestion???

Re: SAS EG Connection Issue

Kurt_Bremser — Wed, 08 Mar 2017 13:01:39 GMT

@japsas100 wrote:

Still am not able to connect to metadata. Any suggestion???

Show the relevant part of the metadata server log (do a tail on it immediately after your connection attempt fails).

Re: SAS EG Connection Issue

japsas100 — Wed, 08 Mar 2017 13:37:57 GMT

Please below metadata log

2017-03-08T15:31:30,430 INFO [00092307] :sastrust@saspw - New client connection (9885) accepted from server port 8561 for user sastrust@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:xxx.xxx.xx.xxx]:35933 for APPNAME=Content Server 9.4.
2017-03-08T15:31:30,430 INFO [00092307] :sastrust@saspw - Request made to cluster SASMeta - Logical Metadata Server (A57LP4MN.AX000001).
2017-03-08T15:31:30,430 INFO [00092307] :sastrust@saspw - Redirect client in cluster SASMeta - Logical Metadata Server (A57LP4MN.AX000001) to server SASMeta - Metadata Server (A57LP4MN.AZ000001) at sastest01.s.xxxx.xx:8561.
2017-03-08T15:31:30,453 INFO [00092321] 9885:sas - Client connection 9885 for user sastrust@saspw closed.

Re: SAS EG Connection Issue

Kurt_Bremser — Wed, 08 Mar 2017 13:45:04 GMT

That means that EG never gets a network connection to the metadata server. Do you have some kind of personal firewall installed on your desktop?

Re: SAS EG Connection Issue

japsas100 — Wed, 08 Mar 2017 13:48:10 GMT

No firewall blocking at client and server level.

With same client I am able to connect prod server.

In Prod we have two IP address one start with 193.XXXXX and with10.XXXXX but in test we have only one IP address and athat start with 10.

Re: SAS EG Connection Issue

Kurt_Bremser — Wed, 08 Mar 2017 13:55:48 GMT

A 193. IP address is a public IP address that can be reached across the internet.

A 10. address is a private network that can't be routed through the internet. If you're not in the same logical network, the 10. is unreachable.

Re: SAS EG Connection Issue

japsas100 — Wed, 08 Mar 2017 13:59:44 GMT

Thanks for quick reply.

Can we have a private ip at the server level to connect the sas client such as SAS EG?

or any other issue?

Re: SAS EG Connection Issue

Kurt_Bremser — Wed, 08 Mar 2017 14:17:25 GMT

@japsas100 wrote:

Thanks for quick reply.

Can we have a private ip at the server level to connect the sas client such as SAS EG?

or any other issue?

It depends on your connection. If you have to make a jump through the internet, the 10. address won't work. If the address you use in prod is the 193. address, then you need a similar one for the test environment.

Ping the metadata server for the prod environment by name and see what the ping returns as target IP address.

Re: SAS EG Connection Issue

japsas100 — Wed, 08 Mar 2017 14:24:19 GMT

Prod hostname return ip like 193.XXXXXXXX which we alredy have in test env.

I alredy raised the track with SAS Tech support but not find any solution for the same.

Re: SAS EG Connection Issue

Kurt_Bremser — Wed, 08 Mar 2017 14:37:29 GMT

@japsas100 wrote:

Prod hostname return ip like 193.XXXXXXXX which we alredy have in test env.

I alredy raised the track with SAS Tech support but not find any solution for the same.

From your earlier post:

"In Prod we have two IP address one start with 193.XXXXX and with10.XXXXX but in test we have only one IP address and athat start with 10."

From that I took that

- your prod server is reachable via two alternate IP addresses, a 193. and a 10.

- your test server only has a 10. address

And I also assume that you have no problem connecting EG to the prod environment, but can't reach your test environment from the same EG.

Which IP address is returned if you try to ping your test metadata server by name?

Re: SAS EG Connection Issue

japsas100 — Wed, 08 Mar 2017 14:41:58 GMT

test IP also return : 193.XXXXXXXXXXX same as prod.

In test we dont have ip start with 10.XXXXXX

Re: SAS EG Connection Issue

Kurt_Bremser — Wed, 08 Mar 2017 15:08:07 GMT

Then we have to wait what SAS TS comes up with. They have more options, as you can supply them confidential data that can't be posted here.