LEDfan
commented
3 years ago Hi
ShinyProxy does not keep applications indefinitely running, so it's not really possible to use healthcheck on them. If the application is not used (e.g. because the user logged out or closed the tab), ShinyProxy removes the app and thus also the underlying pod.
Can you provide the full stack trace of the error message you get? Usually there is some more information in there on what is causing the error. I guess it's better to solve that issue then trying to apply health checks.
Hello Team,
I would successfully deploy Shiny Proxy on Kubernetes. Thanks for your great help and valuable advice to get me here. I have 7 Shiny applications run under proxy and all works well, but i am experiencing an issue like, if i do not use this application in 1 or 2 days and later i tried to access, the proxy page says:
Error Status code: 500 Message: Failed to start the container
Hence i thought we can set up a health check on the Kubernetes side. i need your help to understand how Proxy calls applications, so that i can write a script to call the application every hour and check the application is live or not.
For example, my endpoint in Browser would be http://aplambosd001:30085/app/Shiny_TMA in the application.yaml file i specified session like this:
proxy: title: Open Analytics Shiny Proxy logo-url: https://www.openanalytics.eu/shinyproxy/logo.png port: 8080
specs:
i have gone through Doc - https://shinyproxy.io/documentation/deployment/#readiness-and-liveness-probes but i am not sure how they call HTTP endpoint from Proxy - path: /actuator/health/liveness
Could you provide me some light to make this implement.
Thank you.