Bug 103433 - Rhn connection didn't connect through squid proxy server.
Rhn connection didn't connect through squid proxy server.
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: rhn-applet (Show other bugs)
9
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Veillard
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-08-30 05:38 EDT by Chan Min Wai
Modified: 2007-04-18 12:57 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-30 06:38:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chan Min Wai 2003-08-30 05:38:52 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; zh-TW; rv:1.2.1) Gecko/20030225

Description of problem:
After getting the new ssl Cert and the Rhn, The Rhn now starting to be weird it
cannot connection to Rhn using the proxy server.

I've my firewall blocking any direct access to the internet and that cause the
firewall log have the following error.

Aug 30 17:24:20 gw Block host "" internet access - Source=192.168.0.2 -
Destination=66.187.232.101:443 - HTTPS, Group Everyone

FYI, By just running up2date it self using root does run via the proxy. So the
only problem would be the python Rhn applet.



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Setup squid proxy server, setup the new rhn server to connect via proxy.
2. Now start Rhn icon notice it will first show blue then change an unconnect
icon later prompt a "Network error :110" Message box.

    

Actual Results:  "Network error :110" Message box popup later (a few minutes)

Expected Results:  Rhn should run trough proxy without any problem.

Additional info:
Comment 1 Daniel Veillard 2003-08-30 05:51:13 EDT
Nothing changed recently in the way the rhn-applet connects to the services.
The upgrade should only have affected the CERT certificates from an rhn-applet
point of view. Please check that the registration and proxy informations are
properly provided in :

/etc/sysconfig/rhn/rhn-applet
$(HOME)/.rhn-applet.conf

This is very likely to be a configuration problem. If everything is 
correctly set-up then provide the result of:

rpm -q rhnlib rhn-applet up2date up2date-gnome
and
rpm -V rhnlib rhn-applet up2date up2date-gnome

Daniel
Comment 2 Daniel Veillard 2003-08-30 05:57:25 EDT
I don't think the report can qualify as a security issue. The only effect is
that you get reported that the applet cannot connect to the service. The 
fact that the applet tries to connect to the RHN servers is part of the
definition of the service provided, it has no direct security implication.
I will change severity back to the normal level, do not change that unless
you can provide a description in how this might lead to a security issue.

Daniel
Comment 3 Chan Min Wai 2003-08-30 06:38:45 EDT
So that is my problem 
$(HOME)/.rhn-applet.conf was not setup correctly...
And I don't have a chance to change (when the configure is wrong) due to that
Rhn applet is not responding all time, and the "configre" is unclickable.

I've to delete the .rhn-applet.conf to reconfigure it.

Anyway this is solve.

Note You need to log in before you can comment on or make changes to this bug.