[LU-2319] Remove "Not available for connect" messages

• Type: Improvement
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.4.0
• Labels: llnl shh
• Assignee: Alex Zhuravlev
• Reporter: Prakash Surya (Inactive)

Description

Do these messages provide any real benefit?

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

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?