Yum update could not retrieve mirrorlist




















To complement: aws. Could you please briefly explain or post a link on how to edit this policy? Thank you! I struggled for several hours why I couldn't even ping the yum repo. Adding your policy fixed it. Even I had the same issue. Then I rebooted the instance and I had the same error. You can check my question here: stackoverflow. Correct me if I'm wrong, but Security Groups are stateful in AWS, meaning that anything setup in inbound traffic also does the same for outbound traffic.

I suppose though, if you had this tied to your single IP address, then it wouldn't work in the outbound mode, maybe? AspiretoCode I totally agree with you — lft93ryt. By default, security groups allow all outbound traffic. CyclingDave Interesting, that seems like a Terraform-specific thing. Show 3 more comments. I have the same problem and was related to name resolution.

Community Bot 1 1 1 silver badge. Add a comment. In my case, outbound was deleted. I again set to "All traffic" and it works.

Amit Baderia Amit Baderia 2, 17 17 silver badges 15 15 bronze badges. ElasticThoughts ElasticThoughts 3, 7 7 gold badges 42 42 silver badges 57 57 bronze badges. Lejdi Prifti Lejdi Prifti 97 6 6 bronze badges. The same worked for me.

I am following acloud. In the series they rarely allow inbound HTTPS, and in the beginning I couldn't understand why my instances behaved differently than theirs. I believe the course was recorded in and assumably many of the repositories have updated to HTTPS protocol since then.

This works for me too. Thanks for your answer. Go to console. Yoonian Yoonian 12 12 silver badges 13 13 bronze badges. It's not the same. Yes, this. The yum servers from web respond back through the ephemeral ports, which means inbound traffic comes from the web into the VPC, somewhere between and , back through the ig, then the nACL, and sg. There are a few ways to work "fix" this: Contact the upstream for the repository and get them to fix the problem.

Quick fix You will have to open inbound Ephemeral ports for this yum update. For example adding the inbound rule below: Notice that this is still necessary even if the outbound rules allow all traffic: Why did have to do this? RtmY RtmY Kent L. Estes Kent L. Estes 1. Ambar Hassani Ambar Hassani 1. Phani Kumar M 4, 1 1 gold badge 12 12 silver badges 25 25 bronze badges. EC2newbie EC2newbie 1.

Gaurav Seth Gaurav Seth 3 3 silver badges 9 9 bronze badges. JoSSte 2, 5 5 gold badges 28 28 silver badges 43 43 bronze badges. Erick Erick 47 2 2 silver badges 6 6 bronze badges. Andrew Hude Andrew Hude 1. Ananize Scott Ananize Scott 1 1 gold badge 8 8 silver badges 10 10 bronze badges.

Here is perfect answer i found go to outbound rules add All Traffic That's it. Mallikarjuna Reddy Mallikarjuna Reddy 1. Hello asktyagi! Something weird happend, I installed vmware pro 14 in my desktop, the remote machine is using vmware Like i said, the yum didnt work at all on remote computer, so i did a installation on vmware 14 plus a backup and uploaded to google drive. Downloaded to remote machine and opened via vmware and now it runs yum without problems Thx for the help!

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 0. Hot Network Questions. Question feed. Server Fault works best with JavaScript enabled.

Post by avij » Fri Apr 19, pm Well, that's odd. Have you done anything odd to curl, like updated it from some other source? If you have bind-utils installed you could try running dig 8. Pinging the DNS server might not be a sufficient test. You could also try some other public DNS server like 1. Post by vimba » Sat Apr 20, pm I installed fedora server in virutalbox which has an updated version of CURL, but the problem still exists..

Post by TrevorH » Sat Apr 20, pm The analysis that curl needs to be rebuilt is completely wrong. Our shipped version of curl works perfectly thanks. It's not doing what you think it is and it's not valid. Use the FAQ Luke. Post by vimba » Sat Apr 20, pm Hello okay thanks. Post by vimba » Sun Apr 21, pm Hello I updated virutal box to the latest version Updated by uninstalling the old version and installing the new version..



0コメント

  • 1000 / 1000