Socket bind failure handling

[pervazea]

If I run Peloton, then run another instance. In the second instance:

Peloton does a bit of initialization, then fails on the socket bind (expected), and throws an exception The exception is caught and peloton exits. Two problems:

1. Peloton exits, silently. Exit code is 0, indicating a normal exit. This is incorrect. It should return an appropriate error exit value.
2. It does this silently. It should log an error. It encountered a fatal, non-recoverable error and quit.