topic Re: SAS Viya - VTA 8.4 Installation ran into Issue in Administration and Deployment

SAS Viya - VTA 8.4 Installation ran into Issue

mpratapwar — Fri, 15 Nov 2019 21:56:04 GMT

Error Message: "msg": "https://packages.microsoft.com/rhel/6/prod/repodata/repomd.xml: [Errno 12] Timeout on https://packages.microsoft.com/rhel/6/prod/repodata/repomd.xml: (28, 'connect() timed out!')\nTrying other mirror.\nError: Cannot retrieve repository metadata (repomd.xml) for repository: packages-microsoft-com-prod. Please verify its path and try again\n",

Re: SAS Viya - VTA 8.4 Installation ran into Issue

SASKiwi — Fri, 15 Nov 2019 22:16:38 GMT

@mpratapwar - I moved your post here for greater visibility.

Re: SAS Viya - VTA 8.4 Installation ran into Issue

mpratapwar — Fri, 15 Nov 2019 22:28:38 GMT

I tried adding timeout=52 in ansible.cfg and re-ran the installation. But it error-ed out with same error message.

Re: SAS Viya - VTA 8.4 Installation ran into Issue

alexal — Mon, 18 Nov 2019 13:37:36 GMT

@mpratapwar ,

It does appear Microsoft repository was defined on your system in /etc/yum.repos.d directory, but your Linux server can't set up a connection to that server:

2019-11-15 15:30:16,569 p=67468 u=m26440 | fatal: [deployTarget]: FAILED! => {
"changed": false, 
"failed": true, 
"invocation": {
"module_args": {
"allow_downgrade": false, 
"conf_file": null, 
"disable_gpg_check": false, 
"disablerepo": null, 
"enablerepo": null, 
"exclude": null, 
"install_repoquery": true, 
"installroot": "/", 
"list": null, 
"name": [
"sas-javaesntl"
], 
"security": false, 
"skip_broken": false, 
"state": "latest", 
"update_cache": false, 
"validate_certs": true
}
}, 
"msg": "https://packages.microsoft.com/rhel/6/prod/repodata/repomd.xml: [Errno 12] Timeout on https://packages.microsoft.com/rhel/6/prod/repodata/repomd.xml: (28, 'connect() timed out!')\nTrying other mirror.\nError: Cannot retrieve repository metadata (repomd.xml) for repository: packages-microsoft-com-prod. Please verify its path and try again\n", 
"rc": 1, 
"results": []
}

That problem isn't related to SAS and if you want to use that repository you have to fix a connection problem to https://packages.microsoft.com.

Re: SAS Viya - VTA 8.4 Installation ran into Issue

mpratapwar1 — Mon, 18 Nov 2019 20:31:07 GMT

I tried accessing the page using curl command and it seems to be working.

[m26440@blph724 ~]$ curl https://packages.microsoft.com/rhel/6/prod/repodata/repomd.xml

<?xml version="1.0" encoding="UTF-8"?>

<repomd xmlns="http://linux.duke.edu/metadata/repo" xmlns:rpm="http://linux.duke.edu/metadata/rpm">

<revision>1570554833</revision>

<data type="filelists">

<checksum type="sha256">c9748b18a7b943172ab2bb1592c530dc16280dc6ec1cfc6d231d1a758d58d98c</checksum>

<open-checksum type="sha256">9a4de8df6ed6156350d2e53adc1d6313ee58ceb13ddba2a933246a44be241cdb</open-checksum>

<location href="repodata/c9748b18a7b943172ab2bb1592c530dc16280dc6ec1cfc6d231d1a758d58d98c-filelists.xml.gz"/>

<timestamp>1570554846</timestamp>

<size>1383542</size>

<open-size>23453250</open-size>

</data>

<data type="primary">

<checksum type="sha256">a56260fd99b8d8f45df0b2c08c623a4514c82f214512bc9abb650838cf619533</checksum>

<open-checksum type="sha256">410d2d3af6e6ab9d46b8b27d5adfe0bd0318bdf50e6b37b0874bd4a91eb8f015</open-checksum>

<location href="repodata/a56260fd99b8d8f45df0b2c08c623a4514c82f214512bc9abb650838cf619533-primary.xml.gz"/>

<timestamp>1570554846</timestamp>

<size>24451</size>

<open-size>301838</open-size>

</data>

<data type="primary_db">

<checksum type="sha256">3b2e76258739ea7b5d92eeaaa898f971d90cccac18993e3ff6e921e1eb16febd</checksum>

<open-checksum type="sha256">5f41922ac6c4156a9ee1523bd03f03db486f6df8fced0bae52980ecb0d34a68a</open-checksum>

<location href="repodata/3b2e76258739ea7b5d92eeaaa898f971d90cccac18993e3ff6e921e1eb16febd-primary.sqlite.bz2"/>

<timestamp>1570554849</timestamp>

<database_version>10</database_version>

<size>70578</size>

<open-size>462848</open-size>

Re: SAS Viya - VTA 8.4 Installation ran into Issue

alexal — Mon, 18 Nov 2019 20:37:00 GMT

@mpratapwar1 ,

Your Linux administrator should be able to help you with that. Have you had a chance to speak with him/her?