search for: retrycod

...DigiCert Global Root G2 # DigiCert Global Root G3 # DigiCert High Assurance EV Root CA # DigiCert Trusted Root G4 > * Closing connection 29 > 2019-08-29 17:23:18,117 exception: [Errno 14] curl#60 - "Peer's > Certificate issuer is not recognized." > 2019-08-29 17:23:18,117 retrycode (14) not in list [-1, 2, 4, 5, 6, > 7], re-raising [ ... ] > Cannot retrieve metalink for repository: epel/x86_64. Please verify > its path and try again So can we check what version of the ca-certificates packages is being installed on your system? And a check into a different direc...

...: None, 'progress_obj' : None, 'proxies' : None, 'proxy' : None, 'quote' : None, 'range' : None, 'reget' : None, 'retry' : None, 'retry_no_cache': False, 'retrycodes' : [-1, 2, 4, 5, 6, 7], 'size' : None, 'ssl_ca_cert' : None, 'ssl_cert' : None, 'ssl_cert_type': 'PEM', 'ssl_context' : None, 'ssl_key' : None, 'ssl_key_pass' : None, 'ssl_...

Am 2019-08-29 17:36, schrieb Gary Stainburn: > On Thursday 29 August 2019 16:20:00 Alexander Dalloz wrote: >> Hi, >> >> yum uses libcurl behind the scenes and thus NSS and not OpenSSL. >> >> Do you get something indicative when running: >> >> URLGRABBER_DEBUG=1 yum --disablerepo=\* --enablerepo=webtatic >> check-update >> >>

...: None, 'progress_obj' : None, 'proxies' : None, 'proxy' : None, 'quote' : None, 'range' : None, 'reget' : None, 'retry' : 10, 'retry_no_cache': False, 'retrycodes' : [-1, 2, 4, 5, 6, 7], 'size' : None, 'ssl_ca_cert' : None, 'ssl_cert' : None, 'ssl_cert_type': 'PEM', 'ssl_context' : None, 'ssl_key' : None, 'ssl_key_pass' : None, 'ssl_...

Am 2019-08-29 16:51, schrieb Gary Stainburn: > On Thursday 29 August 2019 15:45:44 Gordon Messmer wrote: >> On 8/29/19 3:03 AM, Gary Stainburn wrote: >> > https://us-east.repo.webtatic.com/yum/el7/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized." >> >> >> What do you see when you run: >>

ok a good hint. I will test it monday. Ralf Von meinem iPhone gesendet > Am 10.01.2019 um 18:23 schrieb Mogens Kjaer <mk at lemo.dk>: > >> On 1/10/19 11:32 AM, Ralf Prengel wrote: >> yum install doesn't work running the script via cron allthough yum remove works. > > Is the network up when the script executes? > > Mogens > > -- > Mogens

On Thursday 29 August 2019 18:10:19 Alexander Dalloz wrote: > > 2019-08-29 17:23:18,117 exception: [Errno 14] curl#60 - "Peer's > > Certificate issuer is not recognized." > > 2019-08-29 17:23:18,117 retrycode (14) not in list [-1, 2, 4, 5, 6, > > 7], re-raising > > [ ... ] > > > Cannot retrieve metalink for repository: epel/x86_64. Please verify > > its path and try again > > So can we check what version of the ca-certificates packages is being > installed on you...

...=www.digicert.com,O=DigiCert Inc,C=US * NSS error -8179 (SEC_ERROR_UNKNOWN_ISSUER) * Peer's Certificate issuer is not recognized. * Closing connection 29 2019-08-29 17:23:18,117 exception: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized." 2019-08-29 17:23:18,117 retrycode (14) not in list [-1, 2, 4, 5, 6, 7], re-raising Based on that it appears to me very clear that the trust with the DigiCert chain wasn't given due to a missing trust from the ca-cert bundle. Unfortunately we haven't seen a status of the ca-certificates RPM content before fixing it wit...

On 8/30/19 5:52 AM, Gary Stainburn wrote: > Incidentally, the*good* server that I was referencing my broken server against has decided to start giving the curl certificate errors in the same way that the broken one did. Very strange. I ran It's possible that the error is unrelated to the ca-certificates file.? You'll only see it if yum selects a mirror that uses a Let's Encrypt

...<gary.stainburn at ringways.co.uk> wrote: > On Thursday 29 August 2019 18:10:19 Alexander Dalloz wrote: > > > 2019-08-29 17:23:18,117 exception: [Errno 14] curl#60 - "Peer's > > > Certificate issuer is not recognized." > > > 2019-08-29 17:23:18,117 retrycode (14) not in list [-1, 2, 4, 5, 6, > > > 7], re-raising > > > > [ ... ] > > > > > Cannot retrieve metalink for repository: epel/x86_64. Please verify > > > its path and try again > > > > So can we check what version of the ca-certificates...

Am 2019-08-30 10:52, schrieb Gary Stainburn: > On Thursday 29 August 2019 18:10:19 Alexander Dalloz wrote: >> > 2019-08-29 17:23:18,117 exception: [Errno 14] curl#60 - "Peer's >> > Certificate issuer is not recognized." >> > 2019-08-29 17:23:18,117 retrycode (14) not in list [-1, 2, 4, 5, 6, >> > 7], re-raising >> >> [ ... ] >> >> > Cannot retrieve metalink for repository: epel/x86_64. Please verify >> > its path and try again >> >> So can we check what version of the ca-certificates packages...