503 Service Temporarily Unavailable after using SaS Viya Start/Stop

[aasadi]

Hi SAS Support Team,

I deployed SAS Viya (Pay-As-You-Go) on our Azure account, and everything was working fine until I started using the "sas-viya-automation | Start/Stop" service. After attempting to start the service from the last stopped state, I began receiving a "503 Service Temporarily Unavailable" message when trying to access the application.

Could you please help me understand what might be causing this issue and how I can resolve it?

Thank you!

Best regards,

Alireza

[priyhat_sas]

After you started Viya, it may take a few minutes to get it up and running. Please let us know if you still get 503s after 5 minutes or so, and any logs from the failures. Thanks.

[aasadi]

It has been more than 4 hours since the StartStopViya job completed, and there are no errors in the logs. However, we have two warnings related to upcoming breaking changes in the cmdlet and the Azure version which I think it should not be relevant to the issue we are experiencing. 

[aasadi]

After trying the runbook multiple times on different days, I was finally able to log in to the application. I'm not sure what caused the issue or how it was resolved, but Start/Stop Scheduler is working now.

[DataCruncherX]

This often happens if some Viya services don’t restart properly. Try checking the service logs or use the sas-viya status command to confirm all services are up.

[aasadi]

It seems this issue is coming and going intermittently. I checked our activity log, and there are no major errors or warnings. I’d like to see if anything is happening behind the scenes—such as deployments or updates—that might be causing the issue. Thanks!

[josevalenzuela]

Hi I have had the same issue sometimes, but since yesterday there is no way to have it running.

We have scheduled a job to start and stop the instance during office hours but since yesterday it only shows the 503 error.

I can access to the keycloak but anything else. And I cannot do nothing as is an administrated application and it give me permissions errors if I want to check kubernetes logs and everything.

Any advice about how can I check where the error comes from?

Thanks in advance.