initializing NodeManager should still work even if one of the startup nodes listed is unavailable
Merge pull request #52 from happybits/unstable-init-w-node-down

initializing NodeManager should still work