Re: Problems accessing Dag's site via yum

Dag Wieers <[email protected]>
Newsgroups gmane.linux.freshrpms.user
Organization 3TI Web Hosting Services
Message-ID <[email protected]>
On Tue, 23 Aug 2005, Josh Kelley wrote:

> I'm having a very bizarre problem getting one of my systems to update
> from Dag's repo.
> 
> I have a CentOS 4 server set up to access
> http://apt.sw.be/redhat/el4/en/i386/dag/repodata/repomd.xml, the
> standard URL for Dag's RHEL/CentOS 4 repository.
> 
> It gets a "Connection refused" error every time I try to run yum.
> 
> My other CentOS 4 servers can access apt.sw.be just fine.
> 
> On the affected server, elinks also fails to access apt.sw.be, but wget
> works.
> 
> Access to other sites appears to work fine.
> 
> Changing the IP address did not help.  NAT'ing the affected server did
> not help.  Disabling firewall rules did not help.
> 
> When the connection is refused, a packet sniff reveals that apt.sw.be
> replies to the HTTP SYN request with a RST.  I'm not a TCP guru, but I
> can't see any significant differences between the connection attempts
> that succeed and the connection attempts that fail.  (The timestamp
> value is different, and wget on the affected server apparently tries
> twice to connect without seeint a RST; the second attempt succeeds.)
> 
> Any suggestions?

I'm forwarding this to the admin of HEAnet (where apt.sw.be is pointing 
to). Since they are one of biggest public mirrors of free software they 
handle that much load that they fequently run development Apache releases 
in order to test them under these unique conditions.

Since a month or more, I noticed that apt.sw.be sometimes takes a long 
time to have an initial connection. Afterwards everything goes more smooth 
(probably because it is reusing the same connection with HTTP/1.1).

It might have the same cause.

Kind regards,
--   dag wieers,  [email protected],  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.