Problem Note 63185: The error "Could not find/write expected config file" occurs in the SAS® Environment Manager log viewer for SAS® Viya® and in the ops-arm.log file
 |  |  |  |  |
The ops-arm.log file (located in the /opt/sas/viya/config/var/log/evmsvrops/default directory) and the SAS Environment Manager log viewer for SAS Viya might contain errors similar to the following:
2018-08-11T12:41:54.985842-04:00 ERROR [] [ops-arm] - /opt/sas/viya/config/etc/sysconfig/compsrv/default/sas-compsrv
2018-08-11T12:41:54.985842-04:00 ERROR [] [ops-arm] - Server batchserver, Could not find/write expected config file,
2018-08-11T12:41:54.985842-04:00 ERROR [] [ops-arm] - /opt/sas/viya/config/etc/sysconfig/batchserver/default/sas-batchserver
2018-08-11T12:41:54.985842-04:00 ERROR [] [ops-arm] - Server connectserver, Could not find/write expected config file,
2018-08-11T12:41:54.985842-04:00 ERROR [] [ops-arm] - /opt/sas/viya/config/etc/sysconfig/connectserver/default/sas-connectserver
2018-08-11T12:41:54.985842-04:00 ERROR [] [ops-arm] - Server workspaceserver, Could not find/write expected config file,
2018-08-11T12:41:54.985842-04:00 ERROR [] [ops-arm] - /opt/sas/viya/config/etc/sysconfig/workspaceserver/default/sas-workspaceserver
These errors can be safely ignored if both of these conditions are true:
- You use a multi-node deployment.
- The services that are described in the errors (compsrv, batchserver, connectserver, and workspaceserver) are not deployed on the node where the agent reports the errors.
Example
A multi-node deployment has all SAS Viya services and the SAS® Cloud Analytic Services (CAS) controller on node0. Only the CAS workers are on node1, node2, and node3. The ops-arm.log file and log viewer both show “Could not find/write expected config file” errors on node1, node2, and node3.
The errors on node1, node2, and node3 can be safely ignored because in this example the services that the agent is looking for (compsrv, batchserver, connectserver, and workspaceserver) are deployed only on node0.
However, in this example, if the errors occurred on node0, you would investigate the errors, because node0 is where the services are deployed.
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
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.4 | |||
Viya on Linux: An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Linux Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.4&softwareContextId=softwareUpdatesAn update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Windows Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.4&softwareContextId=softwareUpdatesWinViya on Windows: An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Windows Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.4&softwareContextId=softwareUpdatesWinAn update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Linux Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.4&softwareContextId=softwareUpdates| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2019-02-28 08:36:19 |
| Date Created: | 2018-11-07 10:59:31 |