On Thu, 24 Jun 2010, Terry wrote:
On Thu, Jun 24, 2010 at 11:23 PM, James Antill <james-yum@xxxxxxx> wrote:
Terry <td3201@xxxxxxxxx> writes:
> Hello,
>
> I have a single server that is giving me a fit. It is a RHEL
5.3 box that
> was installed with no package groups, not even base, so a
minimal install.
>
> I have the following proxy configuration in yum.conf:
> proxy=http://server:3128/
> proxy_username=DOMAIN%5Cbar
> proxy_password=foo
From that the latest yum (from 5.5 or upstream) would set a proxy for
http, https and ftp of:
http://DOMAIN%5Cbar:foo@server:3128/?
...does that look fine? Do you know what error you are getting?
--
James Antill -- james@xxxxxxx
_______________________________________________
Thanks for the reply. I am using yum-3.2.22-26.el5. I gave what you
suggested a try. Here's what my new config says:
proxy=http://DOMAIN%5Cfoo:bar@server:3128
[root@server network-scripts]# yum check-update
Loaded plugins: rhnplugin, security
There was an error communicating with RHN.
RHN support will be disabled.
Error communicating with server. The message was:
Connection refused
I double checked my firewall logs and it is completely ignoring the proxy
configuration because it is going directly to the Internet to get to RHN:
Jun 24 23:30:44 10.98.1.1 %ASA-4-106023: Deny tcp src
VLAN197:10.197.1.5/46109 dst outside:209.132.183.44/443 by access-group
"VLAN197-in" [0x0, 0x0]
It's hitting RHN directly, not via proxy.
Hmm - well if you're using the rhnplugin then yum's communication being
proxied has nothing to do with it.
what do you see in your rhn-plugin configuration?
specifically
/etc/sysconfig/rhn/up2date
-sv
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
