Bug 26841 - up2date not connecting to server
Summary: up2date not connecting to server
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Preston Brown
QA Contact: Aaron Brown
Whiteboard: Florence Gold
Depends On:
TreeView+ depends on / blocked
Reported: 2001-02-09 16:21 UTC by Iulian Florin VLADU
Modified: 2007-04-18 16:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-12 09:22:15 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Iulian Florin VLADU 2001-02-09 16:21:33 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.0-0.99.11 i686)

up2date -r (anonymous) will not connect to server. The message is "unable
to set-up CONNECTION tunnel".

I use a http proxy and this was set up with RHN configuration.

Reproducible: Always
Steps to Reproduce:
1.  Program | System | RHN Update Agent - root password
2.  Red Hat Update Agent | Next | Update Agent Progress
3.  Error  - There was a fatal error communicating with the server. The
message was: "unable to set up CONNECTION tunnel"

Actual Results:  Fail to update

Expected Results:  Update

I tryed in a termonal window with up2date -r. The result was the same. Is
the server up?

Comment 1 Glen Foster 2001-02-09 23:09:03 UTC
We (Red Hat) should really try to resolve this before next release.

Comment 2 Iulian Florin VLADU 2001-02-12 09:22:07 UTC
That was quick. I tried again today and it worked. The sequence was as follows:

1. Running directly up2date from Program | System ... resulted in an error with
the message "Invalid server certificate".

2. Running up2date -r in a terminal window produced a new message ("Successfully
completed anonymous registration. You do not need to use this option in the
future.") and then the update was sucessfull (only one new package).


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