diff options
| author | Matthias Radestock <matthias@lshift.net> | 2010-02-03 17:00:34 +0000 |
|---|---|---|
| committer | Matthias Radestock <matthias@lshift.net> | 2010-02-03 17:00:34 +0000 |
| commit | ce8891a58b10c5d8a8bfedc3b0a85d05b5a298ba (patch) | |
| tree | eafe14db855c46d6105453ca2fa0e65f19ef2b1a | |
| parent | 6536d1fe4230924eec20d13196b6d36a0a75fa07 (diff) | |
| download | rabbitmq-server-ce8891a58b10c5d8a8bfedc3b0a85d05b5a298ba.tar.gz | |
better error reporting
Don't mis-report errors on the remote end as "unable to connect" errors.
The reason this didn't come up previously is that the function we call
for close_connection is the first to fail with an 'EXIT' signal rather
than a 'throw'.
| -rw-r--r-- | src/rabbit_control.erl | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/rabbit_control.erl b/src/rabbit_control.erl index 2a4c1f03..2c2c67a6 100644 --- a/src/rabbit_control.erl +++ b/src/rabbit_control.erl @@ -81,6 +81,9 @@ start() -> {error, Reason} -> error("~p", [Reason]), halt(2); + {badrpc, {'EXIT', Reason}} -> + error("~p", [Reason]), + halt(2); {badrpc, Reason} -> error("unable to connect to node ~w: ~w", [Node, Reason]), print_badrpc_diagnostics(Node), |