Dial tcp: i/o timeout while pushing a sample app to Cloud Foundry BOSH-Lite deployment


Giovanni Napoli
 

Hi everybody, few days ago i've deployed Cloud Foundry locally using BOSH-Lite, and seems that all VMS deployed run without any problem. Here's a screen with the VMS and IP's:
http://imgur.com/zEo68Dp

Than i've followed this blog to push a sample "Hello World" app, for testing my deployment:
https://blog.pivotal.io/labs/labs/worlds-smallest-iaas-part-4-hello-world

But when i launche the "cf push hello -b ruby_buildpack" command, i have an intermintently "dial tcp: i/o timeout":
http://imgur.com/eWYRd6M
As you can see, at first launch, it gave me the timeout error. Then it started to push the app but stopped again.
Can you help me? Thanks.


Giovanni Napoli
 

EDIT: Strange thing. I tried to not use a wired internet connection, and it's works. Infact i used an hotspot with my cell phone and it pushes the app to the local Cloud without any problem.
Just saying.


Rob Dimsdale
 

We have noticed similar things recently. Our issue was a misconfigured DNS record in /etc/resolv.conf so we suggest you check your nameservers point to valid DNS servers, and that those servers have the required DNS entries for the hostnames.

It might also be related to the CLI switching from golang 1.5 to 1.6 in cf v6.16, though we haven't confirmed this. You could try downloading the previous version of the CLI and seeing if that resolves your issue.

It's also possible that DNS is taking longer than 5 seconds to return correctly - the CLI will not handle this due to a hard-coded timeout. See https://github.com/cloudfoundry/cli/issues/763 for more information.

Thanks,
Rob && Al
CF Release Integration
Pivotal


Giovanni Napoli
 

Hi Rob, first of all thank you for your answer. I tried to look into /etc/resolv.conf file and the only nameserver is 127.0.1.1 that is my hostname. This morning, trying to do the same thing and using another time my cell phone and a hotspot, seems to be the same issue. I really don't know what cloud be the problem. I'll try to switch to CLI 1.5 and see if that resolves the issue.
However, have you got any other suggestions?


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Giovanni Napoli
 

PS: I tried to install and use cf-cli 6.15 and had the same issue.


Rob Dimsdale
 

Giovanni,

A github issue was opened by others with similar issues at https://github.com/cloudfoundry/cf-release/issues/923. Could you take a look at our suggestions there and, in the interest of keeping conversation in one place, post any further responses on that issue?

Thanks,
Rob & Nima
CF Release Integration


Giovanni Napoli
 

Hello Rob, sure...i will post to the other thread. Thank you for your answer.