BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
sasdol
Obsidian | Level 7

Hi,

 

I have installed SAS Viya 3.5 on Red Hat 8 single server (ansible on the same host), using default site.yml, inventory.ini and mirror repo / deployment package specific for our order. Installation completed with only 1 error for rabbitmq (though the sas-viya-rabbitmq-server-default service is active(running) after deployment). I tried to follow "Add Data Source Information" from Linux Deployment Guide (SAS Help Center: Modify the vars.yml File) for single server installation (ansible on the same server); however, I am not clear about specific configuration for data source information in vars.yml for our environment (totally new SAS installation).

 

Do I need to create a database before running the ansible playbook to deploy and specify ODBC connection to that in vars.yml  OR the ansible playbook will create a PostgreSQL database as default? Do I need to make any change in inventory, site or vars file for the ansible playbook to create default database on the same server?

 

Tried to follow post-deployment tasks for SAS Help Center: Configure ODBC and SAS Help Center: Configure SAS/ACCESS Interface to PostgreSQL; however, it didn't help in getting clear picture about whether I need to create a database or ansible playbook will create it.

 

Accessing SASDrive or SASStudio, as per validating deployment (SAS Help Center: Validating the Deployment), returns 404 (http or https); so, overall not clear what is the next step for me. Any direction will be much appreciated. 

 

No webpage was found for the web address: http://<hostname>:8500/SASDrive

HTTP ERROR 404

No webpage was found for the web address:  https://<hostname>:8501/SASStudio

HTTP ERROR 404

 

We have data / ACCESS related components in the order, if that helps in guiding what configuration should be changed in vars.yml:

ORACLEBNDL SAS/ACCESS to ORACLE

ODBC SAS/ACCESS to ODBC

PCFILE SAS/ACCESS to PC Files

WKSPSRVLOCAL SAS Workspace Server for Local Access

WKSPSRVENT SAS Workspace Server for Enterprise Access

CDFBASE Data Connector SAS Data Sets

CDFODBC SAS Data Connect to ODBC

CDFORCL Data Connector to Oracle;
CDFPCFL SAS Data Connect to PC Files;
TKCDFTS Common TK Extensions for CAS Data Feeders;
TKORACLE SAS TK Ext for Oracle;
TKODBC SAS TK Ext for ODBC;
CDFWEB WEB Media Data Feeder;
CDFSPDE Data Connector to SPDE;

CRSLOADSTRMS Action Set for Streaming Data

 

=========   error while deploying

        "Tue Apr 26 19:01:58 EDT 2022 setup_rabbit_cluster Starting sas-viya-rabbitmq-server-default",

        "Tue Apr 26 19:03:04 EDT 2022 setup_rabbit_cluster The RabbitMQ service sas-viya-rabbitmq-server-default could not be started.",

        "Tue Apr 26 19:03:04 EDT 2022 setup_rabbit_cluster Returned status was 1",

        "Tue Apr 26 19:03:04 EDT 2022 setup_rabbit_cluster Setup failed. Beware of independent Rabbit hosts running with different shared secrets."

    ]

}

 

NO MORE HOSTS LEFT ************************************************************************************************************************************************************

 

PLAY RECAP ********************************************************************************************************************************************************************

deployTarget               : ok=369  changed=136  unreachable=0    failed=1    skipped=853  rescued=0    ignored=0

localhost                  : ok=12   changed=2    unreachable=0    failed=0    skipped=6    rescued=0    ignored=0

 

================== rabbitmq service status

sas_viya_playbook]# systemctl status sas-viya-rabbitmq-server-default
● sas-viya-rabbitmq-server-default.service - LSB: start and stop sas-rabbitmq-server server
Loaded: loaded (/etc/rc.d/init.d/sas-viya-rabbitmq-server-default; generated)
Active: active (running) since Sun 2022-05-01 22:46:13 EDT; 1 day 19h ago
Docs: man:systemd-sysv-generator(8)
Process: 91371 ExecStop=/etc/rc.d/init.d/sas-viya-rabbitmq-server-default stop (code=exited, status=0/SUCCESS)
Process: 94438 ExecStart=/etc/rc.d/init.d/sas-viya-rabbitmq-server-default start (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 410046)
Memory: 1.6M
CGroup: /system.slice/sas-viya-rabbitmq-server-default.service
└─16408 /bin/bash /opt/sas/viya/home/sbin/rabbitmq-server

May 01 22:44:40 hostname su[94928]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0)
May 01 22:45:22 hostname sas-viya-rabbitmq-server-default[94438]: sas-viya-rabbitmq-server-default service is registered
May 01 22:45:36 hostname su[98503]: (to sasrabbitmq) root on none
May 01 22:45:36 hostname su[98503]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0)
May 01 22:45:37 hostname su[98575]: (to sasrabbitmq) root on none
May 01 22:45:37 hostname su[98575]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0)
May 01 22:45:59 hostname su[99775]: (to sasrabbitmq) root on none
May 01 22:45:59 hostname su[99775]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0)
May 01 22:46:13 hostname sas-viya-rabbitmq-server-default[94438]: sas-viya-rabbitmq-server-default service is started
May 01 22:46:13 hostname systemd[1]: Started LSB: start and stop sas-rabbitmq-server server.
[sas_viya_playbook]#

 

 

======= alldata related services are down

sas-viya-dataplans-default down N/A N/A N/A
sas-viya-report-data-default down N/A N/A N/A
sas-viya-web-data-access-default down N/A N/A N/A
sas-viya-dataexplorer-default down N/A N/A N/A
sas-viya-dataprofiles-default down N/A N/A N/A
sas-viya-datastudio-default down N/A N/A N/A
sas-viya-dmdataservices-default down N/A N/A N/A

 

================ ports open

[sas_viya_playbook]# netstat -ntpl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 10.50.12.103:50846 0.0.0.0:* LISTEN 28358/java
tcp 0 0 10.50.12.103:10334 0.0.0.0:* LISTEN 28357/java
tcp 0 0 0.0.0.0:40799 0.0.0.0:* LISTEN 28357/java
tcp 0 0 0.0.0.0:43139 0.0.0.0:* LISTEN 15722/objspawn
tcp 0 0 0.0.0.0:5671 0.0.0.0:* LISTEN 17075/beam.smp
tcp 0 0 127.0.0.1:199 0.0.0.0:* LISTEN 1933/snmpd
tcp 0 0 10.50.12.103:47816 0.0.0.0:* LISTEN 28358/java
tcp 0 0 0.0.0.0:25672 0.0.0.0:* LISTEN 17075/beam.smp
tcp 0 0 0.0.0.0:8200 0.0.0.0:* LISTEN 10921/vault
tcp 0 0 0.0.0.0:8201 0.0.0.0:* LISTEN 10921/vault
tcp 0 0 0.0.0.0:14443 0.0.0.0:* LISTEN 28358/java
tcp 0 0 0.0.0.0:8300 0.0.0.0:* LISTEN 8542/consul
tcp 0 0 0.0.0.0:8301 0.0.0.0:* LISTEN 8542/consul
tcp 0 0 10.50.12.103:56431 0.0.0.0:* LISTEN 28357/java
tcp 0 0 0.0.0.0:8591 0.0.0.0:* LISTEN 15722/objspawn
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 14117/httpd
tcp 0 0 127.0.0.1:43473 0.0.0.0:* LISTEN 15722/objspawn
tcp 0 0 0.0.0.0:4369 0.0.0.0:* LISTEN 15110/epmd
tcp 0 0 10.50.12.103:59570 0.0.0.0:* LISTEN 28357/java
tcp 0 0 0.0.0.0:37459 0.0.0.0:* LISTEN 28358/java
tcp 0 0 0.0.0.0:8500 0.0.0.0:* LISTEN 8542/consul
tcp 0 0 0.0.0.0:8501 0.0.0.0:* LISTEN 8542/consul
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1922/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1939/cupsd
tcp 0 0 0.0.0.0:15672 0.0.0.0:* LISTEN 17075/beam.smp
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 4872/master
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 14117/httpd
[sas_viya_playbook]#

 

 
Thanks in advance.
1 ACCEPTED SOLUTION

Accepted Solutions
gwootton
SAS Super FREQ
The SAS/ACCESS interfaces use database clients to work, which must be installed on those hosts where it is to be used (foundation, CAS). The modifications of vars.yml are to provide the information on where those clients are installed to SAS. In the case of Oracle for example you are setting ORACLE_HOME to where the oracle client is installed and adding the oracle client's binary path to the PATH variable and library path to LD_LIBRARY_PATH. With ODBC you are setting the location of the odbc.ini file and odbcinst.ini file, as well as again updating LD_LIBRARY_PATH with the path for the ODBC drivers libraries. The contents of the ODBC ini file are dependent on the connection information for the database server you would like to connect via ODBC. Your database administrator may be able to help you to set up clients on your server.

http://www.unixodbc.org/odbcinst.html
--
Greg Wootton | Principal Systems Technical Support Engineer

View solution in original post

5 REPLIES 5
sasdol
Obsidian | Level 7

Trying to simplify and shorten the question:

 

We have following SAS/ACCESS products in our order:

 

*PRODNUM194 = ORACLEBNDL SAS/ACCESS to ORACLE;

*PRODNUM208 = PCFILE SAS/ACCESS to PC Files;
*PRODNUM209 = ODBC SAS/ACCESS to ODBC;

 

It is not clear to me whether I need to create any database and provide ODBC ini file for that database in vars.yml to be used during the deployment or the ansible playbook will create required database(s) in PostgreSQL.  

 

Pre-installation tasks (SAS Help Center: Pre-installation Tasks) does not have any requirements/config for databases; whereas Installation --> "Modify the vars.yml file" (https://documentation.sas.com/doc/en/calcdc/3.5/dplyml0phy0lax/n1knvzbsifo9xqn1al0bh7wxrrkg.htm ) is referring to odbc.ini file. So, if any one can help showing should be the content of this ODBC ini file, it will be much appreciated.

Thanks.

 

SASKiwi
PROC Star

These types of installation issues are best progressed via SAS Tech Support tracks if you haven't done so already. I see you have three posts already and Tech Support is able to respond and diagnose more quickly than Community posters.

sasdol
Obsidian | Level 7

Thank you for replying. Sure, will work with tech support.

gwootton
SAS Super FREQ
The SAS/ACCESS interfaces use database clients to work, which must be installed on those hosts where it is to be used (foundation, CAS). The modifications of vars.yml are to provide the information on where those clients are installed to SAS. In the case of Oracle for example you are setting ORACLE_HOME to where the oracle client is installed and adding the oracle client's binary path to the PATH variable and library path to LD_LIBRARY_PATH. With ODBC you are setting the location of the odbc.ini file and odbcinst.ini file, as well as again updating LD_LIBRARY_PATH with the path for the ODBC drivers libraries. The contents of the ODBC ini file are dependent on the connection information for the database server you would like to connect via ODBC. Your database administrator may be able to help you to set up clients on your server.

http://www.unixodbc.org/odbcinst.html
--
Greg Wootton | Principal Systems Technical Support Engineer
sasdol
Obsidian | Level 7

Thank you @gwootton . Seems that these requirements are for the data which we want to analyzed through SAS - not for the database required for SAS config itself (like bundled PostgreSQL). I was confused with that and can keep this config for later part as current requirement is satisfied by importing CSV files. However, need to resolve the postgre related error as replied in other post. Any hint on that will be much appreciated. Thanks.

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
  • 1106 views
  • 1 like
  • 3 in conversation