BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
sathya66
Barite | Level 11

Hi,

I launched new environment with our base  image. I think,it is not updated new host names properly. I am getting below error when I try to update SID file metadata server. which file holds this info  on metadata server.

 

Configuration Directory Configuration Level
(*) 1 - /opt/sas/config Lev1

The * character indicates the current selection.
You can change the selection by specifying a number below.
Enter <b> to go back to the previous prompt, <h> for help, or <q> to quit.
Note that these commands include the letter and the angle brackets.
Press Enter to accept the current selection and continue.
Selection:

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

Specify Connection Information
Specify connection information to the SAS Metadata Server.

Host Name: sasmeta.test.com

Port: 8561

Enter <b> to go back to the previous prompt, <h> for help, or <q> to quit.
Note that these commands include the letter and the angle brackets.
Press Enter to accept the default or supply alternate text and press Enter.
Default: sasadm@saspw
User ID:

Enter <b> to go back to the previous prompt, <h> for help, or <q> to quit.
Note that these commands include the letter and the angle brackets.
Password:

Error: A SAS Metadata Server is not currently running on the Port.

 

1 ACCEPTED SOLUTION

Accepted Solutions
JuanS_OCS
Amethyst | Level 16

Hello @sathya66,

 

forgetting about the hostname update in the SAS metadata, your host is the first one that has to resolve the new alias, and telnet has to be able to telnet {newalias} 8561. Can the server resolve the new alias to the right IP? Can the server telnet with the new alias on the port number?

 

Once you do this, you should be able to execute the command properly.

 

I would carefully review anyways the documented steps for updating hostnames: https://documentation.sas.com/?docsetId=bisag&docsetTarget=n0zdcqxsmd21wtn17vt0w2prek90.htm&docsetVe...

https://documentation.sas.com/?docsetId=bisag&docsetTarget=n1ov3paky6afj8n1bj7l55o8jvw5.htm&docsetVe...

 

Check the troubleshooting guide: https://documentation.sas.com/?docsetId=bisag&docsetTarget=p0vjf8irdhbbndn1ck1ur7j0djlh.htm&docsetVe...

 

To avoid hostname issues while running SAS Deployment manager you can run

 

sasdm.sh -confighostname [your_fqdn_hostname_or_alias]

 

This might get the license place in place, but you still might need to resolve the hostname/alias issue with infra.

 

View solution in original post

5 REPLIES 5
Denise
Obsidian | Level 7

Is your metadata tier running?

/opt/sas/config/Lev(n)/sas.servers status

 

It should be running for this task.

 

sathya66
Barite | Level 11

yes, it is running with different host name(testmeta.test.com). "sasmeta.test.com" is our base metadata hostname. it is updated with "testmeta.test.com"  but it is still showing the base metadata host name when I try to do this task. Some file is not updated with new hostname thats why I am getting below error

Error: A SAS Metadata Server is not currently running on the Port.

Denise
Obsidian | Level 7

How did you update from "sasmeta.test.com" to "testmeta.test.com"?  Did you use SAS Depolyment Manager for "update Host Name References"?  If so, do you have a multiple tier update where you need to run that on each tier?

 

 

sathya66
Barite | Level 11
Yes, by using Deployment manager.
It is sorted now. sasmeta data server host name reference is wrong
Thanks for taking time on this.
JuanS_OCS
Amethyst | Level 16

Hello @sathya66,

 

forgetting about the hostname update in the SAS metadata, your host is the first one that has to resolve the new alias, and telnet has to be able to telnet {newalias} 8561. Can the server resolve the new alias to the right IP? Can the server telnet with the new alias on the port number?

 

Once you do this, you should be able to execute the command properly.

 

I would carefully review anyways the documented steps for updating hostnames: https://documentation.sas.com/?docsetId=bisag&docsetTarget=n0zdcqxsmd21wtn17vt0w2prek90.htm&docsetVe...

https://documentation.sas.com/?docsetId=bisag&docsetTarget=n1ov3paky6afj8n1bj7l55o8jvw5.htm&docsetVe...

 

Check the troubleshooting guide: https://documentation.sas.com/?docsetId=bisag&docsetTarget=p0vjf8irdhbbndn1ck1ur7j0djlh.htm&docsetVe...

 

To avoid hostname issues while running SAS Deployment manager you can run

 

sasdm.sh -confighostname [your_fqdn_hostname_or_alias]

 

This might get the license place in place, but you still might need to resolve the hostname/alias issue with infra.

 

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
  • 5 replies
  • 1335 views
  • 4 likes
  • 3 in conversation