Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: core
    • Labels:
    • Environment:
      RHEL 6.4 x86_64
    • Similar Issues:

      Description

      jenkins->nodes->'node x' 'Launch slave agent'

      Having restarted jenkins this shows the connection progress

      Trying the same on a second node the log 'spinning cursor' shows but nothing is logged.

      The connection is established but nothing is ever written to this node log for this or any subsequent node.

      Problem seems to have been present in the last two or three point versions. Currently running 1.525

        Attachments

          Issue Links

            Activity

            Hide
            schander Satpal Chander added a comment - - edited

            We have been seeing this to.
            What makes this is a little more interesting is that we have been having this Builds fail because of "slave went offline during the build" problem aswell. Given that, that bug is related to not finding the correct log file i do wonder if it is linked in some way.

            We are running v 1.530 on debian with slaves running OS X

            Show
            schander Satpal Chander added a comment - - edited We have been seeing this to. What makes this is a little more interesting is that we have been having this Builds fail because of "slave went offline during the build" problem aswell. Given that, that bug is related to not finding the correct log file i do wonder if it is linked in some way. We are running v 1.530 on debian with slaves running OS X
            Hide
            chris_jones Chris Jones added a comment -

            With the roll to 1.531 I had the chance to look at this again.
            The problem persists but not immediately it seems.
            I have six nodes but the log 'hang' does not occur until one or more of them report 'Time out for last 4 try' under 'Response time'.
            Before that happens I get the log details for any, once it reaches beyond 4 all logs are unavailable.
            Curiously it reports this timeout even for nodes that have legitimately gone off line due to non use. When the particular node is demanded it will come back on line but the log is never again available that I can see.

            Show
            chris_jones Chris Jones added a comment - With the roll to 1.531 I had the chance to look at this again. The problem persists but not immediately it seems. I have six nodes but the log 'hang' does not occur until one or more of them report 'Time out for last 4 try' under 'Response time'. Before that happens I get the log details for any, once it reaches beyond 4 all logs are unavailable. Curiously it reports this timeout even for nodes that have legitimately gone off line due to non use. When the particular node is demanded it will come back on line but the log is never again available that I can see.

              People

              • Assignee:
                Unassigned
                Reporter:
                chris_jones Chris Jones
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: