Description of problem: # up2date -l There was an SSL error: [('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')] A common cause of this error is the system time being incorrect. Verify that the time on this system is correct. The system time and date is correct since I use rdate from crontab. Version-Release number of selected component (if applicable): up2date-3.1.23.1-5 How reproducible: Always. It appears suddenly, the up2date service was running without problems last days. Steps to Reproduce: 1. up2date -l or anything option 2. 3. Actual results: Can use redhat network service at all. Expected results: List the new packages and update them, of course. Additional info: I tried to use stunnel as I read in other bugs reports at bugzilla, but I couldn't: # /usr/sbin/stunnel -r xmlrpc.rhn.redhat.com:443 -cf -v 2 -A /usr/share/rhn/RHNS-CA-CERT 2003.08.29 11:48:20 LOG3[18651:1076046944]: -r: No such file or directory (2) It's strange, isn't it?
Sorry, I wrote... Actual results: Can use redhat network service at all. instead of... Actual results: Can't use redhat network service at all. I research into bugzilla and I am can confirm there is no time or date problems: # date vie ago 29 11:58:48 CEST 2003 neither dns problems: # host xmlrpc.rhn.redhat.com xmlrpc.rhn.redhat.com has address 66.187.232.101
*** This bug has been marked as a duplicate of 103336 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.