When you attempt to start SAS^® Viya^® 3.5, the SAS Infrastructure Data Server (sas-viya-sasdatasvrc-postgres-node#) or PGPool (sas-viya-sasdatasvrc-postgres-pgpool#) might fail to start. These applications do not keep attempting to start if Consul is down. This issue might occur if Consul is not given enough time to completely start.

Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.

When you apply this hot fix, the following happens:

• An attempt to connect to Consul is made. If Consul is unavailable, the microservice goes into a wait state and this is logged as a failed initial connection attempt.
• A connection retry is made every three seconds.
• For every one minute that passes without a successful connection to Consul, one log entry is made for the failure.
• If after 30 minutes the microservice still cannot connect to Consul, the microservice completely fails and an error message stating the failure is logged.
• If at any point the microservice is able to connect to Consul, a successful connection message is logged and no further attempt to connect is made.

Operating System and Release Information

Viya on Windows: 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 Windows Deployment Guide at

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