can you try this: VBoxManage modifyvm "VM name" --natdnshostresolver1 on from: https://www.virtualbox.org/ticket/12441

It is indeed the virtualbox ethernet going bad or something https://dl.dropboxusercontent.com/u/12188201/Screen%20Shot%202015-07-08%20at%2017.03.46.png

So, ping to 10.244.xxx fails but ping to the 192.168.50.4 also fails? What happens if you disconnect from external network (to avoid the 10.244...) or delete the cf deployment from bosh-lite (dont

Here’s what just happened now testing it again. Note the times are a little longer this time so it’s not a hard 15

Yup. I saw that note somewhere and did it before even starting at all. -kris

Did you install the vbox client extensions toolkit? I had issues with networking when the client extensions were not installed. -Sabha -- View this message in context:

Nope vbox shows the vm still running just no longer accessible. So I do a vagrant halt / up which brings it back up and the only one from running bosh vms that is ever running is the postgres one.

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.

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?

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

Gwenn Etourneau wrote -- View this message in context: http://cf-bosh.70367.x6.nabble.com/cf-bosh-cf-mysql-release-tp406p418.html Sent from the CF BOSH mailing list archive at Nabble.com.

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

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

Can you successfully use `vagrant ssh` to get into the VM? If so how are the system resources? CPU, RAM... It sounds like some kind of virtualbox bug on your OS or misconfiguration.

I added it on the right hand nav of the wiki here: https://github.com/cloudfoundry-community/cf-docs-contrib/wiki Chip Childers | VP Technology | Cloud Foundry Foundation

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

May I inquire as to the location of the public calendar, please? Thanks! wrote: -- Casey

Hi all, I've updated the public calendar to reflect today's change. The CAB will be on July 15. -chip Chip Childers | VP Technology | Cloud Foundry Foundation wrote:

Hello! 1. Does BOSH has role-based authentication? The case is single bosh director managing multiple deployments. Some of deployments are in prod state, and some are PoC. I want to limit user

Please log into the proxy vm and check the logs /var/vcap/sys/log Grikor.Hanparsian(a)bnymellon.com> wrote: