Supporting the Monitoring Features

Introduction
Network Name Resolution
Managing the Monitoring Server
Commands
Requirement: Passwordless SSH
Logging for the Monitoring Server

Introduction

Note: This topic is applicable to only distributed servers.
Features that depend on the monitoring server (SAS LASR Analytic Server Monitor) include the following:
  • table details about the Process Monitor tab
  • per-instance memory gauges on the LASR Servers tab
  • certain information about the HDFS tab

Network Name Resolution

Successful functioning of the monitoring server requires network name resolution on the middle-tier machine.
Insufficient network name resolution can cause a log entry such as the following:
Exception caught in LASRClient (lasr=null, host=hostname, port=nnnn)
java.net.UnknownHostException: hostname
action=TableInfo
The log entry is written to the bihpgrdc.monitor.console.log file, which is in the SAS configuration directory at /Applications/SASVisualAnalytics/HighPerformanceConfiguration/Logs.
The host name that the log entry references requires name resolution on the middle-tier machine. You can alias the host name to the IP address for the grid host that is used for the SAS LASR Analytic Server.

Managing the Monitoring Server

Commands

Use the following commands to manage the process that monitors a distributed server:
UNIX:
 
LASRMonitor.sh
 
start | stop | restart | status
Windows:
 
LASRMonitor.bat
 
start | stop | restart | status | pause |resume
The script is in the SAS configuration directory under /Applications/SASVisualAnalytics/HighPerformanceConfiguration.
Note: On Windows, the monitoring process runs as a service (for example, SAS [config-Lev1] LASR Analytic Server Monitor). You can manage the process using the Windows Services interface.

Requirement: Passwordless SSH

The monitoring process account must have passwordless SSH access to all machines on the cluster.
To provide passwordless SSH access to a monitoring process that runs on Windows:
  1. Determine which Windows account the service runs as. Here are sample instructions:
    1. Select Startthen selectControl Panelthen selectAdministrative Toolsthen selectServices.
    2. Right-click on the service, and select Properties.
    3. On the Log On tab, next to the This account radio button, note the user ID.
  2. Make sure that the following requirements are met:
    • The account must have a copy of the SSH keys that belong to a corresponding UNIX account on the distributed server. See the section about Windows clients in Passwordless SSH in the SAS LASR Analytic Server: Reference Guide.
    • In the HighPerformanceConfiguration\wrapper\LASRMonitor.conf file, the set.USERNAME field must specify the user name of the corresponding UNIX account.

Logging for the Monitoring Server

Note: Changes to logging should be made only under the direction of SAS Technical Support.
Generated logs are in the SAS configuration directory under /Applications/SASVisualAnalytics/HighPerformanceConfiguration/Logs.
The following log excerpt indicates that the account that attempted to start the monitoring server is not configured correctly for passwordless SSH: 
NOTE: Unable to enumerate grid.
java.io.IOException
        at com.sas.grid.broker.monitor.ConnectionManager.startTKGridMon(
ConnectionManager.java:228)
        at com.sas.grid.broker.core.BrokerCore.main(BrokerCore.java:257)
ERROR: ERROR: Monitor thread failed to start.
Copyright © SAS Institute Inc. All Rights Reserved.
Last updated: December 18, 2018