Check if local services are up before starting them

- Ran into this issue when using a local master/slave.  If
the master and slave were already up, using the build command
would wipe out the clusterrunner_slave.log, try to start the
slave service again, and log some ugly exceptions.

- Now we check if the master is up first, and abandon starting
local services if so.
So previously we'd just go ahead and try to start the master and slave, and if they were already running those commands would fail? Would it also wipe out the master log as well? 

Just out of curiosity: was the behavior that trying to launch a new master/slave would cause the logs to rotate? So the previously running master and slave would then continue actively logging to clusterrunner_master.log.1 and clusterrunner_slave.log.1? 

(I just did a manual test and confirmed that is indeed what seems to be happening but wanted to make sure that's what you were seeing as well. If I tried to start a slave five more times, log rotation would then delete the currently running slave's log and it would be gone for good, although that doesn't seem to cause an error in the slave process.)