The SAS Viya operations agent might repeatedly log the following messages.

• In the sas-ops-agent_*.log file that resides in /opt/sas/viya/config/var/log/ops-agent/default/sas-ops-agent_*.log:

• In the sas-ops-agentsrv_*.log file that resides in /opt/sas/viya/config/var/log/ops-agentsrv/default/sas-ops-agentsrv_*.log:

This problem occurs when either /tmp/agent.pipes/ops-agent.command.fifo or /tmp/agent.pipes/ops-agentsrv.command.fifo is deleted. The problem can happen when an automated process cleans the /tmp directory. Examples of the automated process include tmpwatch in Red Hat Enterprise Linux 6 or systemd-tmpfiles in Red Hat Enterprise Linux 7.

After the problem occurs, the operations-agent command cannot communicate with the operations-agent server until the server is restarted. The deletion of these files from /tmp does not impact the scheduling of tasks such as the extract, transform, and load (ETL) driver or ev-genAudit. The operations-agent command, ops-agent-cmd, is new in SAS Viya 3.5. So, this issue impacts only the 3.5 release.

One way to work around this problem is as follows: 

1. Create /etc/tmpfiles.d/sasagentpipes.conf and include this line in the sasagentpipes.conf file:
   x /tmp/agent.pipes
2. Restart these services on any machine where they exist:
   • sas-viya-ops-agentsrv-default
   • sas-viya-ops-agent-default

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

Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at