Problem Note 67659: The launcher service log shows the error "No Qualified Launcher Servers are available to complete request. Process reaper failed to delete process..."
 |  |  |  |
After you apply the hot fixes associated with SAS Note 65966 and SAS Note 66914, the memory leaks are resolved. However, the launcher service log still shows the following error and warning messages repeatedly:
2021-01-27 15:01:23.064 ERROR 30491 --- [1-auto-1-exec-3] com.sas.commons.rest.ExceptionLog : sas.launcher [19a6f9c69d98079d] com.sas.commons.rest.exceptions.ResourceException: No qualified launcher servers are available to complete request.
2021-01-27 15:01:23.066 WARN 30491 --- [pool-6-thread-1] com.sas.launcher.process.ProcessReaper : service [fbd92a0daee2e4b4] Process reaper failed to delete process with ID "9f735b22-f97c-4302-b9e4-d196b4d24c6a":org.springframework.web.client.HttpServerErrorException$InternalServerError: 500
2021-01-27 15:01:23.066 WARN 30491 --- [pool-6-thread-1] com.sas.launcher.process.ProcessReaper : service [fbd92a0daee2e4b4] Process reaper failed to delete process with ID "9f735b22-f97c-4302-b9e4-d196b4d24c6a":org.springframework.web.client.HttpServerErrorException$InternalServerError: 500
These messages can be safely ignored.
If you are concerned about these messages and would like to suppress them, you can disable the process reaper by following these steps:
- Source the consul.conf file to add the new configuration value:
source SAS-Viya-configuration-directory/consul.conf
- Check which value is currently set for the process reaper:
/opt/sas/viya/home/bin/sas-bootstrap-config --token-file /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token kv read --recurse config/launcher/sas.launcher.process.reaper-enabled
- Write the new key-value pair to disable the process reaper:
/opt/sas/viya/home/bin/sas-bootstrap-config --token-file /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token kv write --key config/launcher/sas.launcher.process.reaper-enabled --value false
- Check that the new value is set to false:
/opt/sas/viya/home/bin/sas-bootstrap-config --token-file /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token kv read --recurse config/launcher/sas.launcher.process.reaper-enabled
config/launcher/sas.launcher.process.reaper-enabled=false
config/launcher/sas.launcher.process.reaper-enabled=false
- Restart the launcher service and launcher server:
sudo systemctl restart sas-viya-runlauncher-default
sudo systemctl restart sas-viya-launcher-default
A fix for this issue is planned for a future software release.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Viya | Linux for x64 | 3.5 | Viya | ||
After you apply the most recent launcher hot fixes, the launcher service log still shows errors and warnings even though there are no issue occurring in the environment.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2021-03-26 14:40:11 |
| Date Created: | 2021-03-25 15:27:41 |