BookmarkSubscribeRSS Feed
HemanthMG
Fluorite | Level 6

Hi Folks,

 

I hope you're all doing well. I wanted to reach out for some assistance with a recurring issue we've been experiencing with SAS Viya Studio sessions terminating unexpectedly. Upon investigation, I noticed that some compute pods were showing a terminating state in Pods, and I was unable to collect the logs. I tried to locate the viya.logs in the SAS directory at "/var/log/sas/viya.log", but unfortunately, I couldn't find them. Has anyone else encountered this problem before? If so, could you please share any steps or solutions that could help us resolve this issue?

 

Any help or guidance would be greatly appreciated.

 

Thank you in advance for your assistance.

 

HemanthMG_2-1731426579689.png

 

 

HemanthMG_3-1731426637250.png

 

 

Regards ,

Hemanth MG 

3 REPLIES 3
gwootton
SAS Super FREQ
Hi Hemanth,
Kubernetes pods typically do not write logs to files but to the output streams stdout and stderr. While the pod is running, these can be retrieved with the kubectl logs command.

If the pod is terminating on startup and you can't capture the log before the pod goes away, you'd need a solution like viya4-monitoring-kubernetes deployed, which persists logs from the pods in an OpenSearch database.

https://github.com/sassoftware/viya4-monitoring-kubernetes
--
Greg Wootton | Principal Systems Technical Support Engineer
HemanthMG
Fluorite | Level 6

@gwootton - Thanks for your quick response !!

 

We haven't set up viya4-monitoring-kubernetes in our environment.  Is there any other way to view logs or fix this studio issue? 

 

 

 

Thanks,

Hemanth MG 

gwootton
SAS Super FREQ
The screenshot shows the pod terminating after 44 seconds, so it is unlikely to be a timeout issue and more likely an error being encountered by the pod when it starts. You can check the Kubernetes event log (kubectl get events) for any references to that pod, but if the failure is due to a FATAL error in the compute server pod and if you do not have any logging solution to persist logs, you would need to catch the pod while it still exists in the terminating state by running kubectl logs pod-name to see what error is being encountered by the pod causing it to terminate.
--
Greg Wootton | Principal Systems Technical Support Engineer

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 457 views
  • 1 like
  • 2 in conversation