Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
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.
[root@pmd HadGEM]# yum install glibc-devel
Loaded plugins: rhnplugin, security
This system is not registered with RHN.
RHN support will be disabled. http://10.0.0.1/repos/1000/Server/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (111, 'Connection refused')>
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: kusu-installer-Server. Please verify its path and try again [root@pmd HadGEM]# uname -a
Linux pmd.pakmet.com 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
[root@pmd HadGEM]#
so HAVE you verified the path?? someone has clearly set up a local server in your LAN, on 10.0.0.1 so there's probably an isseu with that, or reaching it.
BTW, just dumping console output and thinking it alone makes a good post on a forum.. nope. you need to actually give us some context, what you've already tried etc.
Dear Chris
Actually its a cluster system installed using Platform cluster manager, 10.0.0.1 is the default gateway ip of cluster. Please have a look at below file
[kusu-installer-VT]
name=Kusu installer rhel 5 x86_64
baseurl=http://10.0.0.1/repos/1000/VT
enabled=1
gpgcheck=0
gpgkey=http://10.0.0.1/repos/1000/RPM-GPG-KEY-KUSU
I have another backup cluster on which same yum.conf file is present with ip 20.0.0.1 and the yum is working fine there
yes, look at that server. this is VERY clearly NOTHIGN to do with yum. It's YOUR server that YOU set up to host a repo. Fix it, or the generic networking to it.
Consider me a newbie or not an expert to such a level. I didn't set up anything as I said all this settings are by default I just defined network IP of this cluster during installation (i.e 10.0.0.0).
To test this I have built another cluster with the network ID 20.0.0.0 and there the yum is working successfully.
[root@pmd ~]# wget http://10.0.0.1/repos/1000/Server/repodata/repomd.xml
--07:59:30-- http://10.0.0.1/repos/1000/Server/repodata/repomd.xml
Connecting to 10.0.0.1:80... failed: Connection refused.
[root@pmd ~]#
"you" doesn't necessarily mean you as a person. You have non-default config from a distro perspective. someone has changed that configuration outside of anything official. If it wasn't you personally, go find the guy that did do it, or may know something about that server or the network infrastructure within which is resides for assistance. There settings are NOT by default.
I know this is not the default config from the Redhat. But I think during cluster installation it is default configuration, as I am the person who installed this cluster and then didnt change any thing. Just to add the following path and xml is present.
/repos/1000/Server/repodata/repomd.xml
Now yum update worked, but I am not able to find any package
like [root@pmd yum.repos.d]# yum install glibc-devel
Loaded plugins: rhnplugin, security
This system is not registered with RHN.
RHN support will be disabled.
Setting up Install Process
Parsing package install arguments
No package glibc-devel available.
Nothing to do
[root@pmd yum.repos.d]# yum list glibc-devel
Loaded plugins: rhnplugin, security
This system is not registered with RHN.
RHN support will be disabled.
Error: No matching Packages to list
[root@pmd yum.repos.d]#
Although I installed this package on the other system at the same time
[root@pmd02 pmdtest]# yum reinstall glibc-devel.i386
Loaded plugins: rhnplugin, security
This system is not registered with RHN.
RHN support will be disabled.
Setting up Reinstall Process
Resolving Dependencies
--> Running transaction check
---> Package glibc-devel.i386 0:2.5-34 set to be erased
---> Package glibc-devel.i386 0:2.5-34 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
glibc-devel i386 2.5-34 kusu-installer-Server 2.0 M
Removing:
glibc-devel i386 2.5-34 installed 4.6 M
Total download size: 2.0 M
Is this ok [y/N]: y
Downloading Packages:
glibc-devel-2.5-34.i386.rpm | 2.0 MB 00:00
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Erasing : glibc-devel [1/2]
Installing : glibc-devel [1/2]
Sorry for the all the messup.
My point is I want from yum working. If my path or /etc/yum.repos.d/kusu-installer.repo file is wrong what you advise me to do to make it work.
1. check on and fix the SELinux configuration on the repo server and repo client if applicable.
2. check on and fix the firewall configuration on the repo server and repo client if applicable.
3 ensure the repo server is pingable from the repo client.
4. ensure that port 80 is being listened on on the repo server and that requests from the repo client reach the port.
5. Check on the permissions of the repo resource in focus from the mount point up.
5. Check on / compare the http / network / SELinux / firewall / yum configurations on the working and non working repo clients.
Yum will say " nothing to install " if it sees that the package in focus is already installed and will reinstall a package that is already installed. ie a install is not the same as a reinstall.
Is there a reason " yum install glibc-devel " is expected to behave the same as " yum reinstall glibc-devel.i386 " ?
Last edited by smbhandary; 02-11-2013 at 12:13 AM.
Reason: improvements...
[root@pmd HadGEM]# yum install glibc-devel
Loaded plugins: rhnplugin, security
This system is not registered with RHN.
RHN support will be disabled. http://10.0.0.1/repos/1000/Server/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (111, 'Connection refused')>
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: kusu-installer-Server. Please verify its path and try again
Connection refused means the request is reaching but not able to access because of
Port is not open or firewall might be blocking ... ask network admin at switch level configuration to open the port for http for the server which you are using.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.