• Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Low Low
    • None
    • None
    • None
    • None

      Summary

      If sockets are not available on Windows agents, source code checkouts will fail with a Windows socket error

      Steps to Reproduce

      1. Set up a Windows agent with invalid WinSocks configuration that needs to be refreshed
      2. Set up a build with source code checkout
      3. Run the build

      Expected Results

      The build runs as expected

      Actual Results

      The below exception is thrown in the atlassian-bamboo.log file:

      2017-07-20 17:29:26,299 WARN [sshd-SshServer[1272c81]-nio2-thread-1] [Nio2Acceptor] Caught IOException while accepting incoming connection from /127.0.0.1:53265: An operation was attempted on something that is not a socket
      java.io.IOException: An operation was attempted on something that is not a socket

      Workaround

      To work around this error, please reset WinSocks as follows:

      1. Open the Command Prompt with elevated permissions (Run as Admin)
      2. Run the following command at the command prompt: netsh winsock reset
      3. Press Enter, and restart the computer

      Related

      Improvement request:

            [BAM-18570] Socket failure on Windows agents

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 2411509 ] New: JAC Bug Workflow v3 [ 3384872 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Krystian Brazulewicz made changes -
            Resolution New: Not a bug [ 12 ]
            Status Original: Needs Triage [ 10030 ] New: Resolved [ 5 ]

            Krystian Brazulewicz added a comment - If you encounter this problem refer to https://confluence.atlassian.com/bamkb/source-code-checkout-fails-on-windows-agents-due-to-winsock-error-932389394.html
            Ellie Z (they/them) made changes -
            Security Original: Reporter and Atlassian Staff [ 10751 ]
            Ellie Z (they/them) made changes -
            Description New: h3. Summary
            If sockets are not available on Windows agents, source code checkouts will fail with a Windows socket error

            h3. Steps to Reproduce
            # Set up a Windows agent with invalid WinSocks configuration that needs to be refreshed
            # Set up a build with source code checkout
            # Run the build

            h3. Expected Results
            The build runs as expected

            h3. Actual Results
            The below exception is thrown in the {{atlassian-bamboo.log}} file:
            {noformat}
            2017-07-20 17:29:26,299 WARN [sshd-SshServer[1272c81]-nio2-thread-1] [Nio2Acceptor] Caught IOException while accepting incoming connection from /127.0.0.1:53265: An operation was attempted on something that is not a socket
            java.io.IOException: An operation was attempted on something that is not a socket{noformat}

            h3. Workaround
            To work around this error, please reset WinSocks as follows:
            # Open the Command Prompt with elevated permissions (Run as Admin)
            # Run the following command at the command prompt: {{netsh winsock reset}}
            # Press Enter, and restart the computer

            h3. Related
            Improvement request:
            * [BAM-18569 - Improved reporting when git hangs on Windows agents due to socket error|https://jira.atlassian.com/browse/BAM-18569]
            Ellie Z (they/them) created issue -

              Unassigned Unassigned
              ezeidan Ellie Z (they/them)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: