The deployment is always successful, I get to use the app normally every day, but every morning on the next day I find the error messages and need to reboot the app, which fixes the issue for the whole day until I find the error again on the following day.
The last error message suggests I should know what the error is, but I don’t. Can I run the error checks myself and find out what the error is?
What I get in the ‘Manage app’ logs:
[05:06:19] The service has encountered an error while checking the health of the Streamlit app: Get “http://localhost:8501/script-health-check”: EOF
[05:07:52] Streamlit server consistently failed status checks
[05:07:52] Please fix the errors, push an update to the git repo, or reboot the app.
Hey @Caroline, the project is private since it contains sensitive data. Would it be possible to instruct me on performing a health check? If that’s not an option, sure I could temporarily share the access privately with you. Does that work?
This sounds like it might be a resource issue (apps are limited to 1GB) – if you can share the app link I can check the resource usage (I don’t need view access to the app to do so)
The limit for apps on Community Cloud is 1 GB, so it seems pretty likely that the resource limit is the cause of the error you’re seeing. Check out our blog post on reducing your app’s resource usage here.
If your app is used by an educational or nonprofit organization, you can request increased resources here.
With a limit of 1GB, how are the chart’s values always above 2GB ?
Is it possible to find out the cause of peaks in resource usage that lead to crashing? considering they happen in periods of inactivity, since I have never experienced it crashing while using it.
Each app is guaranteed 1 GB of memory, but you usually won’t see a resource-related error until you get closer to 3 GB of memory.
Unfortunately I don’t have visibility into what’s causing the higher resource usage for your app (especially since it’s private), but I’d recommend checking out that blog post I linked above, as well as our docs on caching.
I see. Thanks @Caroline, I will try using psrecord to track memory usage. Do you know if it’s possible to use it on the community cloud? Since the steps mentioned on the post only consider testing out on localhost.
Also, do you find it strange that the memory crashes often happen during the app’s inactive periods? Or is this normal, based on your experience?
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Performance cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
Functional cookies
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
Targeting cookies
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.