-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
optimadeclient stuck in loading #76
Comments
Is this reproducible? If so, to understand if the issue is with the template or not, I suggest to deploy another app (e.g. on the dev machine) with a standard template. |
@giovannipizzi thanks a lot for the suggestions.
I won't say it is fully reproducible. It appears more frequently when I use less pre-heat kernel. On the dev server, since the load is not big, it rarely happened. If there is a tool to intentionally try to request the service and force it to open more kernels, we can give it a try. I think it will be also useful if we have some tool that can conduct a stress test for any dokku app. @eimrek Is that possible to have this as what the monitor server is doing now? |
Hi, could this be related to gliderlabs/herokuish#659? And also this fix might be related: Edit: regarding the stress test, yes, in principle we could use something similar as we use in the monitor server to access the app many times: https://github.com/materialscloud-org/openstack-ansible/blob/master/roles/mc_monitor_server/files/check_httpjs.py |
@eimrek thanks a lot! I think they are related. The change in Maybe @dou-du ever build the image by hand? I remember you mentioned you have updated the version? Can you confirm with it? I think to fix this, I need first figure out what is this |
We can now use python 3.8 for optimade-client which means dokku or herokuish (I need to spend some time to understand how these things work under the hood, sorry for the vagueness of the terminologies here.) is updated as mentioned at materialscloud-org/tools-optimade-client#42 |
I updated the version number from ansible. |
Indeed, just start from the latest version of the image and apply the fix to prevent the "stuck due to lack of entropy" issue. |
Thanks @ltalirz. Could you elaborate a bit on how the image |
If you just run the image with the entry point herokuish is built on top of the heroku docker image and basically does what they do (detect what kind of app the user is trying to run, install dependencies, etc.) |
Then how do I test if this change is taking effect? I just can not find where the image built by ansible task https://github.com/materialscloud-org/openstack-ansible/blob/master/roles/mc_dokku/tasks/fix-dockerfile.yml is used in the server. |
Well, if you
Well, dokku should be using this image (you may need to look at the dokku source code). In any case, you can simply look at the containers running in one of the dokku instances and see whether they are using the image |
@ltalirz thanks and sorry for the late reply, I was on vacation last week.
I did this and it is for sure not using have the
I use
I suspect the new version of dokku use the new tag point to the image, I am curious what this |
Hi @dou-du
I got following error message when I found optimadeclient is stuck in loading. There is template related information in tracklog.
The text was updated successfully, but these errors were encountered: