Log etcd machine updates.

Reports come in that this trigger skydns hogging the CPU, at least log
this so we can see something is going crazy.
Version 2.0.0g
Use exponential backoff when getting machines updates

When there is no etcd the machine update Watch fires continuously,
this causes SkyDNS to hog the CPU. Use simple exponential back off,
from 1 second to 32 seconds when trying to update.
And reset the timer when a connect works
fucking travis