Open buchireddy opened 8 years ago
Looks like the real problem is that the controllers cannot be reached through HAproxy. That causes curl to try retrieve that nonsensical URL.
Yes, this failure is very late in the game so I'm curious to know what was wrong with the HAProxy setup. In theory it should be exactly the same as mine at home!
On Fri, Nov 4, 2016 at 11:51 AM, jomagam notifications@github.com wrote:
Looks like the real problem is that the controllers cannot be reached through HAproxy. That causes curl to try retrieve that nonsensical URL.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ianmiell/shutit-k8s-the-hard-way/issues/2#issuecomment-258412285, or mute the thread https://github.com/notifications/unsubscribe-auth/AGrczROnMlWYsUTdbYtqOLHnx4Jumn-Zks5q6xxGgaJpZM4KpCeA .
My book on Docker in Practice: Get 39% off with the code 39miell http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62
Can you log onto the lb and cat out the haproxy config?
On Fri, Nov 4, 2016 at 12:01 PM, Ian Miell ian.miell@gmail.com wrote:
Yes, this failure is very late in the game so I'm curious to know what was wrong with the HAProxy setup. In theory it should be exactly the same as mine at home!
On Fri, Nov 4, 2016 at 11:51 AM, jomagam notifications@github.com wrote:
Looks like the real problem is that the controllers cannot be reached through HAproxy. That causes curl to try retrieve that nonsensical URL.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ianmiell/shutit-k8s-the-hard-way/issues/2#issuecomment-258412285, or mute the thread https://github.com/notifications/unsubscribe-auth/AGrczROnMlWYsUTdbYtqOLHnx4Jumn-Zks5q6xxGgaJpZM4KpCeA .
My book on Docker in Practice: Get 39% off with the code 39miell http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62
My book on Docker in Practice: Get 39% off with the code 39miell http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62
@ianmiell Unfortunately I've torn down my setup. I will update if I retry this again.
Well I guess that's the point! :)
On Fri, Nov 4, 2016 at 5:19 PM, Buchi Reddy Busi Reddy < notifications@github.com> wrote:
@ianmiell https://github.com/ianmiell Unfortunately I've torn down my setup. I will update if I retry this again.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ianmiell/shutit-k8s-the-hard-way/issues/2#issuecomment-258493642, or mute the thread https://github.com/notifications/unsubscribe-auth/AGrczdMJPZON1MEYclBuaNY4xWT1ETNOks5q62kygaJpZM4KpCeA .
My book on Docker in Practice: Get 39% off with the code 39miell http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62
@ianmiell I've retried this and this time the setup came up fine. Not sure what is the problem.
OK, that's great to hear, thanks for getting back to me.
Most often, issues with ShutIt come down to race conditions due to issues caused by lack of memory or CPU resource. I suspect that was the case here.
Thanks again!
I've tried to run the setup on my Mac (OS X El Capitan 10.11.6) with VirtualBox (5.0.28) and vagrant (1.8.4) already installed and the setup with the below errors.
curl --version