Bug 83298
Summary: | rhn_check throws SSL.Error | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Boris Folgmann <boris> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED NOTABUG | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | gafton, mihai.ibanescu, rob |
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: | 2003-08-06 23:03:22 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
Boris Folgmann
2003-02-01 22:04:06 UTC
Can you check the clock on the machine in question? This looks to be the kind of error I've seen on machines with badly off sync time clocks. The clock is ok. The problem was an overloaded/faulty (?) primary DNS. It returned always "non existing" for every lookup e.g. nslookup www.zvw.de printed: Non-authoritative answer: *** Can't find www.zvw.de: No On the next day it worked again. Sadly my ISP could not find any problem with his DNS. Because the DNS returned "non existing" the local resolver did not try the secondary server which returned true results according to nslookup. I have the identical problem on my system, but at Red Hat 9.0. My system clock is correct and up to date (I reset it using bot the redhat and time-a.nist.gov time servers, and neither fixed the problem). I have the identical problem on my system, but at Red Hat 9.0. My system clock is correct and up to date (I reset it using bot the redhat and time-a.nist.gov time servers, and neither fixed the problem). Rob, have a look at this, it should help you. The certificate used by up2date and rhn_register to communicate with the Red Hat Network reached its end of life on August 28th 2003. Users attempting to connect to Red Hat Network will see SSL connection or certificate verification failures. New versions of the up2date and rhn_register clients are now available which are required for continued access to Red Hat Network. * RHSA-2003:267 for Red Hat Linux: https://rhn.redhat.com/errata/RHSA-2003-267.html * RHSA-2003:268 for Red Hat Enterprise Linux: https://rhn.redhat.com/errata/RHSA-2003-268.html New versions of the up2date client that contain the new certificate are immediately available for download at: https://rhn.redhat.com/help/latest-up2date.pxt For users who would prefer to install the new certificate directly, it is available at: https://rhn.redhat.com/help/ssl_cert.pxt - -the Red Hat Network Team |