Open Source Development

Power Open Source Development

Explore the open source tools and capabilities for building and deploying modern applications on IBM Power platforms including AIX, IBM i, and Linux.


#Power


#Power

 View Only

  • 1.  Yum/Curl error

    Posted Mon March 15, 2021 05:00 PM
    Edited by Avery Keyes Tue March 16, 2021 04:39 PM
    Hello!

    I just installed yum on my host and I get the error below when running yum repolist.

    # yum repolist
    anonymous@public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/repodata/repomd.xml:">https://anonymous:anonymous@public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/repodata/repomd.xml: [Errno 14] curl#6 - "Couldn't resolve host 'public.dhe.
    ibm.com'"
    Trying other mirror.
    repo id repo name status
    AIX_Toolbox AIX generic repository 0
    AIX_Toolbox_71 AIX 7.1 specific repository 0
    AIX_Toolbox_noarch AIX noarch repository 0
    repolist: 0

    I started troubleshooting curl directly and I see what's displayed below:

    # curl www.google.com
    curl: (6) Couldn't resolve host 'www.google.com'

    Update (with no luck):
    I replaced public.dhe.ibm.com with the IP and now I get a new error:
    # yum repolist
    anonymous@170.225.15.112/aix/freeSoftware/aixtoolbox/RPMS/ppc/">https://anonymous:anonymous@170.225.15.112/aix/freeSoftware/aixtoolbox/RPMS/ppc/
    repodata/repomd.xml: [Errno 14] curl#60 - "SSL certificate problem: self signed
    certificate in certificate chain"
    Trying other mirror.
    repo id repo name status
    AIX_Toolbox AIX generic repository 0
    AIX_Toolbox_71 AIX 7.1 specific repository 0
    AIX_Toolbox_noarch AIX noarch repository 0
    repolist: 0
    #

    ------------------------------
    Avery Keyes
    ------------------------------
    #AIXOpenSource


  • 2.  RE: Yum/Curl error

    Posted Mon March 22, 2021 01:02 PM
    I think there is some problem in your name server and it is not able to resolve host.
    I would suggest to fix the nameserver. 

    If problem persist then you may want to use http instead of https and update ca-certificate.

    ------------------------------
    SANKET RATHI
    ------------------------------

    Original Message


Related Content