On Jul 8, 2015, at 12:40, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote:

Issue of not being able to ping 192.168.50.4 is different from bohs reporting unresponsive VMs. At the bottom of the readme it mentions cck command: https://github.com/cloudfoundry/bosh-lite/blob/master/docs/bosh-cck.md. This should resolve unresponsive agents.

On Wed, Jul 8, 2015 at 9:00 AM, kris rice <kris.rice(a)jokr.net> wrote:
I’m sure it’s something os/vbox but on two machines repeating nothing but the steps in the doc I get the same results.

Here’s another example of what’s right now. I stop/start vagrant/vbox and then issue a bosh vms and everything is unresponsive but 1
http://pastebin.com/4THpYher

I’m the only person on this machine which is 48 cores and 256m of ram in it so should be more than enough.


-kris

On Jul 8, 2015, at 11:14, kris rice <kris.rice(a)jokr.net> wrote:

All,
I’ve run the install several times now on both OEL 6.4 and Fedora 20 with virtualbox 4.3.28 w/extras ( current ) They have all very consistently stopped being able to access the network at about the 15 minute mark with this failure

System call error while talking to director: No route to host - connect(2) (https://192.168.50.4:25555)

Pings to the 192.168.50.4 also fail ( as expected from the message )

I’ve checked that iptables is clean. Is there something else I should be looking at ?
-kris

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh