Nov 23 09:08:15 aerocool systemd-udevd: failed to execute '/opt/VirtualBox/VBoxCreateUSBNode.sh' '/opt/VirtualBox/VBoxCreateUSBNode.sh 189 4 00': No such file or directory Nov 23 09:08:15 aerocool systemd-udevd: failed to execute '/opt/VirtualBox/VBoxCreateUSBNode.sh' '/opt/VirtualBox/VBoxCreateUSBNode.sh 189 3 00': No such file or directory Nov 23 09:08:12 aerocool systemd-udevd: failed to execute '/opt/VirtualBox/VBoxCreateUSBNode.sh' '/opt/VirtualBox/VBoxCreateUSBNode.sh 189 1 09': No such file or directory Nov 23 09:08:12 aerocool systemd-udevd: failed to execute '/opt/VirtualBox/VBoxCreateUSBNode.sh' '/opt/VirtualBox/VBoxCreateUSBNode.sh 189 129 09': No such file or directory Nov 23 09:08:12 aerocool systemd-udevd: failed to execute '/opt/VirtualBox/VBoxCreateUSBNode.sh' '/opt/VirtualBox/VBoxCreateUSBNode.sh 189 128 09': No such file or directory

Still the same results for the bosh commands.Nov 23 09:08:12 aerocool systemd-udevd: failed to execute '/opt/VirtualBox/VBoxCreateUSBNode.sh' '/opt/VirtualBox/VBoxCreateUSBNode.sh 189 0 09': No such file or directory System 'system_agent-id-bosh-0' not monitored Process 'director_scheduler' not monitored The Monit daemon 5.2.4 uptime: 3d 14h 42m Yes, I did stop all the processes and restarted them. Reply to this email directly or view it on GitHub. On Nov 19, 2014, at 6:11 AM, Rags wrote:ĭocumentation: $ sudo su - monit summary The Monit daemon 5.2.4 uptime: 3d 10h 32m I would recommend running 'monit stop all' and then 'monit start all' to make sure all running processes are correct.

We are currently working on a bug to clean up pids after host vm is restarted. Obviously the apps also stopped working since there is some routing issue? I tried out with no_proxy and http_proxy combinations to no avail. The Monit daemon 5.2.4 uptime: 3d 10h 32m

Documentation: $ sudo su monit summary.

It also looks like I have vBox additions installed and running as well (see below). I can still ssh in and looks like all the services are running. cannot access director, trying 1 more times. cannot access director, trying 2 more times. cannot access director, trying 3 more times. cannot access director, trying 4 more times. 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. I seem to have run into a similar issue as well.

Virtualbox extension pack 4.3.18