About Iyappan21

Iyappan21 · ‎04-28-2020

@jeromesauve Thanks for the suggestion. Its worth information. In my case, I have modified ansible log directory at ansible.cfg and deployment was successful. Thanks, Iyappan M S

Iyappan21 · ‎04-28-2020

Hi All, Another solution for this issue. Set create a directory at /tmp (For Ex. /tmp/ansiblelog and mention it as log directory in Ansible.cfg with proper permission to the installing user id. Thanks

Iyappan21 · ‎04-28-2020

@jeromesauve I am doing the same and the issue is still there. We are installing with normal user with sudo password still we face the issue. Can you please explain the solution If we miss any. Kindly Guide. Thanks, Iyappan M S

Iyappan21 · ‎04-28-2020

@alexal This issue is resolved with extending var/cache folder disk. Thanks for the response

Iyappan21 · ‎04-28-2020

@alexal We kept Keepcache =0 and deploying with local repository, still it downloads the repository in /var/cache/yum. Is it an expected behaviour? Or anything else to be done to avoid the additional download. Thanks for the reponse. Thanks, Iyappan M S

Iyappan21 · ‎04-27-2020

Hi Alex, The above issue is resolved by creating a playbook with proper Deployment file. But we are facing issue with below error [Errno 16] error opening local file from https://sasviyablobstorage6.blob.core.windows.net/sasviya-mirror-repository-35/sas_repos/repos/shipped/inteldecn/125/inteldecn-125-x64_redhat_linux_6-yum/Packages/s/sas-modelsvr1-03.21.00-20191104.232733829217.x86_64.rpm, IOError: [Errno 28] No space left on device: '/var/cache/yum/x86_64/7Server/sas-inteldecn-125-x64_redhat_linux_6-yum/packages/sas-modelsvr1-03.21.00-20191104.232733829217.x86_64.rpm'\nTrying other mirror.\nhttps://sasviyablobstorage6.blob.core.windows.net/sasviya-mirror-repository-35/sas_repos/repos/shipped/dmdatap/125/dmdatap-125-x64_redhat_linux_6-yum/Packages/s/sas-monitoring-2.2.7-20191105.1572981193739.x86_64.rpm: [Errno 16] error opening local file from https://sasviyablobstorage6.blob.core.windows.net/sasviya-mirror-repository-35/sas_repos/repos/shipped/dmdatap/125/dmdatap-125-x64_redhat_linux_6-yum/Packages/s/sas-monitoring-2.2.7-20191105.1572981193739.x86_64.rpm, IOError: [Errno 28] No space left on device: '/var/cache/yum/x86_64/7Server/sas-dmdatap-125-x64_redhat_linux_6-yum/packages/sas-monitoring-2.2.7-20191105.1572981193739.x86_64.rpm'\nTrying other mirror. Repository Warehouse is accesible and enough space as well. What needs to be done on this. Please guide.

Iyappan21 · ‎04-27-2020

Hi Experts, We are performing SAS Viya 3.5 Single Machine Deployment. Deployment is done with failed task : 1. We are able to see the folders under /opt/sas but it seems some of the m are missing. While analysing the log files we could see below: "stderr": "The generated orchestration is not current.\nYou must regenerate the orchestration for this order and restart the deployment.\n\nThe following software units are in the repository warehouse but not in the intended orchestration\n x64_redhat_linux_6-yum:default\n pgpoolc\n sas-postgresql-secure-11:rpm\n sas-postgresql-secure-libs-11:rpm\n sas_casserver_primary\n sas-pgpool-II-40:rpm\n sas_casserver_secondary\n sas-pgpool-II-40:rpm\n sas_casserver_worker\n sas-pgpool-II-40:rpm\n sasdatasvrc\n sas-pgpool-II-40:rpm", "stderr_lines": [ "The generated orchestration is not current.", "You must regenerate the orchestration for this order and restart the deployment.", "", "The following software units are in the repository warehouse but not in the intended orchestration", " x64_redhat_linux_6-yum:default", " pgpoolc", " sas-postgresql-secure-11:rpm", " sas-postgresql-secure-libs-11:rpm", " sas_casserver_primary", " sas-pgpool-II-40:rpm", " sas_casserver_secondary", " sas-pgpool-II-40:rpm", " sas_casserver_worker", " sas-pgpool-II-40:rpm", " sasdatasvrc", " sas-pgpool-II-40:rpm" ], Can anyone help us to get the issue and resolve it. Thanks

Iyappan21 · ‎04-27-2020

Hi, I have removed previous failed deployments with deploy clean up and below command : sudo rpm -e $(rpm -qg SAS) --nopreun Now the above issue is resolved. Thanks, Iyappan M S

Iyappan21 · ‎04-27-2020

HI, It doesn't help. While analysing further, could see the error message : 2020-04-27 07:56:26,466 p=12280 u=root | TASK [sas-requirements-java : Set Java to use Java 1.8 when it is not the default Java on the system] ******** 2020-04-27 07:56:26,466 p=12280 u=root | task path: /sasviyainst/SAS_Viya_playbook/roles/sas-requirements-java/tasks/main.yml:69 2020-04-27 07:56:26,514 p=12280 u=root | ok: [deployTarget] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } 2020-04-27 07:56:26,536 p=12280 u=root | Read vars_file '../vars.yml' 2020-04-27 07:56:26,537 p=12280 u=root | TASK [sas-requirements-java : If Java not found on host, display an error] *********************************** 2020-04-27 07:56:26,537 p=12280 u=root | task path: /sasviyainst/SAS_Viya_playbook/roles/sas-requirements-java/tasks/main.yml:79 2020-04-27 07:56:26,562 p=12280 u=root | skipping: [deployTarget] => { "changed": false, "skip_reason": "Conditional result was False" } 2020-04-27 07:56:26,581 p=12280 u=root | Read vars_file '../vars.yml' 2020-04-27 07:56:26,592 p=12280 u=root | Read vars_file '../vars.yml' 2020-04-27 07:56:26,592 p=12280 u=root | TASK [sas-requirements-java : Log a message 'Java was not found' on the host] Can you help us. Thanks, Iyappan M S

Iyappan21 · ‎04-23-2020

Hi Alex, Now I am getting error as ---- "msg": "Destination /opt/sas/viya/config/etc/sysconfig/sas-javaesntl/sas-java does not exist !"------ I have done deploy-cleanup.yml and still facing the same error. Is there any other process for cleanup unsuccessful deployments. One more point, we have mounted Opt/sas with ext4 filesystem in Linux. Will it impact on unsuccesful deployments? Its just a curious question. Kindly guide. Thanks, Iyappan M S

Iyappan21 · ‎04-23-2020

Hi Alex, The Values are : sasenv_java_home: "/usr/java/jre1.8.0_251/" sas_install_java: true I could see JAVA HOME has proper value in log file. Is it mandatory to install JDK?. I have installed JRE. Or is it mandatory to keep lower version of JRE? Please advice. Thanks , Iyappan M S

Iyappan21 · ‎04-23-2020

More details on Logs: 2020-04-22 23:42:54,767 p=5336 u=root | fatal: [deployTarget]: FAILED! => { "msg": "The conditional check 'sasenv_java_home is defined and sasenv_java_home and (usrjavacheck.stdout is defined and usrjavacheck.stdout is version(sas_minimum_java_version, '<'))' failed. The error was: Version comparison: LooseVersion instance has no attribute 'version'\n\nThe error appears to have been in '/sasviyainst/SAS_Viya_playbook/roles/sas-requirements-java/tasks/main.yml': line 10, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n ## User defined\n - name: Log the value of sasenv_java_home on each host\n ^ here\n" } 2020-04-22 23:42:54,768 p=5336 u=root | NO MORE HOSTS LEFT ******************************************************************************************* 2020-04-22 23:42:54,769 p=5336 u=root | PLAY RECAP *************************************************************************************************** 2020-04-22 23:42:54,769 p=5336 u=root | deployTarget : ok=98 changed=10 unreachable=0 failed=1 2020-04-22 23:42:54,769 p=5336 u=root | localhost : ok=9 changed=0 unreachable=0 failed=0 2020-04-22 23:49:08,565 p=7113 u=root | ansible-playbook 2.7.2

Iyappan21 · ‎04-23-2020

Hi Experts, We are doing single machine deployment.The results should failed 1. But folders are already created in Opt/sas and services are not available. While analysing the logs we can see errors with JAVA. Can anyone help me with this. Thanks!

Iyappan21 · ‎03-20-2020

Hi, Thanks for the comments! I have done a resync still the error is same. How it could be resolved? Kindly help on this. Thanks,' Iyappan M S

Iyappan21 · ‎03-20-2020

Hi Experts, We are performing deployment on single machine with mirror repository. Deployment is failed due to Mirror Repository (dagent-135-x64_redhat_linux_6-yum) could not found. Is it related with download limit but we use mirror repository? Is it OK to skip the (dagent-135-x64_redhat_linux_6-yum) repository? Error Message below: fatal: [deployTarget]: FAILED! => {"changed": false, "msg": "https://sasviyablobstorage6.blob.core.windows.net/sasviya-mirror-repository-35/sas_repos/repos/shipped/dagent/135/dagent-135-x64_redhat_linux_6-yum/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found\nTrying other mirror.\n To address this issue please refer to the below knowledge base article \n\nhttps://access.redhat.com/articles/1320623\n\nIf above article doesn't help to resolve this issue please open a ticket with Red Hat Support.\n\n\n\n One of the configured repositories failed (dagent-135-x64_redhat_linux_6-yum),\n and yum doesn't have enough cached data to continue. At this point the only\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\n\n 1. Contact the upstream for the repository and get them to fix the problem.\n\n 2. Reconfigure the baseurl/etc. for the repository, to point to a working\n upstream. This is most often useful if you are using a newer\n distribution release than is supported by the repository (and the\n packages for the previous distribution release still work).\n\n 3. Run the command with the repository temporarily disabled\n yum --disablerepo=sas-dagent-135-x64_redhat_linux_6-yum ...\n\n 4. Disable the repository permanently, so yum won't use it by default. Yum\n will then just ignore the repository until you permanently enable it\n again or use --enablerepo for temporary usage:\n\n yum-config-manager --disable sas-dagent-135-x64_redhat_linux_6-yum\n or \n subscription-manager repos --disable=sas-dagent-135-x64_redhat_linux_6-yum\n\n 5. Configure the failing repository to be skipped, if it is unavailable.\n Note that yum will try to contact the repo. when it runs most commands,\n so will have to try and fail each time (and thus. yum will be be much\n slower). If it is a very temporary problem though, this is often a nice\n compromise:\n\n yum-config-manager --save --setopt=sas-dagent-135-x64_redhat_linux_6-yum.skip_if_unavailable=true\n\nfailure: repodata/repomd.xml from sas-dagent-135-x64_redhat_linux_6-yum: [Errno 256] No more mirrors to try. \nhttps://sasviyablobstorage6.blob.core.windows.net/sasviya-mirror-repository-35/sas_repos/repos/shipped/dagent/135/dagent-135-x64_redhat_linux_6-yum/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found\n", "rc": 1, "results": []}

Online Status	Offline
Date Last Visited	‎09-07-2020 01:31 PM

Re: Failed to create remote module tmp path at dir /tmp/.root.ansible/...

Re: Failed to create remote module tmp path at dir /tmp/.root.ansible/...

Re: Failed to create remote module tmp path at dir /tmp/.root.ansible/...

Re: SAS Viya 3.5 Deployment failed: The generated orchestration is not...

Re: SAS Viya 3.5 Deployment failed: The generated orchestration is not...

Re: SAS Viya 3.5 Deployment failed: The generated orchestration is not...

SAS Viya 3.5 Deployment failed: The generated orchestration is not cur...

Re: SASViya 3.5 Single Machine deployment Failed - Java Error MEssage ...

Re: SASViya 3.5 Single Machine deployment Failed - Java Error MEssage ...

Re: SASViya 3.5 Single Machine deployment Failed - Java Error MEssage ...

Re: Failed to create remote module tmp path at dir /tmp/.root.ansible/...

Re: Failed to create remote module tmp path at dir /tmp/.root.ansible/...

Re: Failed to create remote module tmp path at dir /tmp/.root.ansible/...

Re: SAS Viya 3.5 Deployment failed: The generated orchestration is not...

Re: SAS Viya 3.5 Deployment failed: The generated orchestration is not...

Re: SAS Viya 3.5 Deployment failed: The generated orchestration is not...

SAS Viya 3.5 Deployment failed: The generated orchestration is not cur...

Re: SASViya 3.5 Single Machine deployment Failed - Java Error MEssage ...

Re: SASViya 3.5 Single Machine deployment Failed - Java Error MEssage ...

Re: SASViya 3.5 Single Machine deployment Failed - Java Error MEssage ...

Re: SASViya 3.5 Single Machine deployment Failed - Java Error MEssage ...

Re: SASViya 3.5 Single Machine deployment Failed - Java Error MEssage ...

SASViya 3.5 Single Machine deployment Failed - Java Error MEssage in L...

Re: SAS Viya deployment failed - configured repositories failed (dagen...

SAS Viya deployment failed - configured repositories failed (dagent-13...