run fails with unknown curl option error

[buchireddy]

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

curl 7.43.0 (x86_64-apple-darwin15.0) libcurl/7.43.0 SecureTransport zlib/1.2.5
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz UnixSockets

client#gvvyLq7f#
CTRL-] caught, continuing with run...


================================================================================
Curl the load balancer ip for the nginx port
================================================================================
Command to be run is:
	curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?
until one of these seen:
.*nginx.*
================================================================================

Hit CTRL-] to continue

client#gvvyLq7f#
CTRL-] caught, continuing with run...
2016-11-03 16:29:32,754 INFO: Sending: "curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?" until one of these regexps seen: .*nginx.*
2016-11-03 16:29:32,754 INFO: Retrieving output from command: curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?
curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?
curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?
curl: option -: is unknown
curl: try 'curl --help' or 'curl --manual' for more information
client#gvvyLq7f# 2016-11-03 16:29:37,821 INFO: Retrieving output from command: curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?
curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?
curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?
curl: option -: is unknown
curl: try 'curl --help' or 'curl --manual' for more information
client#gvvyLq7f# 2016-11-03 16:29:42,885 INFO: Retrieving output from command: curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?
curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?
curl http://192.168.2.8:The connection to the server 192.168.2.8:6443 was refused - did you specify the right host or port?
curl: option -: is unknown
curl: try 'curl --help' or 'curl --manual' for more information

[jomagam]

Looks like the real problem is that the controllers cannot be reached through HAproxy. That causes curl to try retrieve that nonsensical URL.

[ianmiell]

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
#2 (comment),
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

[ianmiell]

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
#2 (comment),
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

[buchireddy]

@ianmiell Unfortunately I've torn down my setup. I will update if I retry this again.

[ianmiell]

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
#2 (comment),
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

[buchireddy]

@ianmiell I've retried this and this time the setup came up fine. Not sure what is the problem.

[ianmiell]

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!