1 2 Previous Next 17 Replies Latest reply on Mar 9, 2016 2:36 PM by Yanick Girouard

    Why does "cd" command fail after an NSH connection experiences [Error on socket: 'Connection reset by peer'] yet all other NSH commands continue to work?

      Why does "cd" command fail after an NSH connection experiences [Error on socket: 'Connection reset by peer'] yet all other NSH commands continue to work?

       

      I'm running BMC BladeLogic Server Automation Console Version: 8.6.01.66 using SRP AuthenticationType.
      From BSA console, I right-click on a server object | Run Custom Command | NSH Here.

       

      Straight after login to a remote host
      ===========================
      Note how "cd" command works normally.


      <remote host>% cd var
      <remote host>% pwd
      //<remote host>/var
      <remote host>%

       


      After NSH login has been left idle for 4-5 minutes
      =====================================
      If I leave NSH session idle for 4-5 minutes then a time-out occurs (Error on socket: 'Connection reset by peer').
      After that event it now thinks "cd: is a directory:"


      <remote host>% cd /
      SSL_write (Error on socket: 'Connection reset by peer')
      SSL_write
      SSL_write (Error on socket: 'Connection reset by peer')
      SSL_write
      cd: is a directory: /

       


      If you continue with the NSH session then "cd" cannot be used
      ================================================
      Thereafter, anytime I run 'cd' command I get 4 "SSL_write" responses and "cd: no such file or directory:". This fault happens for any O/S (Solaris, Linux, HP UX, Windows) running various RSCD Agent versions (such as 8.2.3.416; 8.2.1.273, 8.0.11.1107). All other NSH commands I try continue to work normally (e.g. cp, mkdir, rmdir, pwd).

       

      //<remote host>/
      <remote host>% cd /var
      SSL_write
      SSL_write
      SSL_write
      SSL_write
      cd: no such file or directory: /var
      <remote host>%

       


      Questions
      =========

      1. How can I increase the time-out setting for idle NSH connections? What can be done at the client end (preferred)? What can be done at the BSA server end?

       

      2. Can I configure anything to stop "cd" being interpreted as a directory after (Error on socket: 'Connection reset by peer') event? Alternatively, once that happens is there a way I can recover it without having to close and reopen the session?

       

      3. Can BMC provide a patch? We are running BSA 8.6 SP1.

        1 2 Previous Next