Up2date not working

[Jonathan Allen]

Hi All,

I have FC2 running on a machine inside our corporate firewall.  The machine
has no direct Internet access but must use squid running on the firewall
machine.  I started up2date, and it went through the setup-process for a
first-time connection.  I pointed it at squid:3128 and it seemed happy.
However, when I tell it to go and start work, it puts up the following
process dialog:

Fetching http://fedora.redhat.com/download/up2date-mirrors/fedora-core-2/headers/head...

and sits there on a permanent basis.  Monitoring the network, there is no
traffic and the squid log doesn't report any attempt to actually make the
access.

What gives ?

Jonathan

[William Hooper]

Jonathan Allen said:
> Hi All,
>
> I have FC2 running on a machine inside our corporate firewall.  The
> machine has no direct Internet access but must use squid running on the
> firewall machine.

up2date yum and apt backends ignore the proxy settings
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=102272

[Jonathan Allen]

William Hooper said:
> up2date yum and apt backends ignore the proxy settings
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=102272

Thanks - I did the 'export http_proxy' and ran "up2date -u" from the
command line.  It's still going, so it's a bit early to say that it
definitely worked, but it's a definite step forward.

Jonathan

[Thomas E Dukes]

> Hi All,
>
> I have FC2 running on a machine inside our corporate 
> firewall.  The machine has no direct Internet access but must 
> use squid running on the firewall machine.  I started 
> up2date, and it went through the setup-process for a 
> first-time connection.  I pointed it at squid:3128 and it 
> seemed happy.
> However, when I tell it to go and start work, it puts up the 
> following process dialog:
>
> Fetching 
> http://fedora.redhat.com/download/up2date-mirrors/fedora-core-
> 2/headers/header.info
>
> and sits there on a permanent basis.  Monitoring the network, 
> there is no traffic and the squid log doesn't report any 
> attempt to actually make the access.
>
> What gives ?

It might not be a squid problem as I had a similar problem on the first
update attempt.

I changed /etc/sysconfig/rhn/sources to a different mirror and things
updated.  Your mileage may vary.