Google Compute Engine health checks failing

Question

I have a node.js app on two VM instances that I\'m trying to load balance with network load balancing. To test that my servers are up and serving, I have the health check r

Answer 1

I got this back working, after making contact with the Google Compute Engine team. There is a service process on a GCE VM that needs to run on boot, and continue running while the VM is alive. The process is named google-address-manager. It should run at runlevels 0-6. For some reason this service stopped and will not start when one of my VMs boots/reboots. Starting the service manually worked. Here are the steps we went through to determine what was wrong: (This is a Debian VM)

sudo ip route list table all

This will display your route table. In the table, there should be a route to your Load Balancer Public IP:

local lb.pub.ip.addr dev eth0  table local  proto 66  scope host

If there is not, check that google-address-manager is running:

sudo service google-address-manager status

If it not running, start it:

sudo service google-address-manager start

If it starts ok, check your route table, and you should now have a route to your load balancer IP. You can also manually add this route:

sudo /sbin/ip route add to local lb.pub.ip.addr/32 dev eth0 proto 66

We have still not resolved why the address manager stopped and does not start on boot, but at least the LB Pool is healthy