Bug 87883
| Summary: | up2date SSL errors | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Chris Ricker <chris.ricker> |
| Component: | rhnlib | Assignee: | Mihai Ibanescu <mihai.ibanescu> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | gafton, mihai.ibanescu |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-10-07 04:51:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Chris Ricker
2003-04-03 15:42:22 UTC
BTW, this machine was a fresh everything install of RHL 9, plus the proposed glibc errata (glibc-2.3.2-22.9) Same error, different system. This time the system was a RHL 9 with all errata as of 20030408 (ie, kernel-smp-2.4.20-9, but not the glibc errata released 20030409) [kaboom@verdande kaboom]$ sudo up2date --nox -u Fetching package list for channel: redhat-linux-i386-9... ######################################## Fetching Obsoletes list for channel: redhat-linux-i386-9... ######################################## Fetching rpm headers... There was an SSL error: (104, 'Connection reset by peer') A common cause of this error is the system time being incorrect. Verify that the time on this system is correct. [kaboom@verdande kaboom]$ And on a third machine, I just got a similar meaningless SSL error when I tried
to up2date:
[kaboom@skuld kaboom]$ sudo up2date --nox -u
There was an SSL error: [('SSL routines', 'SSL23_GET_SERVER_HELLO', 'unknown
protocol')]
A common cause of this error is the system time being incorrect. Verify that the
time on this system is correct.
[kaboom@skuld kaboom]$
This machine, like the other two, is time-synchronized using ntpd, so the
explanation is nonsense here too....
I only write 'up2date' command and I have the same error and I have time-synchronized using ntpd too Grettings Should be fixed in newer rhnlib packages I believe... |