AIX Open Source

AIX Open Source

Share your experiences and connect with fellow developers to discover how to build and manage open source software for the AIX operating system

 View Only
  • 1.  yum repo time out errors , repo is on prod network. prod servers works , but dev and test fails

    Posted Wed March 23, 2022 02:01 AM
    Edited by Nag N Thu March 24, 2022 09:51 AM
    Our yum repo was on AIX prod server in production network . Yum works fine on prod servers but yum times out if I am on dev/test network.
    I am sorry for posting again , I could not change previous title.

    Does yum needs any firewall ports to be opened ? I am guessing our firewall team changed rules between prod and nonprod . 

    On  non prod server:
    yum -y install sudo_noldap-1.9.5p2-1.ppc
    http://server1.edc.com/aixtoolbox/AIX_Toolbox/repodata/repomd.xml: [Errno 12] Timeout on http://server1.edc.com/aixtoolbox/AIX_Toolbox/repodata/repomd.xml: (28, 'Connection timed out after 30000 milliseconds')
    Trying other mirror.

    On Prod server:
    yum -y install sudo_noldap-1.9.5p2-1.ppc ....... it installs the rpm.

    Please suggest , what leads these timeout errors . it was working 6 months ago . We upgraded sudo on all non prod servers using yum . Same yum repo and no changes  and repo is on production network.




    ------------------------------
    Nag N
    ------------------------------


  • 2.  RE: yum repo time out errors , repo is on prod network. prod servers works , but dev and test fails

    Posted Wed March 23, 2022 09:51 AM
    Please check whether you are able to ping the prod server from the machine. Also you can try invoking curl to get a file from the repo. 
    This mostly looks like a network issue.

    ------------------------------
    Ayappan P
    ------------------------------



  • 3.  RE: yum repo time out errors , repo is on prod network. prod servers works , but dev and test fails

    Posted Wed March 23, 2022 11:05 AM
    Thanks Ayyappan.  Our network team blocked logins and pings from nonprod to prod  network I guess about 2 years ago.  I am new to this open source and AIX , can you please let me know what options to use with curl command. So , I can run and post the output here

    Really appreciate you for taking time to help with this issue.

    ------------------------------
    Nag N
    ------------------------------



  • 4.  RE: yum repo time out errors , repo is on prod network. prod servers works , but dev and test fails

    Posted Wed March 23, 2022 12:43 PM
    If you are not able to ping or connect to prod (yum server) then curl will also not work. What Ayappan meant if ping is working then use curl command to get the file info from the yum repo to verify if connection is fine.  Something like following

    $ curl http://server1.edc.nam.com/aixtoolbox/AIX_Toolbox/repodata/repomd.xml

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



  • 5.  RE: yum repo time out errors , repo is on prod network. prod servers works , but dev and test fails

    Posted Wed March 23, 2022 01:29 PM
    Thanks Sanket and Ayyappan . Does yum needs any ports to be opened ? Right now ping and ssh ports are blocked between Non-prod and yum server.  Please see the difference below  between production and  Dev yum client output .

    On Dev server: ( timseout  and status , I think package count is 0)
    --> yum repolist
    http://server1.edc.nam.com/aixtoolbox/AIX_Toolbox/repodata/repomd.xml: [Errno 12]
    Timeout on http://server1.edc.nam.com/aixtoolbox/AIX_Toolbox/repodata/repomd.xml: (28, 'Connection timed out after 30000 milliseconds')

    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

    on PROD server: ( No time and status shows  package count )
    --> yum repolist
    AIX_Toolbox | 2.9 kB 00:00:00
    Not using downloaded repomd.xml because it is older than what we have:
    Current : Mon Dec 6 18:42:15 2021
    Downloaded: Thu Feb 4 16:00:57 2021
    AIX_Toolbox_71 | 2.9 kB 00:00:00
    AIX_Toolbox_noarch | 2.9 kB 00:00:00
    repo id repo name status
    AIX_Toolbox AIX generic repository 3,934
    AIX_Toolbox_71 AIX 7.1 specific repository 295
    AIX_Toolbox_noarch AIX noarch repository 251
    repolist: 4,480

    ------------------------------
    Nag N
    ------------------------------



  • 6.  RE: yum repo time out errors , repo is on prod network. prod servers works , but dev and test fails

    Posted Wed March 30, 2022 09:45 AM
    If you are using http then http port needs to be open. As I said please verify with curl command if curl started working then hopefully yum will also work.

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



  • 7.  RE: yum repo time out errors , repo is on prod network. prod servers works , but dev and test fails

    Posted Wed June 29, 2022 07:31 PM

    I, too, am seeing "A remote host did not respond within the timeout period" messages from yum clients in one of my network segments (the default yum timeout value is 30 seconds, which is more than enough in my other network segments).

    If I "telnet <repository_host> 443" I am able to connect to the repository host -- but it takes nearly 5 minutes!  

    So, I added "timeout=360" to my /opt/freeware/etc/yum/yum.conf file -- but the firewall logs still show yum timing out after 30 seconds.

    What else, if anything, can I do on the client end to try to increase the timeout value (or force the yum command to keep trying for 360 seconds instead of giving up after 30)?



    ------------------------------
    Erich Wolz
    ------------------------------



  • 8.  RE: yum repo time out errors , repo is on prod network. prod servers works , but dev and test fails

    Posted Wed July 06, 2022 11:57 AM
    This is a guess based on experience with other applications:

    Can the target system (and/or your firewall) resolve the client's name? If there is anything in place to limit access, or possibly log it, you may be waiting for several serial DNS requests to time out.

    Sent from my iPad