VirtualBox install #202
Comments
|
What specific problems did you encounter? We are using 4.3.12 on variety of Macs (mine is 10.9.3). |
|
The VM was successfully deployed. I could vagrant ssh into the VM and monit showed all services running, etc. I wish I had kept my terminal history. Essentially, for some reason, the 192.168.50.4 was getting mapped to the en0 interface instead of the vboxnet0 interface. @fraenkel and I spent some time comparing environments and he noticed that I hadn't installed the extensions. After that, the network was correctly configured and the VM accessible to bosh from a fresh vagrant up. |
|
I've mentioned extenstion pack in the readme on develop branch [1]. It will be promoted to master at some point. [1] 0489877 |
|
I seem to have run into a similar issue as well. Very similar environment (VBox 4.3.18 on Mac 10.9.5) Works fine when I destroy the box and recreate it again, but whenever the network environment changes, bosh and cf stop working. [WARNING] cannot access director, trying 4 more times... I can still ssh in and looks like all the services are running. It also looks like I have vBox additions installed and running as well (see below). vagrant ssh
Process 'nats' running lsmod | grep -i vbox I tried out with no_proxy and http_proxy combinations to no avail. I did the bin/add_route as well. Obviously the apps also stopped working since there is some routing issue? Any ideas? Rags |
|
We are currently working on a bug to clean up pids after host vm is restarted. I would recommend running 'monit stop all' and then 'monit start all' to make sure all running processes are correct. -dmitriy
|
|
Yes, I did stop all the processes and restarted them. monit summary Process 'nats' not monitored Process 'nats' running Still the same results for the bosh commands. Rags |
|
Any updates/ideas? The processes still seem to be running but I am unable to bosh login. bosh target monit summary Process 'nats' running |
|
Is 192.168.50.4 pingable? On Tue, Nov 25, 2014 at 9:59 AM, Rags notifications@github.com wrote:
|
|
No it's not pingable. Even when I was able to successfully bosh login it was not pingable -- since it uses ssh port forwarding? I would rather not blow away and reinstall again :-) Rags |
|
I would suggest vagrant ssh into the box and trying to use bosh from On Tue, Nov 25, 2014 at 10:14 AM, Rags notifications@github.com wrote:
|
|
do you have a VPN? I have found that some VPN clients make it difficult to connect to your VM. I have to turn mine off (Cisco Anyconnect) |
I suspected the same or some vbox networking issue which it very well could be. VPN or no VPN I had same issues.
Tried that and was able to bosh login bosh-lite However, bosh cck showed the VMs not running. Unfortunately, my Mac spinning wheel started to appear and I had to reboot -- so, don't have that information. It looks like I may have to start from scratch (yet again). Rags |
|
It is expected that bosh vms will be unresponsive after a reboot. You have On Tue, Nov 25, 2014 at 4:04 PM, Rags notifications@github.com wrote:
|
|
Original issue is mentioned in bosh-lite readme. Closing. |
I struggled with a fresh install on a new machine (MacOSX 10.9.5). Until I installed the VirtualBox 4.3.18 Oracle VM VirtualBox Extension Pack, could not get the network correctly configured. Install notes should probably call this out as a dependency.
The text was updated successfully, but these errors were encountered: