AIX

 View Only

  • 1.  ssh: Resource temporarily unavailable

    Posted Fri February 28, 2025 12:59 AM
    Reply

    Hi All. I have a question about one of my servers. 

    I have been having issues with running backups on one of my servers as it keeps failing due to SSH but at some point, it connects without me doing anything at all

    See below.

    [pqaWASCPS02] / #
    [pqaWASCPS02] / # ssh -vvv s2029809@brktsmap03
    OpenSSH_8.1p1, OpenSSL 1.0.2u  20 Dec 2019
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: init_func_ptrs success
    debug1: Value of krb5 is 1
    debug1: Value of gssapi is 1
    debug2: resolving "brktsmap03" port 22
    debug2: ssh_connect_direct
    debug1: Connecting to brktsmap03 [10.30.6.55] port 22.
    debug1: connect to address 10.30.6.55 port 22: Resource temporarily unavailable
    ssh: connect to host brktsmap03 port 22: Resource temporarily unavailable
    [pqaWASCPS02] / #



    ------------------------------
    Theophelous Mbokazi
    ------------------------------


  • 2.  RE: ssh: Resource temporarily unavailable

    Posted Fri February 28, 2025 01:45 AM
    Reply

    Hi,

    There seems to be old version of openssh, openssl installed in this system which we no longer support.

    openssh is at 8.1 and openssl is at 1.0.2 version

    Is it possible to update to supported versions, openssh to 9.7 and openssl to 3.0.15 from AIX web download pack ? 

    Links to download and install

    https://www.ibm.com/resources/mrs/assets?source=aixbp&S_PKG=openssl
    https://www.ibm.com/resources/mrs/assets?source=aixbp&S_PKG=openssh

    Thanks



    ------------------------------
    Sandeep Umesh
    ------------------------------

    Original Message


  • 3.  RE: ssh: Resource temporarily unavailable

    Posted 12 days ago
    Reply

    Hi Sandeep.

    Thanks a lot for the prompt response.

    I have taken the box to the highest level of SSH and OPENSSL but still didn't work as it was supposed to but while still at that, at some point it worked without me doing anything at all. Later we then realized that the box had too many established connections which left the system with no free ports to establish newer connections. On our troubleshooting we find out that most of the sockets were held by WAS processes and just by restarting WAS JVMs all connection was back to normal.

    Thanks again. 



    ------------------------------
    Theophelous Mbokazi
    ------------------------------

    Original Message