An issue can occur where the SAS LASR Analytic Server Monitor service might report a successful start, but the service never actually runs. After a few minutes, the SAS LASR Analytic Server Monitor service reports a status of "not started". Repeat attempts to start the service result in the same behavior loop. In addition, the SAS LASR Analytic Server Monitor log file displays a java.io.IOException error and instructs the administrator to check SSH key configurations.
This issue might be caused by SSH key configurations, as the error message advises. However, this issue might also be caused by missing system libraries that the tkgridmon binary uses, which SAS Grid Broker invokes, and is triggered by the SAS LASR Analytic Server Monitor start-up processes.
The required system library versions are no longer available on various modern UNIX operating system versions. If these system libraries are not available, the SAS LASR Analytic Server Monitor is unable to start its dependent processes. As a result, the time-outs and behavior noted above occur. (No error is displayed or logged to make this condition known.)
Impacted operating system versions include the following:
The behavior described in the Summary section might have multiple causes. These symptoms could appear when you launch the SAS LASR Analytic Server Monitor from its control script (LASRMonitor.sh) or the init.d service (sas.lasrmonitor).
Please contact SAS Technical Support if you are unable to determine the exact cause from the information below, or if the conditions designated for the causes below do not match those that occur on your system.
Before you implement the workarounds outlined in this article, it is important to verify that Passwordless-SSH configuration works correctly across your distributed LASR nodes. The error message in the log indicates that the cause is due to incorrect Passwordless-SSH configuration, which would result in the described behavior. Every host and machine in the SAS® High-Performance Analytics environment must be able to connect to all others via SSH without a password, including SSH connections to itself.
See SAS KB0036303 for instructions about how to verify the Passwordless-SSH configuration requirements.
After verifying the Passwordless-SSH configuration, complete all additional debugging and resolution tasks noted in this article on the LASR controller machine. (This is the machine where you launch the SAS LASR Analytic Server Monitor.)
Check the log file that the SAS LASR Analytic Server Monitor uses, which is located at <SAS-configuration-directory>/LevN/Applications/SASVisualAnalytics/HighPerformanceConfiguration/Logs/
server_<date>.log. Looping messages might occur regarding the ServerSocket opening a port, followed by attempts to launch tkgridmon on that port.
These messages would look similar to the following:
[NOTE@2026-06-18 08:14:20.096] SAS Grid Broker initialization is complete.
[NOTE@2026-06-18 08:14:20.147] ServerSocket open on 43423
[NOTE@2026-06-18 08:14:20.148] ServerSocket timeout is 5000
[NOTE@2026-06-18 08:14:20.148] Executing [/opt/SASHome/SASFoundation/9.4/utilities/bin/tkgridmon, -showranks, -quiet, -nousers, -guiport, 43423]
[NOTE@2026-06-18 08:14:25.154] Restarting the monitoring service.
[NOTE@2026-06-18 08:14:25.155] ServerSocket open on 33565
[NOTE@2026-06-18 08:14:25.155] ServerSocket timeout is 5000
[NOTE@2026-06-18 08:14:25.155] Executing [/opt/SASHome/SASFoundation/9.4/utilities/bin/tkgridmon, -showranks, -quiet, -nousers, -guiport, 33565]
[NOTE@2026-06-18 08:14:30.157] Restarting the monitoring service.
<similar log messages continue to repeat for some time>
[EXCEPTION@2026-06-18 13:22:28.826] NODE="hostname.sas.com" - class java.io.IOException java.io.IOException at com.sas.grid.broker.monitor.ConnectionManager.startTKGridMon(ConnectionManager.
java:248) at com.sas.grid.broker.core.BrokerCore.main(BrokerCore.java:267)
[ERROR@2026-06-18 13:22:28.827] Monitor thread failed to start due to configuration errors.
[ERROR@2026-06-18 13:22:28.828] No I/O produced by the grid monitor, check your SSH key configuration.
The log messages above show that the tkgridmon binary does not successfully initialize within the time-out interval displayed (default: five seconds). As a result, the process enters a restart loop. However, at this point, you have determined that the final error message about checking the SSH key configuration is not an accurate diagnosis (as you should have already verified that the SSH configuration is correct).
You should check the actual start-up tkgridmon issue by attempting to manually invoke it. To do so, try to launch the program located at /<SAS-home-directory>/SASFoundation/9.4/utilities/bin/tkgridmon in a terminal window. An error message similar to the following likely occurs:
./tkgridmon: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
If you have verified the following, then the condition caused by missing system libraries is likely the issue:
The following required system libraries are typically missing:
See the Workaround section for information about how to resolve this issue and enable the SAS LASR Analytic Server Monitor to run properly.
This method is a resolution that directly implements the expected system library versions. If applicable, it is the preferred method to address the behavior outlined in this article.
However, this method applies to only certain operating system versions, as the system libraries expected are legacy releases. These system library versions are no longer distributed by vendors for the latest operating system versions supported by SAS 9.4 (such as Red Hat Enterprise Linux 9.x+, Oracle Enterprise Linux 9.x+, and so on).
If you are unable to locate the legacy system library versions in your operating system's repositories, or are unsure how to do so, see Method 2.
To install the legacy system library versions required, you need to install the ncurses-compat-libs package (sometimes also called the libncurses5 package) using the system's repository manager. See your operating system vendor for specific command guidance where applicable.
Here are some examples for reference:
Red Hat Enterprise Linux 8.x
sudo dnf install ncurses-compat-libs
SUSE Enterprise Linux Server 12
sudo zypper install libncurses5ll libncurses5
This method is a workaround that should be available on all impacted operating system versions.
The impacted tkgridmon binary has been found to be capable of running with the newer libncurses.so.6+ and libtinfo.so.6+ versions (delivered by default on newer Operating System releases), but is not aware of the system library by that newer version's name. If you create a symbolic link with the name of the expected versions and point to the new versions that are already available on the system, tkgridmon will likely be able to start. This workaround should permit the SAS LASR Analytic Server Monitor to run continuously.
Complete the following steps to configure the required symbolic links:
1. Determine the existing libncurses and libtinfo system library versions using the commands below.
Note the non-symlink file shown in outputs of (b) and (c). This is the file that does not have "l" at the beginning of the listing, and also the file that does not display an arrow "->" to another file in the listing. In addition, if you do not see any output from (b) and (c) commands, check that the system library directory on your system matches that shown in (a).
a) Navigate to the system library directory: cd /usr/lib64
b) Display the libncurses system library versions that are installed: ls -la | grep libncurses
c) Display the libtinfo system library versions that are installed: ls -la | grep libtinfo
2. Create symlinks to the files identified in step 1, using the names of the versions expected by the tkgridmon binary.
Note that the examples below were from a Red Hat Enterprise Linux 9.8 system, which contained version 6.2 of the system libraries. It is critical that you check the versions available on your system using the commands in step 1, as they vary between operating system releases. Errors will persist if you create symlinks to a version of the system library that is not actually installed on your operating system.
a) Create symlink for libncurses: sudo ln -sf libncurses.so.6.2 libncurses.so.5
b) Create symlink for libtinfo: sudo ln -sf libtinfo.so.6.2 libtinfo.so.5
After you complete either Method 1's or Method 2's workaround, the SAS LASR Analytic Server Monitor service should continue to run (for more than the ~five minutes that it would attempt to restart tkgridmon before previously reporting an error and stopping the service).
If a stopped SAS LASR Analytic Server Monitor still occurs after some time, contact SAS Technical Support for further diagnosis.