Improve the robustness of the deployment via a few methods:

- add retry logic for starting the master process
- shutdown existing slave services before the master service
- log an error when 'clusterrunner stop' fails
The 5 seconds before was the time we gave to have the tornado server startup and begin accepting/responding to http requests. The 1 second I'm giving here is the amount of time for the process to appear in "ps ax". 1 second is generous here if it were local, but I'm giving it 1 second because it's possible the master is remote, and the master service start command is being performed over ssh.

My theory on why the process would fail to start right now is that the master port is still used. The 'stop' command for the master service has been issued pretty much immediately before we ask the master service to start up. This retry logic would sort of cover up for the sweet time that tornado may take to release the port that we need to run this master service on.

Also, I'm open to increasing the timeout of 5 seconds to maybe 10.