|
Home > Archive > Red Hat Topics > December 2004 > apt-get woes
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Ben Hopkins 2004-12-03, 5:45 pm |
| This is a sad tale of problems lining up like a row of dominoes.
I'm posting this to multiple groups because I don't know where the
expertise lies to enlighten this sordid situation. If any of the groups
are extraneous, you can trim them from the reply.
Running RedHat 9, using Apache with mod-perl.
They (my brother-in-law and his wife) want to use Plone as a CMS to make
their life easier. Plone works hand-in-glove with zope, a web server,
both implemented in python.
OK, I have a week or so off work, so I will replace apache with zope (on
a test server), see if it works for the current web pages, and then
add Plone, which will let them make new pages using the CMS.
zope requires the newest version of python. I want to install Python as
an rpm, so I can replace (rpm -U) the current old Python and not mess up
the other things that depend on it.
The new Python had several 'Failed dependencies', and, trying to avoid a
descent into 'dependency hell', I looked into a little thing called apt
(Advanced Package Tool), which is supposed to find failed dependencies,
and get them, and so on.
Every single one of the attempts by `apt-get update` failed like this:
-------------
Err http://ayo.freshrpms.net redhat/9/i386 release
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection
timed out [IP: 32.1.7.112 80]
Err http://ayo.freshrpms.net redhat/9/i386/os pkglist
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection
timed out
-------------
After a season of feeling sorry for myself and banging my head up
against the wall, I found a there was a newer version of apt, so I got
it and upgraded (from 0.5.5 to 0.5.15).
Now only _some_ of the connection attempts _do not_ fail. The results
vary: sometimes certain ones work, sometimes other ones work. Are the
servers _that_ flaky?
Here is a sample output run:
--------------------
[root@acoma root]# apt-get update
Get:1 http://newrpms.sunsite.dk redhat/en/i386/9.0 release [493B]
Err http://apt.sw.be redhat/9/en/i386 release
Could not connect to apt.sw.be:80 (32.1.7.112), connection timed out
[IP: 32.1.7.112 80]
Err http://ayo.freshrpms.net redhat/9/i386 release
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection
timed out [IP: 32.1.7.112 80]
Fetched 493B in 2m0s (4B/s)
WORKED! -->Hit http://newrpms.sunsite.dk redhat/en/i386/9.0/newrpms pkglist
WORKED! -->Hit http://newrpms.sunsite.dk redhat/en/i386/9.0/newrpms release
Err http://apt.sw.be redhat/9/en/i386/dag pkglist
Could not connect to apt.sw.be:80 (32.1.7.112), connection timed out
Err http://ayo.freshrpms.net redhat/9/i386/freshrpms pkglist
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection
timed out
Err http://apt.sw.be redhat/9/en/i386/dag release
Could not connect to apt.sw.be:80 (32.1.7.112), connection timed out
Err http://ayo.freshrpms.net redhat/9/i386/freshrpms release
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection
timed out
Err http://ayo.freshrpms.net redhat/9/i386/os pkglist
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection
timed out
Err http://ayo.freshrpms.net redhat/9/i386/os release
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection
timed out
Err http://ayo.freshrpms.net redhat/9/i386/updates pkglist
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection
timed out
Err http://ayo.freshrpms.net redhat/9/i386/updates release
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection
timed out
Failed to fetch http://apt.sw.be/redhat/9/en/i386/base/release Could
not connect to apt.sw.be:80 (32.1.7.112), connection timed out [IP:
32.1.7.112 80]
Failed to fetch http://ayo.freshrpms.net/redhat/9/i386/base/release
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection timed
out [IP: 32.1.7.112 80]
Failed to fetch http://apt.sw.be/redhat/9/en/i386/base/pkglist.dag
Could not connect to apt.sw.be:80 (32.1.7.112), connection timed out
Failed to fetch http://apt.sw.be/redhat/9/en/i386/base/release.dag
Could not connect to apt.sw.be:80 (32.1.7.112), connection timed out
Failed to fetch
http://ayo.freshrpms.net/redhat/9/i...glist.freshrpms Could not
connect to ayo.freshrpms.net:80 (32.1.7.112), connection timed out
Failed to fetch
http://ayo.freshrpms.net/redhat/9/i...lease.freshrpms Could not
connect to ayo.freshrpms.net:80 (32.1.7.112), connection timed out
Failed to fetch http://ayo.freshrpms.net/redhat/9/i386/base/pkglist.os
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection timed out
Failed to fetch http://ayo.freshrpms.net/redhat/9/i386/base/release.os
Could not connect to ayo.freshrpms.net:80 (32.1.7.112), connection timed out
Failed to fetch
http://ayo.freshrpms.net/redhat/9/i...pkglist.updates Could not
connect to ayo.freshrpms.net:80 (32.1.7.112), connection timed out
Failed to fetch
http://ayo.freshrpms.net/redhat/9/i...release.updates Could not
connect to ayo.freshrpms.net:80 (32.1.7.112), connection timed out
Reading Package Lists... Done
Building Dependency Tree... Done
W: Release files for some repositories could not be retrieved or
authenticated. Such repositories are being ignored.
W: You may want to run apt-get update to correct these problems
E: Some index files failed to download, they have been ignored, or old
ones used instead.
[root@acoma root]#
------------------
(I put WORKED! --> in front of the two that appeared to work.)
What's going on? I'm not supplying configuration info or other stuff,
because there's so much I could say, and don't know what would be
helpful, so I'll give you what you say you need.
By the way, I can ping, and lynx, and ftp, and wget all those places
apt-get says it can't get to.
| |
|
|
|
| Apparently, _Ben Hopkins_, on 04/12/04 03:04,typed:
> Ben Hopkins wrote:
>
>
>
> UPDATE: Now I am completely bewildered. I tried and tried and tried,
> and the last time this happened:
>
> [root@acoma root]# apt-get update
> Get:1 http://ayo.freshrpms.net redhat/9/i386 release [1171B]
> Get:2 http://apt.sw.be redhat/9/en/i386 release [494B]
> Get:3 http://newrpms.sunsite.dk redhat/en/i386/9.0 release [493B]
> Fetched 2158B in 0s (4263B/s)
> Get:1 http://apt.sw.be redhat/9/en/i386/dag pkglist [1140kB]
> Hit http://ayo.freshrpms.net redhat/9/i386/freshrpms pkglist
> Hit http://ayo.freshrpms.net redhat/9/i386/freshrpms release
> Hit http://ayo.freshrpms.net redhat/9/i386/os pkglist
> Hit http://ayo.freshrpms.net redhat/9/i386/os release
> Hit http://ayo.freshrpms.net redhat/9/i386/updates pkglist
> Hit http://ayo.freshrpms.net redhat/9/i386/updates release
> Hit http://newrpms.sunsite.dk redhat/en/i386/9.0/newrpms pkglist
> Hit http://newrpms.sunsite.dk redhat/en/i386/9.0/newrpms release
> Hit http://apt.sw.be redhat/9/en/i386/dag release
> Fetched 1140kB in 8s (130kB/s)
> Reading Package Lists... Done
> Building Dependency Tree... Done
>
> Was gibt? How can this happen? What makes it work all of a sudden when
> it consistently failed before?
Maybe it is a MTU problem. If you are using ADSL connection, check what
MTU you have using the ifconfig command. If your MTU is 1500, try
changing it to 1470 and try again:
#> ifconfig eth0 mtu 1470
i.e. if your interface in your computer is eth0. Change accordingly.
->HS
| |
| Ben Hopkins 2004-12-08, 2:45 am |
| H. S. wrote:
> Apparently, _Ben Hopkins_, on 04/12/04 03:04,typed:
>
<snip>[vbcol=seagreen]
>
> Maybe it is a MTU problem. If you are using ADSL connection, check what
> MTU you have using the ifconfig command. If your MTU is 1500, try
> changing it to 1470 and try again:
> #> ifconfig eth0 mtu 1470
>
> i.e. if your interface in your computer is eth0. Change accordingly.
Forgive me for not replying sooner. I have not been able to access the
server in question for that past couple of days -- it's a couple of
hundred miles away, and suddenly stopped responding.
It's also at a location where nobody lives until it warms up again.
(Flagstaff, AZ).
Do you think it got too cold for the machine to work? The house has
been 'winterized' -- i.e. water drained out of the pipes, etc.
| |
| Steve Ackman 2004-12-10, 5:45 pm |
| On Wed, 08 Dec 2004 08:42:48 GMT, Ben Hopkins wrote:
> -- it's a couple of
> hundred miles away, and suddenly stopped responding.
>
> It's also at a location where nobody lives until it warms up again.
> (Flagstaff, AZ).
>
> Do you think it got too cold for the machine to work? The house has
> been 'winterized' -- i.e. water drained out of the pipes, etc.
I ran a machine in an unheated shed in NH starting
one year in February. No problems with a few nights
around 0°F.
Not saying that cold *couldn't* cause a malfunction,
just that in my case, it didn't.
--
Steve Ackman
http://twoloonscoffee.com (Need beans?)
http://twovoyagers.com (glass, linux & other stuff)
|
|
|
|
|