https://github.com/sassoftware/sas-container-recipes
I deployed sas viya according to the above website address. Last week when I constructed single and multiple images, it was still ok, but not this week. The error is as follows:
[container.go:403] &{fatal: [127.0.0.1]: FAILED! => {"changed": true, "cmd": ["yum", "install", "--assumeyes", "sas-cleanutils", "httpd", "mod_ssl"], "delta": "0:00:48.914718", "end": "2019-11-21 01:38:45.593214", "msg": "non-zero return code", "rc": 1, "start": "2019-11-21 01:37:56.678496", "stderr": "https://ses.sas.download/ses/repos/shipped/va/105/va-105-x64_redhat_linux_6-yum/Packages/s/sas-clean...: [Errno 14] HTTPS Error 410 - Gone\nTrying other mirror.\n\n\nError downloading packages:\n sas-cleanutils-1.1.17-20190410.1554912065418.x86_64: [Errno 256] No more mirrors to try.", "stderr_lines": ["https://ses.sas.download/ses/repos/shipped/va/105/va-105-x64_redhat_linux_6-yum/Packages/s/sas-clean...: [Errno 14] HTTPS Error 410 - Gone", "Trying other mirror.", "", "", "Error downloading packages:", " sas-cleanutils-1.1.17-20190410.1554912065418.x86_64: [Errno 256] No more mirrors to try."], "stdout": "Loaded plugins: fastestmirror, ovl\nLoading mirror speeds from cached hostfile\n * base: mirrors.aliyun.com\n * extras: mirrors.aliyun.com\n * updates: mirrors.cn99.com\nResolving Dependencies\n--> Running transaction check\n---> Package httpd.x86_64 0:2.4.6-90.el7.centos will be installed\n--> Processing Dependency: httpd-tools = 2.4.6-90.el7.centos for package: httpd-2.4.6-90.el7.centos.x86_64\n--> Processing Dependency: system-logos >= 7.92.1-1 for package: httpd-2.4.6-90.el7.centos.x86_64\n--> Processing Dependency: /etc/mime.types for package: httpd-2.4.6-90.el7.centos.x86_64\n--> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.4.6-90.el7.centos.x86_64\n--> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.4.6-90.el7.centos.x86_64\n---> Package mod_ssl.x86_64 1:2.4.6-90.el7.centos will be installed\n---> Package sas-cleanutils.x86_64 0:1.1.17-20190410.1554912065418 will be installed\n--> Running transaction check\n---> Package apr.x86_64 0:1.4.8-5.el7 will be installed\n---> Package apr-util.x86_64 0:1.5.2-6.el7 will be installed\n---> Package centos-logos.noarch 0:70.0.6-3.el7.centos will be installed\n---> Package httpd-tools.x86_64 0:2.4.6-90.el7.centos will be installed\n---> Package mailcap.noarch 0:2.1.41-2.el7 will be installed\n--> Finished Dependency Resolution\n\nDependencies Resolved\n\n================================================================================\n Package Arch Version Repository Size\n================================================================================\nInstalling:\n httpd x86_64 2.4.6-90.el7.centos base 2.7 M\n mod_ssl x86_64 1:2.4.6-90.el7.centos base 112 k\n sas-cleanutils x86_64 1.1.17-20190410.1554912065418 sas-va-105-x64_redhat_linux_6-yum\n 12 k\nInstalling for dependencies:\n apr x86_64 1.4.8-5.el7 base 103 k\n apr-util x86_64 1.5.2-6.el7 base 92 k\n centos-logos noarch 70.0.6-3.el7.centos base 21 M\n httpd-tools x86_64 2.4.6-90.el7.centos base 91 k\n mailcap noarch 2.1.41-2.el7 base 31 k\n\nTransaction Summary\n================================================================================\nInstall 3 Packages (+5 Dependent packages)\n\nTotal download size: 24 M\nInstalled size: 32 M\nDownloading packages:", "stdout_lines": ["Loaded plugins: fastestmirror, ovl", "Loading mirror speeds from cached hostfile", " * base: mirrors.aliyun.com", " * extras: mirrors.aliyun.com", " * updates: mirrors.cn99.com", "Resolving Dependencies", "--> Running transaction check", "---> Package httpd.x86_64 0:2.4.6-90.el7.centos will be installed", "--> Processing Dependency: httpd-tools = 2.4.6-90.el7.centos for package: httpd-2.4.6-90.el7.centos.x86_64", "--> Processing Dependency: system-logos >= 7.92.1-1 for package: httpd-2.4.6-90.el7.centos.x86_64", "--> Processing Dependency: /etc/mime.types for package: httpd-2.4.6-90.el7.centos.x86_64", "--> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.4.6-90.el7.centos.x86_64", "--> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.4.6-90.el7.centos.x86_64", "---> Package mod_ssl.x86_64 1:2.4.6-90.el7.centos will be installed", "---> Package sas-cleanutils.x86_64 0:1.1.17-20190410.1554912065418 will be installed", "--> Running transaction check", "---> Package apr.x86_64 0:1.4.8-5.el7 will be installed", "---> Package apr-util.x86_64 0:1.5.2-6.el7 will be installed", "---> Package centos-logos.noarch 0:70.0.6-3.el7.centos will be installed", "---> Package httpd-tools.x86_64 0:2.4.6-90.el7.centos will be installed", "---> Package mailcap.noarch 0:2.1.41-2.el7 will be installed", "--> Finished Dependency Resolution", "", "Dependencies Resolved", "", "================================================================================", " Package Arch Version Repository Size", "================================================================================", "Installing:", " httpd x86_64 2.4.6-90.el7.centos base 2.7 M", " mod_ssl x86_64 1:2.4.6-90.el7.centos base 112 k", " sas-cleanutils x86_64 1.1.17-20190410.1554912065418 sas-va-105-x64_redhat_linux_6-yum", " 12 k", "Installing for dependencies:", " apr x86_64 1.4.8-5.el7 base 103 k", " apr-util x86_64 1.5.2-6.el7 base 92 k", " centos-logos noarch 70.0.6-3.el7.centos base 21 M", " httpd-tools x86_64 2.4.6-90.el7.centos base 91 k", " mailcap noarch 2.1.41-2.el7 base 31 k", "", "Transaction Summary", "================================================================================", "Install 3 Packages (+5 Dependent packages)", "", "Total download size: 24 M", "Installed size: 32 M", "Downloading packages:"]} <nil>}
[container.go:403] &{to retry, use: --limit @/ansible/playbook.retry
70239046
That is your Technical Support Site number, but using that I managed to find your order number created July 2019. You have exceeded the number of downloads. I've added a few more, you should be able to download the packages again after an hour. Also, I encourage you to use a local mirror to avoid these issues with download limits:
thank you very much
Hello
I deploy with containers, and I deploy according to the documentation on github
I want to add multi-user login way, I want to know how to add users.Here's how I deployed it
shell
./build.sh --type multiple --zip /sas/SAS_Viya_deployment_data.zip --docker-registry-namespace datamind-sas --mirror-url "http://172.31.27.151:9999" --docker-registry-url registry-vpc.cn-hongkong.aliyuncs.com --addons "auth-sssd"
here is my sssd.conf
[sssd] config_file_version = 2 services = nss,pam sbus_timeout = 30 domains = default [domain/default] autofs_provider = ldap cache_credentials = True ldap_search_base = dc=mypaas,dc=com id_provider = ldap auth_provider = ldap chpass_provider = ldap ldap_uri = ldap://172.16.0.47:389 #ldap_tls_cacertdir = /etc/openldap/cacerts ldap_id_use_start_tls = False [sssd] services = nss, pam, autofs config_file_version = 2 domains = default [nss] homedir_substring = /home filter_users = root
Should I choose ldap to add users or use another plug-in?If I use ldap, what attributes should my ldap user have to make it work?
thanks!
here is ldap log
11月 26 17:48:49 localhost.localdomain sshd[62521]: pam_unix(sshd:session): session opened for user root by (uid=0) 11月 26 17:49:35 localhost.localdomain slapd[236075]: conn=1456 fd=25 ACCEPT from IP=172.16.0.46:41830 (IP=0.0.0.0:389) 11月 26 17:49:35 localhost.localdomain slapd[236075]: conn=1456 op=0 EXT oid=1.3.6.1.4.1.1466.20037 11月 26 17:49:35 localhost.localdomain slapd[236075]: conn=1456 op=0 STARTTLS 11月 26 17:49:35 localhost.localdomain slapd[236075]: conn=1456 op=0 RESULT oid= err=0 text= 11月 26 17:49:35 localhost.localdomain slapd[236075]: conn=1456 fd=25 closed (TLS negotiation failure) 11月 26 17:49:37 localhost.localdomain slapd[236075]: conn=1457 fd=25 ACCEPT from IP=172.16.0.46:41930 (IP=0.0.0.0:389) 11月 26 17:49:37 localhost.localdomain slapd[236075]: conn=1457 op=0 EXT oid=1.3.6.1.4.1.1466.20037 11月 26 17:49:37 localhost.localdomain slapd[236075]: conn=1457 op=0 STARTTLS 11月 26 17:49:37 localhost.localdomain slapd[236075]: conn=1457 op=0 RESULT oid= err=0 text= 11月 26 17:49:37 localhost.localdomain slapd[236075]: conn=1457 fd=25 closed (TLS negotiation failure) 11月 26 17:49:41 localhost.localdomain slapd[236075]: conn=1458 fd=25 ACCEPT from IP=172.16.0.46:42082 (IP=0.0.0.0:389) 11月 26 17:49:41 localhost.localdomain slapd[236075]: conn=1458 op=0 EXT oid=1.3.6.1.4.1.1466.20037 11月 26 17:49:41 localhost.localdomain slapd[236075]: conn=1458 op=0 STARTTLS 11月 26 17:49:41 localhost.localdomain slapd[236075]: conn=1458 op=0 RESULT oid= err=0 text= 11月 26 17:49:41 localhost.localdomain slapd[236075]: conn=1458 fd=25 closed (TLS negotiation failure)
If you are experiencing problems connecting SAS Viya to your slapd using TLS, then please make sure you have followed the instructions from this document: Configure the LDAPS (Secure LDAP) Connection.
Can I test login without using the TLS certificate
Yes, you can.
set ldap_id_use_start_tls = False ,is true?
ldap_id_use_start_tls = False
If you are talking about SSSD configuration, then yes.
Hi, may I ask when will the full deployment of container-type support production? It is written on github that it is experimental, and there are various precautions
hello,i deployment sas viya with container, here is my build command
./build.sh --type full --zip /sas/SAS_Viya_deployment_data.zip --docker-registry-namespace datamind-sas --mirror-url "http://172.31.27.151:9999" --docker-registry-url registry-vpc.cn-hongkong.aliyuncs.com --addons "auth-sssd access-postgres access-odbc ide-jupyter-python3" &
my pod is all run,bu i can't login,why
[root@test deployments]# kubectl -n=sas-viya-full get pod
NAME READY STATUS RESTARTS AGE
sas-viya-adminservices-57b494f9b8-9g79q 1/1 Running 0 38m
sas-viya-cas-0 1/1 Running 0 16m
sas-viya-casservices-79458cc56d-kpdvk 1/1 Running 0 38m
sas-viya-cognitivecomputingservices-558b96549b-g7hdp 1/1 Running 0 38m
sas-viya-computeserver-0 1/1 Running 0 38m
sas-viya-computeservices-64446ccf7b-hcr88 1/1 Running 0 38m
sas-viya-configuratn-84b9d6895d-7jzx6 1/1 Running 0 38m
sas-viya-consul-0 1/1 Running 0 38m
sas-viya-coreservices-66bd58b768-bgd5c 1/1 Running 0 38m
sas-viya-dataservices-848fdb87fb-g42px 1/1 Running 0 38m
sas-viya-graphbuilderservices-6947f448-shrck 1/1 Running 0 38m
sas-viya-homeservices-5cf944ff44-hxfkj 1/1 Running 0 17m
sas-viya-httpproxy-0 1/1 Running 0 38m
sas-viya-modelservices-6497f4fc4d-n8rxg 1/1 Running 0 38m
sas-viya-operations-844db88585-lqt6r 1/1 Running 0 38m
sas-viya-pgpoolc-0 1/1 Running 0 38m
sas-viya-programming-0 1/1 Running 0 38m
sas-viya-rabbitmq-0 1/1 Running 0 38m
sas-viya-reportservices-c8c5bf9b4-87rmm 1/1 Running 0 30m
sas-viya-reportviewerservices-55d49dd64d-l9j7h 1/1 Running 0 38m
sas-viya-sasdatasvrc-0 1/1 Running 0 33m
sas-viya-scoringservices-695785cd44-f2hpq 1/1 Running 0 34m
sas-viya-studioviya-79798f6cdd-8zhrv 1/1 Running 0 38m
sas-viya-themeservices-746c5dcd44-6h5rz 1/1 Running 0 38m
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
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.