Closed WalterFann closed 5 years ago
When this happens, it's like the controller crashed - there is a PR #155 to fix the forever part that you could try from @Juice10.
Can you check the controller logs in your tmp folder and post any errors that are logged there?
tried adding "wait-for-docker-compose-up" manually, yet got some bugs:
/bin/sh: 5: function: not found /bin/sh: 7: Syntax error: ";" unexpected Makefile:266: recipe for target 'wait-for-docker-compose-up' failed
could you please commit the verified changes?
I just pushed a fix, feel free to merge, should work now.
Thank you so much, it finally works. And the reason it didn't work is probably not the script itself. Here is what I did. I created an EC2 server with only one vCPU. And I "make quick-start" with default configuration. I checked the log and found the limitation of CPU might cause the problem. So I created another one with multiple vCPUs, also pulled the latest version, and it worked. Thank you again, I have been stuck for days.
Glad you’re unstuck. Sorry it took a bit of time.
Hi, I'm getting this exact same issue since Mon Dec 9th 2019 (may have started sooner but was fine on Fri Dec 6th 2019). Was there any updates to the docker images that perhaps broken it once again?
Hi, even I am facing the same since 9th Dec Morning. I believe some changes in the image has triggered this behavior.
Hi, I'm also facing the same issue and haven't been able to find a workaround. My system: Linux: 5.4.2-1 Distro: Manjaro KDE OpenWhisk Devtools: git master Python: 3.8 OpenJDK: 13 Docker: 19.03.5-ce docker-compose: 1.24.1
I had to wipe my drive and set it all up again two weeks ago, after which I couldn't get OpenWhisk to run anymore.
@VaguelySerious
Could you share the controller logs?
Generally, it would be located under ~/tmp/openwhisk/controller/logs/
@style95 I've searched through my past actions and it seems the original problem got resolved after I deleted all docker containers and images and reinstalled docker. For others with this problem, this might help. I did this before I got a chance to send the logs. Still not sure what the actual cause was.
@VaguelySerious ok. So are you still facing the issue or not? Would it be ok to keep this issue closed?
@style95 I'm not facing this issue anymore. You can keep it closed.
downloaded the latest version, still got this result.