search for: urlgrabber_debug

...O = Let's Encrypt, CN = Let's Encrypt Authority X3 > verify return:1 > depth=0 CN = webtatic.com > verify return:1 [ ... ] > Verify return code: 0 (ok) 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 Alexander

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 >> >> Alexander > > I get a lot of output for what looks like access to the local respos.d > files all ending with success. I have included below the first and > last of these immediately followed by the li...

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 > > Alexander I get a lot of output for what looks like access to the local respos.d files all ending with success. I have included below the first and last of these immediately followed by the line saying that webtastic is not...

...Alexander Dalloz wrote: > yum uses libcurl behind the scenes and thus NSS and not OpenSSL. Good to know. In that case: Gary, what do you see when you run: ??? /usr/lib64/nss/unsupported-tools/vfyserv -p 443 us-east.repo.webtatic.com > Do you get something indicative when running: > URLGRABBER_DEBUG=1 yum --disablerepo=\* --enablerepo=webtatic > check-update webtatic is the mirror, not a repo.? That won't do anything useful, will it?

...d the scenes and thus NSS and not OpenSSL. > > > Good to know. > > In that case: Gary, what do you see when you run: > > ??? /usr/lib64/nss/unsupported-tools/vfyserv -p 443 > us-east.repo.webtatic.com > >> Do you get something indicative when running: >> URLGRABBER_DEBUG=1 yum --disablerepo=\* --enablerepo=webtatic >> check-update > > > webtatic is the mirror, not a repo.? That won't do anything useful, > will it? In posting https://lists.centos.org/pipermail/centos/2019-August/173288.html you could see that he has a repo "webtatic...

.......... d /usr/share/man/man5/cert8.db.5.gz ......... d /usr/share/man/man5/cert9.db.5.gz ......... d /usr/share/man/man5/key3.db.5.gz ......... d /usr/share/man/man5/key4.db.5.gz ......... d /usr/share/man/man5/pkcs11.txt.5.gz ......... d /usr/share/man/man5/secmod.db.5.gz [root at stan2 ~]# URLGRABBER_DEBUG=1 yum --disablerepo=\* --enablerepo=epel update [snip] Loading mirror speeds from cached hostfile 2019-08-29 17:23:17,344 combined options: { 'text' : 'epel/x86_64/metalink', 'delegate' : { 'async' : None, 'bandwidth' : 0,...

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: ??? openssl s_client -showcerts -connect us-east.repo.webtatic.com:443

...b.5.gz > ......... d /usr/share/man/man5/key3.db.5.gz > ......... d /usr/share/man/man5/key4.db.5.gz > ......... d /usr/share/man/man5/pkcs11.txt.5.gz > ......... d /usr/share/man/man5/secmod.db.5.gz Ok, that package content looks healthy. No problem there. > [root at stan2 ~]# URLGRABBER_DEBUG=1 yum --disablerepo=\* > --enablerepo=epel update > [snip] > Loading mirror speeds from cached hostfile > 2019-08-29 17:23:17,344 combined options: { > 'text' : 'epel/x86_64/metalink', [ ... ] > 2019-08-29 17:23:17,344 attempt 1/10: > https://mirror...