Closed Bug 546986 Opened 14 years ago Closed 14 years ago

khan isn't speaking rpm anymore

Categories

(mozilla.org Graveyard :: Server Operations, task)

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: clouserw, Assigned: fox2mike)

Details

[root@khan ~]# yum list | grep python
http://mradm01/pub/rpmforge/el5/en/i386/dag/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (111, 'Connection refused')>


Searches still work, but installing stuff seems to fail with a "No more mirrors to try." error.
Fixed. Usually happens when some stuff is cached and then changes.
Assignee: server-ops → shyam
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
And pray what exactly are you doing on mradm01?
I think you meant khan.
Summary: mradm01 isn't speaking rpm anymore → khan isn't speaking rpm anymore
(khan) $ sudo yum clean all
(khan) $ sudo yum install siege
[....blah blah blah...]
http://mradm01/pub/rpmforge/el5/en/i386/dag/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (111, 'Connection refused')>
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: khan isn't speaking rpm anymore → mradm01 isn't speaking rpm anymore
Summary: mradm01 isn't speaking rpm anymore → khan isn't speaking rpm anymore
Fixed on khan. Pointed the rpmforge repo to the world and not mradm01.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
This is broken on sm-hudson01 now.  That's why I filed the bug that mradm01 is broken and not khan.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
mradm01 was decommissioned as an rhn host in favor of nm-rhn01 however, I don't know what has to happen to change configs.

shyam, you know rhn moved right?
yeah, but this is because we were pointing to mradm01 for rpmforge as well, which is what the errors are about.
All the package repos are at mrepo.mozilla.org now.  Look on other boxes that work for what's in the .repo files.  Or just puppetize khan and puppet will fix it. :)
Fixed.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.