summaryrefslogtreecommitdiffstats
path: root/transport/ib-verbs
diff options
context:
space:
mode:
authorAmar Tumballi <amar@gluster.com>2009-06-01 17:58:41 +0000
committerAnand V. Avati <avati@dev.gluster.com>2009-06-03 06:00:08 -0700
commit08d46effee3b5e07b89a3a04251714383cf02eec (patch)
tree99a7ddecd7d1f295a9d70d785fc009d059b29dfc /transport/ib-verbs
parent2dc70c22bdd25362a95f19ab551d39e99f76ebfb (diff)
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 <avati@dev.gluster.com>
Diffstat (limited to 'transport/ib-verbs')
-rw-r--r--transport/ib-verbs/src/ib-verbs.c13
1 files changed, 10 insertions, 3 deletions
diff --git a/transport/ib-verbs/src/ib-verbs.c b/transport/ib-verbs/src/ib-verbs.c
index a05fcf12e07..6b51232849a 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);
}