Build environment- Reoccurring Network errors

kneufeld's Avatar

kneufeld

13 Jul, 2018 03:05 PM

Two hours ago builds were ticking along like usual, but we are now experiencing reoccurring network errors at the install step.

npm install -g newman
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! network request to https://registry.npmjs.org/newman failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\appveyor\AppData\Roaming\npm-cache\_logs\2018-07-13T15_00_00_945Z-debug.log
Command exited with code 1

We have tried the following:

  • commented out npm Newman install, but fails at the next installation

  • tried the previous image; just for kicks to see if it was that.

  1. Support Staff 1 Posted by Feodor Fitsner on 13 Jul, 2018 03:17 PM

    Feodor Fitsner's Avatar

    We are investigating the issue. Thanks for reporting!

  2. 2 Posted by kneufeld on 13 Jul, 2018 03:26 PM

    kneufeld's Avatar

    Feodor,

    Timeline:
    ~ 6:07am PDT

    Error downloading cache item: Remote server returned 500: The process cannot access the file 'D:\cache-data\build-cache-31705\project-331764\da39a3ee5e6b4b0d3255bfef95601890afd80709\283bdbabe7afeec91125ffa362dff032f2794941.zip.001\data' because it is being used by another process.
    

    The next commit at
    ~ 6:10am PDT

    npm install -g newman
    npm ERR! code ENOTFOUND
    npm ERR! errno ENOTFOUND
    npm ERR! network request to https://registry.npmjs.org/newman failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
    npm ERR! network This is a problem related to network connectivity.
    npm ERR! network In most cases you are behind a proxy or have bad network settings.
    npm ERR! network
    npm ERR! network If you are behind a proxy, please make sure that the
    npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
    npm ERR! A complete log of this run can be found in:
    npm ERR!     C:\Users\appveyor\AppData\Roaming\npm-cache_logs\2018-07-13T15_00_00_945Z-debug.log
    Command exited with code 1
    

    Thanks for the quick response.

    On July 13, 2018 at 10:17:36 AM, Feodor Fitsner ([email blocked][email blocked]) wrote:

  3. Support Staff 3 Posted by Feodor Fitsner on 13 Jul, 2018 03:50 PM

    Feodor Fitsner's Avatar

    It should be fixed now. Please let us know if you are still experiencing the issues.

  4. 4 Posted by kneufeld on 13 Jul, 2018 03:55 PM

    kneufeld's Avatar

    Thanks!

    On July 13, 2018 at 10:50:43 AM, Feodor Fitsner ([email blocked]<mailto:[email blocked]>) wrote:

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac