khan isn't speaking rpm anymore

RESOLVED FIXED

Status

RESOLVED FIXED
9 years ago
4 years ago

People

(Reporter: clouserw, Assigned: fox2mike)

Tracking

Details

(Reporter)

Description

9 years ago
[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.
(Assignee)

Comment 1

9 years ago
Fixed. Usually happens when some stuff is cached and then changes.
Assignee: server-ops → shyam
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

9 years ago
And pray what exactly are you doing on mradm01?
(Assignee)

Comment 3

9 years ago
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

Updated

9 years ago
Summary: mradm01 isn't speaking rpm anymore → khan isn't speaking rpm anymore
(Assignee)

Comment 5

9 years ago
Fixed on khan. Pointed the rpmforge repo to the world and not mradm01.
Status: REOPENED → RESOLVED
Last Resolved: 9 years ago9 years ago
Resolution: --- → FIXED
(Reporter)

Comment 6

9 years ago
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 → ---

Comment 7

9 years ago
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?
(Assignee)

Comment 8

9 years ago
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. :)
(Assignee)

Comment 10

9 years ago
Fixed.
Status: REOPENED → RESOLVED
Last Resolved: 9 years ago9 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.