PxPlus User Forum

Twitter Twitter Twitter

Author Topic: SSH Conection Keep alive  (Read 3292 times)

JimGwynn

  • Member
  • **
  • Posts: 16
    • View Profile
SSH Conection Keep alive
« on: March 19, 2020, 12:00:25 PM »
All - Need some emergency help
As we have moved all of our users to home workers we are experiencing excessive timeouts
Is there anyway using the SSH connection in the client launcher to set the Putty keep alive parameters?

Thanks

Mike King

  • Diamond Member
  • *****
  • Posts: 3817
  • Mike King
    • View Profile
    • BBSysco Consulting
Re: SSH Conection Keep alive
« Reply #1 on: March 19, 2020, 12:21:18 PM »
What you can do is create a putty session and save it then instead of providing the host name to WindX provide the session name.

For example if the host is ourhost.yourdomain.com, then create a session in putty that will connect to that host and save it, for example, as myhost.  Now in the WindX SSH host name field specify myhost instead of the server name.

You can also use this to provide SSH keys and pre-define the userid/password.
Mike King
President - BBSysco Consulting
eMail: mike.king@bbsysco.com

JimGwynn

  • Member
  • **
  • Posts: 16
    • View Profile
Re: SSH Conection Keep alive
« Reply #2 on: March 19, 2020, 12:30:22 PM »
Mike - When I do that I get this message

User Override
UserID has been overridden by Session 'TEST'

JimGwynn

  • Member
  • **
  • Posts: 16
    • View Profile
Re: SSH Conection Keep alive
« Reply #3 on: March 19, 2020, 12:37:03 PM »
Here is a screen shot of my config

JimGwynn

  • Member
  • **
  • Posts: 16
    • View Profile
Re: SSH Conection Keep alive
« Reply #4 on: March 19, 2020, 12:40:10 PM »
Here is a better image

Mike King

  • Diamond Member
  • *****
  • Posts: 3817
  • Mike King
    • View Profile
    • BBSysco Consulting
Re: SSH Conection Keep alive
« Reply #5 on: March 19, 2020, 01:37:27 PM »
This is because the system will use the userid from the session definition.  Set your userid on the session and resave then don't provide a user or password on the WindX screen.
Mike King
President - BBSysco Consulting
eMail: mike.king@bbsysco.com

JimGwynn

  • Member
  • **
  • Posts: 16
    • View Profile
Re: SSH Conection Keep alive
« Reply #6 on: March 19, 2020, 04:34:55 PM »
Thanks Mike that did work

For anyone else that may have a similar issue - Here is what we found and what works

We setup SSH access through a Network Load Balancer in AWS. This NLB has a fixed session timeout of 350s

What we did to solve this was Set the +A system parameter to 1.  By default this is set to 10 min causing the NLB to timeout sessions.

With this we did not need to touch any of the the users putty settings.

Thanks Again.

Patrick Denny

  • Member
  • **
  • Posts: 9
    • View Profile
Re: SSH Conection Keep alive
« Reply #7 on: November 01, 2023, 01:48:08 PM »
@JimGwynn

I issued the command:  SET_PARAM '+A'=1
That works great for my Windx session.  I don't get the long delays waiting to reconnect the session, if the session is left inactive for a while.

I don't think that setting would automatically apply to any "*VIEWER*" windows that get launched.
I had a couple (viewer) windows that were still timing out or had a delay in reconnecting.

Were you able to solve that issue also?  How do I get the *VIEWER* windows to launch (generically) with that parameter set?

I see something in the documentation about "system parameters" in the "NOMADS" menu (Utilities, Application Parameter Configuration), but I'm not sure I understand how all that works, or if that's the correct place to put it.

I read that settings in an INI file used when stating PxPlus would also be used when launching *VIEWER* windows, but I don't see where a parameter like the '+A' parameter would be implemented in the INI file.

Otherwise, the *VIEWER* documentation (under "Special File Handling") shows 3 options, with options 2 & 3 appearing to allow passing parameters.
There's a -XT=1 reference on a command line used to launch/spawn a new pxplus session so I assume I could include a -+A=1  also?  although I tried that on my Desktop Shortcut and it didn't seem to work.  If it "should" work, it looks like I need to manage creating a unique SERIAL file and when "CLOSE"ing the serial file output using that file name in the CALL "Windx.utl;SPAWN" command.  Seems like extra "make work" vs. an OPEN()"*VIEWER*" doing it for you somehow.