1. posterid:473307
  2. Messages

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

Kris Rice
 

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. This machine is brand newly created so everything is bone stock. The only thing I’ve wondered is we internally use the 10.244.x.x ranges however I’ve added the routes to the linux host but we do not use 192.168.x.x at all. Is there a way to move what’s used internally? However this doesn’t solve the fact that 192.168.50.4 becomes unacccessible unless that is simply doing a port-fwd to one of the 10.x IPs ?

└─>netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.88.68.1 0.0.0.0 UG 0 0 0 eth0
10.88.68.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0
10.244.0.0 192.168.50.4 255.255.224.0 UG 0 0 0 vboxnet0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 usb0
169.254.182.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0
192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 vboxnet0

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

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)pivotal.io <mailto:jmckenty(a)pivotal.io>> 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)jokr.net <mailto:kris.rice(a)jokr.net>> wrote:

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

-kris

On Jul 8, 2015, at 12:40, Dmitriy Kalinin <dkalinin(a)pivotal.io <mailto: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 <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 <mailto: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 <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 <mailto: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 <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 <mailto:cf-bosh(a)lists.cloudfoundry.org>
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh <https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh>


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

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org <mailto:cf-bosh(a)lists.cloudfoundry.org>
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh <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

?
attachment.html

Join {cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.