https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-2319 Lustre <p>Do these messages provide any real benefit?</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>2012-11-13 09:54:49 LustreError: 137-5: lstest-MDT0000: Not available for connect from 172.20.4.132@o2ib500 (not set up) 2012-11-13 09:54:49 LustreError: 137-5: lstest-MDT0000: Not available for connect from 172.20.17.141@o2ib500 (not set up) 2012-11-13 09:54:50 LustreError: 137-5: lstest-MDT0000: Not available for connect from 172.20.17.65@o2ib500 (not set up) 2012-11-13 09:54:50 LustreError: Skipped 4 previous similar messages 2012-11-13 09:54:51 LustreError: 137-5: lstest-MDT0000: Not available for connect from 172.20.3.112@o2ib500 (not set up) 2012-11-13 09:54:51 LustreError: Skipped 12 previous similar messages </pre> </div></div> <p>At first glance, it looks like a peer is trying to connect before the target is fully initialized. Why do we need to print this to the console?</p> LU-2319

Remove "Not available for connect" messages

Improvement Minor Open Unresolved Alex Zhuravlev Prakash Surya llnl shh Tue, 13 Nov 2012 19:47:24 +0000 Tue, 7 Jun 2016 15:37:50 +0000 Lustre 2.4.0 0 5 <p>Alex </p> <p>Can you please triage and assign this one?</p> <p>Thanks</p> <p>Peter</p> <p>Unlike some of the other messages, this one is potentially quite important, if the client is trying to connect to a server but the server is not set up or the client is configured incorrectly. </p> <p>Will these messages really be shown if the target was misconfigured? From what I can tell, it's coming from here:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> 803 if (target-&gt;obd_stopping || !target-&gt;obd_set_up) { 804 cfs_spin_unlock(&amp;target-&gt;obd_dev_lock); 805 806 deuuidify(str, NULL, &amp;target_start, &amp;target_len); 807 LCONSOLE_ERROR_MSG(0x137, "%.*s: Not available for connect " 808 "from %s (%s)\n", target_len, target_start, 809 libcfs_nid2str(req-&gt;rq_peer.nid), 810 (target-&gt;obd_stopping ? 811 "stopping" : "not set up")); 812 GOTO(out, rc = -ENODEV); 813 } </pre> </div></div> <p>So at first glance, I don't see how a configuration error would cause it.</p> <p>And the case where a client is trying to connect to a server by the server is not set up is exactly the case this message for. Why is that important enough to make it to the console? I'd argue, it should handle it silently since that's normal during set up and tear down.</p> <p>Sorry, I was thinking of some other message then. </p> <p>Andreas, would you agree to turn this into CDEBUG() ? </p> Development End date Fri, 27 Jun 2014 19:47:24 +0000 Rank 1|hzvc67: Rank (Obsolete) 5543 Start date Tue, 13 Nov 2012 19:47:24 +0000