From 4fa1211b0fa015b49e662b26327c306f42299bbb Mon Sep 17 00:00:00 2001 From: Amar Tumballi Date: Mon, 1 Jun 2009 17:58:41 +0000 Subject: ib-verbs error log enhancement Earlier it was thought that only not having 'opensm' running will cause handshake errors in ib-verbs. Recently understood that even having a wrong 'ib-verbs.port' option can also cause the same behavior, and it took more than 5-6 e-mail iterations with the user and lot of brain cycle in support team to understand the problem. Made the log message more descriptive, so user can be find the cause, or can send us email without wasting time. Signed-off-by: Anand V. Avati --- transport/ib-verbs/src/ib-verbs.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) (limited to 'transport') diff --git a/transport/ib-verbs/src/ib-verbs.c b/transport/ib-verbs/src/ib-verbs.c index d44d1f3acc7..687b9c3e874 100644 --- a/transport/ib-verbs/src/ib-verbs.c +++ b/transport/ib-verbs/src/ib-verbs.c @@ -1226,9 +1226,16 @@ ib_verbs_send_completion_proc (void *data) post->buf, wc.byte_len, post->reused); if (wc.status == IBV_WC_RETRY_EXC_ERR) gf_log ("ib-verbs", GF_LOG_ERROR, - "might be an issue with SM. " - "retry after running 'opensm' " - "(Subnet Manager)."); + "connection between client and" + " server not working. check by" + " running 'ibv_srq_pingpong'. " + "also make sure subnet manager" + " is running (eg: 'opensm'), " + "or check if ib-verbs port is " + "valid (or active) by running " + " 'ibv_devinfo'. contact " + "Gluster Support Team if " + "the problem persists."); if (peer) transport_disconnect (peer->trans); } -- cgit