<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SAS Viya 3.5 license file renewal in RHEL in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-license-file-renewal-in-RHEL/m-p/801934#M23958</link>
    <description>The steps to update the license are here: &lt;A href="https://go.documentation.sas.com/doc/en/calcdc/3.5/callicense/n03000saslicensing00000admin.htm#n03004saslicensing00000admin" target="_blank"&gt;https://go.documentation.sas.com/doc/en/calcdc/3.5/callicense/n03000saslicensing00000admin.htm#n03004saslicensing00000admin&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;After saving the new license files in sas_viya_playbook/ and updating vars.yaml to reference those new files, you should be able to just run the apply_license.yaml playbook. So I don't know that you needed to perform your steps 5 and 6...&lt;BR /&gt;The error you're getting in ansible is saying it's trying to use scp to copy the license file for you and this is failing. Does running "ansible -m ping all -i inventory.ini" show you are able to successfully communicate with all the hosts in your inventory.ini file?</description>
    <pubDate>Mon, 14 Mar 2022 13:52:55 GMT</pubDate>
    <dc:creator>gwootton</dc:creator>
    <dc:date>2022-03-14T13:52:55Z</dc:date>
    <item>
      <title>SAS Viya 3.5 license file renewal in RHEL</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-license-file-renewal-in-RHEL/m-p/801796#M23948</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;I have SAS Viya 3.5 installed in multi-tenant environment (1.micro services, 2.cas server) in RHEL 7.9 and license got expired. Received new license renewal and followed the steps to renew the license.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Taken backup for current license files into a backup location.&lt;/LI&gt;&lt;LI&gt;copy new license files (a .txt file and a .jwt file) in "/opt/sas/sas_viya_playbook/" location.&lt;/LI&gt;&lt;LI&gt;Taken backup for vars.yml file&lt;/LI&gt;&lt;LI&gt;Modified Ansible playbook to point to the new license files in sas_viya_playbook/vars.yml, locate LICENSE_FILENAME and LICENSE_COMPOSITE_FILENAME, and replace the current license filename with the corresponding new license filename.&lt;/LI&gt;&lt;LI&gt;Make sure that license files (a .txt file and a .jwt file) reside on your CAS controller machine in the following directory:&amp;nbsp;&lt;SPAN&gt;/opt/sas/viya/config/etc/cas/default/&lt;/SPAN&gt;.&lt;/LI&gt;&lt;LI&gt;Update the symbolic link for sas_license.txt to point to the new CAS license file. (This should be the .jwt file.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; cd /opt/sas/viya/config/etc/cas/default&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ln -sf&amp;nbsp; SASViyaV0300_xxxxxxx_xxxxxx_Linux_x86-64.jwt sas_license.txt&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; 7.&amp;nbsp; Run the following command under the path using sas user &amp;nbsp;/opt/sas/sas_viya_playbook/&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;ansible-playbook -i&amp;nbsp; inventory.ini apply-license.yml&lt;/P&gt;&lt;P&gt;Did i missed any steps before running apply-license command.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After running this command I am getting the following errors.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TASK [create-snapshot : Copy system information to the snapshot directory] ************************************************************************************&lt;BR /&gt;[WARNING]: sftp transfer mechanism failed on [casserver.com]. Use ANSIBLE_DEBUG=1 to see detailed information&lt;BR /&gt;[WARNING]: scp transfer mechanism failed on [casserver.com]. Use ANSIBLE_DEBUG=1 to see detailed information&lt;BR /&gt;fatal: [casserver]: FAILED! =&amp;gt; {"changed": false, "checksum": "c515bc4bb8bdf51b6c947b5f22f4ca9061d81745", "dest": "/opt/sas/sas_viya_playbook/snapshot/16467177 77/casserver.out", "file": "/tmp/casserver.out", "md5sum": "784418cee27fa1f0bb1a0eb5fe12cbdd", "msg": "checksum mismatch", "remote_checksum": "2785712f1b0877e6 dcba1dc475f4505d91cb565c", "remote_md5sum": null}&lt;BR /&gt;changed: [microservices]&lt;/P&gt;&lt;P&gt;NO MORE HOSTS LEFT ********************************************************************************************************************************************&lt;/P&gt;&lt;P&gt;PLAY RECAP ****************************************************************************************************************************************************&lt;BR /&gt;casserver : ok=15 changed=2 unreachable=0 failed=1 skipped=5 rescued=0 ignored=0&lt;BR /&gt;microservices : ok=24 changed=6 unreachable=0 failed=0 skipped=7 rescued=0 ignored=0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 12 Mar 2022 09:38:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-license-file-renewal-in-RHEL/m-p/801796#M23948</guid>
      <dc:creator>MYAKKALA</dc:creator>
      <dc:date>2022-03-12T09:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Viya 3.5 license file renewal in RHEL</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-license-file-renewal-in-RHEL/m-p/801934#M23958</link>
      <description>The steps to update the license are here: &lt;A href="https://go.documentation.sas.com/doc/en/calcdc/3.5/callicense/n03000saslicensing00000admin.htm#n03004saslicensing00000admin" target="_blank"&gt;https://go.documentation.sas.com/doc/en/calcdc/3.5/callicense/n03000saslicensing00000admin.htm#n03004saslicensing00000admin&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;After saving the new license files in sas_viya_playbook/ and updating vars.yaml to reference those new files, you should be able to just run the apply_license.yaml playbook. So I don't know that you needed to perform your steps 5 and 6...&lt;BR /&gt;The error you're getting in ansible is saying it's trying to use scp to copy the license file for you and this is failing. Does running "ansible -m ping all -i inventory.ini" show you are able to successfully communicate with all the hosts in your inventory.ini file?</description>
      <pubDate>Mon, 14 Mar 2022 13:52:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-license-file-renewal-in-RHEL/m-p/801934#M23958</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2022-03-14T13:52:55Z</dc:date>
    </item>
  </channel>
</rss>

