2 Replies Latest reply on Sep 10, 2009 2:35 PM by S Crawford

    NSH Proxy Connection closing too quickly

    S Crawford

      For some reason, our NSH sessions are not staying alive. After starting up an NSH session, I do an 'ls' command on a server. The 'ls' command excutes, but the NSH prompt does not return (remains hung). The app server log shows these corresponding entries when I try running the 'ls' command.

       

      Admin01:BLAdmins:147.179.173.142 NSH Proxy Connection closed

      Admin01:BLAdmins:147.179.173.142 Connecting to lx-bladelogic-p2

      Admin01:BLAdmins:147.179.173.142 Connecting to lx-bladelogic-p2

      Admin01:BLAdmins:147.179.173.142 copy data stop: Connection closed

      Admin01:BLAdmins:147.179.173.142 NSH Proxy Connection closed

      Admin01:BLAdmins:147.179.173.142 Connecting to lx-bladelogic-p2

      Admin01:BLAdmins:147.179.173.142 copy data stop: Connection closed

      Admin01:BLAdmins:147.179.173.142 NSH Proxy Connection closed

       

      Are these log entries normal for an NSH session? Should the connection open and close this quickly (only staying open for the execution of the command)? The connection is closing before the 'ls' command can even finish, so the prompt doesn't reappear.

        • 1. Re: NSH Proxy Connection closing too quickly

          I can't explain the hang but what you're seeing is normal for the ls command. The ls command opens and closes a bunch of shorter lived connections. The NSH proxy will only keep a connection open until the client-side has called close on that connection so if you see a connection getting closed on the proxy it's because the client told it to (usually).

           

          For example, you'll notice if you turn on debug logging on an agent and do something simple like:

          ls ///etc

          and then look at the log entries, you'll see that the ls command opened up at least two new connections to the agent to process the ls. Depending on what's in the directory, you could get more connections as well (and also depending on the ls flags you passed in).

           

          Since a single NSH command can be used against 100s/1000s of servers in one call, we don't keep the connections open any longer then we need to otherwise you'll run out of file descriptors.

          • 2. Re: NSH Proxy Connection closing too quickly
            S Crawford

            Ok, that makes sense about why there are multiple connections. But is it possible they aren't staying opened long enough? Is there a variable in the app server settings that might be dictacting this?