Micro Cloud Foundry Trouble Shooting Help

Here is some general troubleshooting tips for Micro Cloud Foundry (MCF)

Problem with proxies

If you are using a proxy keep in mind that proxy may not be able to access your micro VM. E.g. if you use NAT for the VM, there is no way for the proxy to find the way back to the VM, which means you must exclude your domain in the proxy settings on your system.

Another proxy related problem is if you use VPN on your host while using bridged mode, then the traffic in in the Micro Cloud Foundry VM won't enter the tunnel, and thus not be able to reach the proxy.

Problem accessing your instance

If you are trying to access your instance but it fails, e.g.

martin@vaccine$ vmc target api.martin.cloudfoundry.me
Host is not valid: 'http://api.martin.cloudfoundry.me'
Would you like see the response [yN]? y
HTTP exception: Errno::ETIMEDOUT:Operation timed out - connect(2)

Then the DNS entry may not be up to date.

Check the Micro Cloud Foundry console, enter "1" and hit return to refresh the screen. If you see a line like:

Current Configuration:
 Identity:   martin.cloudfoundry.me (DNS out of sync)
 Admin:      martin@englund.nu
 IP Address: (network up)

Then you should enter "2" and hit return, to force an update to DNS.

On the other hand, if you see "ok" as DNS status, then the IP address of the VM matches what is in DNS. Validate that you do not have a cached entry on your local system with

martin@vaccine$ host api.martin.cloudfoundry.me
api.martin.cloudfoundry.me is an alias for martin.cloudfoundry.me.
martin.cloudfoundry.me has address

If the two differ, then you need to flush the DNS cache:

  • Mac OS X
    dscacheutil -flushcache
  • Linux (Ubuntu)
    sudo /etc/init.d/nscd restart
  • Windows
    ipconfig /flushdns

Switching between networks

If you switch between networks often and don't need to make your Micro Cloud Foundry VM available to other users, then it is easier to reconfigure the VM networking to use NAT instead of the default bridged mode.

Gathering debugging info

If you encounter problems and need help debugging, please do the following:

  1. In the console menu, enter 12 and hit enter to enable debug output
  2. Hit ALT-F2 or use ssh and log in using the vcap user and the password entered during the configuration phase
  3. Get the contents of the file /var/vcap/sys/log/micro/micro.log and attach it to the ticket

Working offline

If you are going to work without Internet access, you can configure Micro Cloud Foundry to use vcap.me

Then you need to use ssh to setup a tunnel to your VM

martin@vaccine$ sudo ssh -L 80: vcap@
Password: ************** <-- this is the sudo password vcap@'s password: ****************

After this you can target your instance with:

martin@vaccine$ vmc target api.vcap.me
Succesfully targeted to [http://api.vcap.me]

and then continue to register and login.

Getting 'Cannot connect to cloud foundry.com' during process of configuring your Micro Cloud VM

If you have configured your Micro Cloud VM to use DHCP, it will assign an address from your networks DHCP pool.   If you are have a team of people continuously creating/destroying VMs, and your DHCP addresses have a lease life of 12 to 24 hours, it's possible you may exhaust your DHCP pool.   If this is the case, you may see a message that you cannot connect to cloudfoundry.com during the configuration process, even though you will be able to reach cloud foundry.com via a browser.    Restarting your DHCP server should return unused leases to the pool, which should enable them for reuse in configuring your Micro Cloud Foundry VM. 

Have more questions? Submit a request


Powered by Zendesk