Re: bosh-lite / cf fails in ~15 minutes

Dmitriy Kalinin

Is your vagrant VM gets shut down by something/someone after 15 minutes?
The only time bosh managed containers inside bosh-lite get destroyed is
when the VM is rebooted/shut down.

On Wed, Jul 8, 2015 at 11:35 AM, Joshua McKenty <jmckenty(a)> wrote:

Sounds like DHCP lease time or some kind of external network config issue
- is there a software firewall running on your local machine? Weird NATTING
or ARP Proxy?

On Jul 8, 2015, at 10:04 AM, kris rice <kris.rice(a)> wrote:

Right. I've done that and 15 minutes later same exact thing again


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

Issue of not being able to ping is different from bohs
reporting unresponsive VMs. At the bottom of the readme it mentions cck
This should resolve unresponsive agents.

On Wed, Jul 8, 2015 at 9:00 AM, kris rice <kris.rice(a)> 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

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


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

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) (

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

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

cf-bosh mailing list

cf-bosh mailing list

cf-bosh mailing list

cf-bosh mailing list

Join to automatically receive all group messages.