Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-2319

Remove "Not available for connect" messages

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • Lustre 2.4.0
    • Lustre 2.4.0
    • 5543

    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?

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-1095 Console message cleanup

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. LU-17432 add "slow start" to some CWARN/CERROR messages

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            [LU-2319] Remove "Not available for connect" messages
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-1095 [ LU-1095 ]
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-17432 [ LU-17432 ]
            adilger Andreas Dilger made changes -
            Fix Version/s New: Lustre 2.4.0 [ 10154 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            pjones Peter Jones made changes -
            End date New: 27/Jun/14
            Start date New: 13/Nov/12
            morrone Christopher Morrone (Inactive) made changes -
            Labels Original: shh New: llnl shh
            pjones Peter Jones made changes -
            Assignee Original: WC Triage [ wc-triage ] New: Alex Zhuravlev [ bzzz ]
            prakash Prakash Surya (Inactive) made changes -
            Description Original: Do these messages provide any real benefit?

            {noformat}

            2012-11-13 09:54:49 LustreError: 32609:0:(sec_config.c:1024:sptlrpc_target_local_copy_conf()) missing llog context
            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
            {noformat}

            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?             		New: Do these messages provide any real benefit?

            {noformat}
            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
            {noformat}

            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?
            prakash Prakash Surya (Inactive) created issue -

            People

              bzzz Alex Zhuravlev
              prakash Prakash Surya (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: