Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello, got an AWS machine. All works well with root, if I run yum update, but while using ansible or just logged in with a normal user and running: sudo yum update, it fails with:
Code:
Connection timed out after 100000 milliseconds
Does anybody know how to fix this or why does it happen?
NOTE: I use some AWS proxy for http/https which is setup in /etc/profile.d/proxy.sh and its accessible by all users.
If it works as root, the issue is most likely related to the user account.
1. Have you made sure, that the user account does have permissions to run sudo?
2. Have you made sure, that indeed all users have access to the proxy?
3. Did you try with a different user?
Looks like, whenever you try to connect with a regular user, the connection fails. I am fairly sure that the connection is the issue, because I suppose if it was for missing sudo permissions, you would get an access denied error and not just the connection timing out.
Unfortunately I am not too familiar with AWS - I will consult with a fellow Linux tech, who does work with this kind of stuff and see if he has an answer.
If it works as root, the issue is most likely related to the user account.
1. Have you made sure, that the user account does have permissions to run sudo?
2. Have you made sure, that indeed all users have access to the proxy?
3. Did you try with a different user?
Looks like, whenever you try to connect with a regular user, the connection fails. I am fairly sure that the connection is the issue, because I suppose if it was for missing sudo permissions, you would get an access denied error and not just the connection timing out.
Unfortunately I am not too familiar with AWS - I will consult with a fellow Linux tech, who does work with this kind of stuff and see if he has an answer.
1. Yes, otherwise I would get a different kind of error
2. Yes, doing echo $http_proxy, works for all users
3. Yes, 2 users in fact
Actually, if I try manually to download the repomd.xml file from the failed repo, I can do it as a normal user.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.