System Evaluation Report
busas.binghamton.edu
Total Issues:
1
System Details:
- SASHome: /opt/sasinside/sashome
- SAS Config Directory: /opt/sasinside/config/metadata/Lev1
- Accessible Files in SAS Config Directory: 4479
- Non-Accessible Files in SAS Config Directory: 0
- Operating System: Linux
- CPU(s): 32
- Thread(s) per core: 2
- Core(s) per socket: 8
- CPU Socket(s):
- NUMA Node(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30
- Kernel Name: Linux
- Kernel Release: 5.4.17-2136.317.5.3.el7uek.x86_64
- Kernel Version: #2 SMP Thu Mar 16 19:26:27 PDT 2023
- System Locale: en_US.utf8
- Total System Memory: 528338492 kB
- Available System Memory: 339416088 kB
Helpful Links
- Please contact SAS Technical Support about any issues requiring further assistance.
- See Supported Operating Systems if you are planning to adopt the latest version of SAS 9.4 and verify that your operating system version is supported.
- See Removing a SAS Configuration for more information on how to unconfigure SAS software.
- See Perform an Update in Place for more information about cleaning out the staging area for clustered SAS Web Application Servers.
- See Upgrading postgreSQL for information about tuning the SAS Web Infrastructure Platform Data Server.
- See Password Policy for guidelines on valid characters for passwords for the SAS Web Infrastructure Platform Data Server.
- See Understanding SAS Web Application Server Configuration for more information about SAS Web Application Server configuration.
- See Understand the Cache Locator Configuration for more information about Cache Locator configuration.
- See SAS Note 65629 for more information about Cache Locator issues.
System Evaluation Summary
| Task | Status | Code | Comments | Message |
|---|---|---|---|---|
| Archiving results directory |  Success |
|||
| Validating all SAS software orders | Success |
|||
| Processing configuration.properties | Success |
|||
| Validating settings for the configuration directory | Success |
|||
| Enumerating the files in the specified SAS configuration directory | Success |
|||
| Verifying all the files in the specified SAS configuration directory are accessible | Success |
|||
| Validating that the specified configuration directory is not shared improperly | Success |
|||
| Processing the SAS Deployment Registry | Success |
|||
| Searching for any retired products | Success |
|||
| Searching for any retired products that require SAS Technical Support assessment | Success |
|||
| Checking for the existence of SAS Federation Server Manager 4.1 | Success |
|||
| Validating the host name | Success |
|||
| Initializing evaluation directories | Success |
|||
| Determining and validating the last SAS software order | Success |
|||
| Validating the dependent SAS metadata components: Is LevDirRoot Empty? | Success |
|||
| Validating the dependent SAS metadata components: Are items only in metadata associated with the specified SAS configuration directory? | Success |
|||
| Validating the dependent SAS metadata components: Are items in status.xml and not in metadata associated with the specified SAS configuration directory? | Success |
|||
| Validating the dependent SAS metadata components: Are items only in status.xml? | Success |
|||
| Evaluating the configuration logs |  Issues Found |
SAS9CASE-LOGCHCK | There are no logs present in /opt/sasinside/config/metadata/Lev1/Logs/Configure. | There are no logs present in /opt/sasinside/config/metadata/Lev1/Logs/Configure. This is unusual as logs should exist. Please contact SAS Technical Support for further assistance. |
| Processing metadata.connection.properties | Success |
|||
| Processing metadataConfig.xml | Success |
|||
| Evaluating software and server components | Success |
|||
| Validating the dependent SAS metadata components | Success |
|||
| Obtaining SAS Metadata Repository information | Success |
|||
| Evaluating SAS Metadata topology | Success |
|||
| Checking for the existence of SAS Model Implementation Platform Server Configuration 3.1 | Success |
|||
| Validating JVM_OPTS specifications in SAS web servers and SAS web application servers | Success |
|||
| Determining the maximum number of connections for the SAS Web Infrastructure Platform Data Server | Success |
|||
| Verifying that the maximum number of connections is equal to the maximum number of prepared transactions for the SAS Web Infrastructure Platform Data Server. | Success |
|||
| Determining the maximum number of prepared transactions for the SAS Web Infrastructure Platform Data Server | Success |
|||
| Validating specified Java usage with SAS Foundation | Success |
|||
| Checking if the credentials for SAS Remote Deployment Agent 2.1 need to regenerated. | Success |
|||
| Detecting if SAS Remote Services exists and is running. | Success |
|||
| Verifying that there are no incomplete SAS deployments on this system | Success |
|||
| Validating the date-time stamps for SAS executables | Success |
|||
| Validating the SAS Private JRE installed correctly. | Success |
|||
| Validating there is only one version of the SAS Private JRE installed. | Success |
|||
| Validating the SAS license | Success |
|||
| Determining SASLogon externalization status | Success |
|||
| Evaluating the SAS Content Server | Success |
|||
| Obtaining SAS setinit information | Success |
|||
| Processing status.xml | Success |
|||
| Collecting and collating additional information | Success |
|||
| Determining system characteristics | Success |
|||
| Verifying that /tmp is not mounted with -noexec | Success |
|||
| Validating required user input | Success |
|||
| Evaluating SAS web applications | Success |
|||
| Validating the SAS web application servers | Success |
|||
| Evaluating SAS Web Application Server clustering status. | Success |
|||
| Checking for occurrences of com.sas.appserver.utils.ResourceManagerImpl in appserver.properties | Success |
|||
| Determining the SAS mid-tier connection information | Success |