Node run error on service instance

This attempts to resolve an issue we were seeing with intermittent connection failures (such as VPN disconnects), which would manifest as service instances ending up in an unknown state with failure: `('Run %s already running !?!', ...)`.

This fix should handle the failed runs more gracefully, so that at least these services can recover and get back into a proper `up` or `down` state when the connection recovers.

The long term fix is to refactor a lot of this connection code to better handle these conditions.   I've started this work on another branch, but it is unlikely to be ready before release 0.6.3.

Also adds port to node config