BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
LucianoMachado
Fluorite | Level 6

After the Red Hat patch RHEL 7.4 our Linux Boxes, the LASR Server stopped working and wouldn't come up.

 

ERROR: A connection to the LASR Analytic Server on 'xxxxxxx.yyyy.zzzz', port 10011, could not be made. Make sure that the

       host and port are correctly specified, that you are attempting to connect to a LASR Analytic Server of the correct vintage,

       and that the server is still running.

ERROR: Libref LASRTEST is not assigned.

ERROR: Error in the LIBNAME statement.

ERROR: Could not start LASR server.  Processing cancelled.

 

In this security patch some ciphers and algorithms were deprecated in the openSSH, causing some SSH Clients to fail to authenticate.

SAS LASR uses its own ssh (tkssh) client to communicate with other nodes

 

 

[/sasbin/SASFoundation/9.4/dbcs/utilities/bin]
 ./tkssh worker01
FATAL ERROR: expected key exchange group packet from server

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
LucianoMachado
Fluorite | Level 6

To fix the issue it is necessary to tell SAS to use the OS ssh Client, by changing sasv9_local.cfg adding the following

 

-SET GRIDRSHCOMMAND "/usr/bin/ssh -q -o StrictHostKeyChecking=no"

 

[/sasbin/SASFoundation/9.4]
$ vi sasv9_local.cfg
-MEMSIZE 128G
-SORTSIZE 64G
-BUFSIZE 64K
-UBUFSIZE 64K
-IBUFSIZE 32767
-BUFNO 10
-UBUFNO 10
-IBUFNO 10
-ALIGNSASIOFILES
-SET GRIDRSHCOMMAND "/usr/bin/ssh -q -o StrictHostKeyChecking=no"

View solution in original post

2 REPLIES 2
LucianoMachado
Fluorite | Level 6

To fix the issue it is necessary to tell SAS to use the OS ssh Client, by changing sasv9_local.cfg adding the following

 

-SET GRIDRSHCOMMAND "/usr/bin/ssh -q -o StrictHostKeyChecking=no"

 

[/sasbin/SASFoundation/9.4]
$ vi sasv9_local.cfg
-MEMSIZE 128G
-SORTSIZE 64G
-BUFSIZE 64K
-UBUFSIZE 64K
-IBUFSIZE 32767
-BUFNO 10
-UBUFNO 10
-IBUFNO 10
-ALIGNSASIOFILES
-SET GRIDRSHCOMMAND "/usr/bin/ssh -q -o StrictHostKeyChecking=no"
alexal
SAS Employee

@LucianoMachado,

 

The root cause of this problem is that TKSSH is not compatible with OpenSSH that ships with RHEL 7.4. You have to use an external SSH client as you said above. I've found this problem almost immediately after the release of RHEL 7.4.

sas-innovate-2024.png

Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.

Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.

 

Register now!

Tips for filtering data sources in SAS Visual Analytics

See how to use one filter for multiple data sources by mapping your data from SAS’ Alexandria McCall.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 2 replies
  • 1944 views
  • 0 likes
  • 2 in conversation