BookmarkSubscribeRSS Feed
Iyappan21
Obsidian | Level 7

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/shipp...: [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": []}

3 REPLIES 3
Anand_V
Ammonite | Level 13

Hi @Iyappan21 

 

Does your host yum repo has this package? You can check it using yum list available | grep -i sas-*

If the package isn't available then you will have to download it and place it in your repo hosted directory. In-case the package is available and if you still see this error, it could be corrupted?

Try syncing your repos again.

 

mirrormgr mirror --deployment-data <path>/SAS_Viya_deployment_data.zip --path <path>/sas_repos --platform <platform-version> --latest

Iyappan21
Obsidian | Level 7

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

Anand_V
Ammonite | Level 13
Hi @iyappan,

If you have the rpm and still facing the same issue, I would suggest you to raise a track with SAS TS by emailing the error snaps and logs to support@sas.com for faster resolution.

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 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 1401 views
  • 1 like
  • 2 in conversation