BookmarkSubscribeRSS Feed
paul-blu
Fluorite | Level 6

Yesterday, our SAS Viya cluster on Azure randomly started having 500 Internal Server Errors, so we decided to restart the instance to try to fix it. Now, the "Start" command succeeds, but we just get 503 from the SAS Viya URL. Unfortunately, I don't even know where to start to debug what the issue is because I just get permission denied errors everywhere in Azure. Below is a screenshot of our AKS monitoring results, which is pretty much the only thing we have access to view.

 

Screenshot 2026-01-06 at 10.52.06 AM.png

 

Our entire production system is down because of this, help would be greatly appreciated!

5 REPLIES 5
SASKiwi
PROC Star

Are you using Azure Marketplace or just "normal" Azure? With normal Azure and the standard SAS licensing agreeement opening a SAS Tech Support track is your best option. 

paul-blu
Fluorite | Level 6
We are using Azure Marketplace Pay-as-you-Go. We don't have the standard SAS licensing agreement.
paul-blu
Fluorite | Level 6

That's why I posted in this forum

 

 

Screenshot 2026-01-06 at 3.36.29 PM.png

cj_blake
SAS Employee

Note for all - @paul-blu shared the Azure subscription and Managed Application details for his Pay-as-you-Go Viya instance privately with me and we were able to get the system back up and running for him. The issue was that the Viya Postgres database had run out of space.