Jenkins throwing NPM err code 403 when publishing to Nexus Repo - docker

I’m having this weird error when deploying to nexus.
npm i
npm ERR! code E403
npm ERR! 403 Forbidden: express#^4.16.3
Where the artifact at the end it changes from time to time (I mean, is not always express#^4.16.3)
Things I have checked so far.
I can login to Nexus through browser using the user and password that is defined on the upload.
I can login to Nexus repo through shell using the user and password defined on the upload.
I can upload the package using a local shell and using the same credentials.
During the execution, I did a curl -v repo-url and I get a correct response (so I assume I got network connectivity).
I have checked if was a proxy, and there was.
I deleted the proxy configuration
I changed to another proxy
I added a no proxy variable so I can except the FQDN of the Nexus URL Repo
I also checked if the package (in this case express#^4.16.3) exists on Nexus, and it does.
But in all cases I’m still getting the 403 error at the end.
To give a bit more of context.
This is using Jenkins.
And targetting a new nexus that I'm deploying.
If I use the old nexus I don’t have this issues. It only happens to the new version
And, I migrate all the data, so the same user that exists in the old nexus is in the new one and you can login with those credentials.
I have checked nexus.log, request.log and Jenkins logs but didn't find any errors.
Jenkins and "old nexus" are installed in docker form in the same server
"New nexus" is installed in another server, also as a container.
From the servers I have network connectivity between them (can ping them, check port, and curl to the URLs.
I have given nx-admin role to the user that is configured.
Still the same error.
While the Jenkins job was running, I left the Nexus Log Viewer open
There was no error or sign in the Nexus Log Viewer.
BUT, I managed to find the following log in Jenkins: JENKINS_HOME/.npm/_logs/timestamp-debug.log
Where I have the ERR 403, and got the following
jenkins#hostname:~/.npm/_logs$ cat timestamp-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/var/jenkins_home/tools /jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/bin/node',
1 verbose cli '/var/jenkins_home/tools /jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/bin/npm',
1 verbose cli 'i' ]
2 info using npm#5.6.0
3 info using node#v8.9.4
4 verbose npm-session 609c979f77769373
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall api-docs#1.0.0
7 info lifecycle api-docs#1.0.0~preinstall: api-docs#1.0.0
8 silly install loadCurrentTree
9 silly install readLocalPackageData
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 silly install loadShrinkwrap
13 silly install loadAllDepsIntoIdealTree
14 http fetch GET 403 http://nexus-url/repository/my-repo-npm/express 2096ms
15 silly fetchPackageMetaData error for express#^4.16.3 403 Forbidden: express#^4.16.3
16 http fetch GET 403 http://nexus-url/repository/my-repo-npm/http-server 2094ms
17 http fetch GET 403 http://nexus-url/repository/my-repo-npm/swagger-ui-express 2092ms
18 silly fetchPackageMetaData error for http-server#^0.11.1 403 Forbidden: http-server#^0.11.1
19 silly fetchPackageMetaData error for swagger-ui-express#^4.0.1 403 Forbidden: swagger-ui-express#^4.0.1
20 http fetch GET 403 http://nexus-url/repository/my-repo-npm/multi-file-swagger 2095ms
21 silly fetchPackageMetaData error for multi-file-swagger#2.2.0 403 Forbidden: multi-file-swagger#2.2.0
22 http fetch GET 403 http://nexus-url/repository/my-repo-npm/express 45ms
23 silly fetchPackageMetaData error for express#^4.16.3 403 Forbidden: express#^4.16.3
24 http fetch GET 403 http://nexus-url/repository/my-repo-npm/http-server 46ms
25 silly fetchPackageMetaData error for http-server#^0.11.1 403 Forbidden: http-server#^0.11.1
26 http fetch GET 403 http://nexus-url/repository/my-repo-npm/multi-file-swagger 48ms
27 silly fetchPackageMetaData error for multi-file-swagger#2.2.0 403 Forbidden: multi-file-swagger#2.2.0
28 http fetch GET 403 http://nexus-url/repository/my-repo-npm/swagger-ui-express 49ms
29 silly fetchPackageMetaData error for swagger-ui-express#^4.0.1 403 Forbidden: swagger-ui-express#^4.0.1
30 silly saveTree api-docs#1.0.0
31 verbose stack Error: 403 Forbidden: express#^4.16.3
31 verbose stack at fetch.then.res (/var/jenkins_home/tools /jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/fetch.js:42:19)
31 verbose stack at tryCatcher (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
31 verbose stack at Promise._settlePromiseFromHandler (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
31 verbose stack at Promise._settlePromise (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
31 verbose stack at Promise._settlePromise0 (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
31 verbose stack at Promise._settlePromises (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
31 verbose stack at Async._drainQueue (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
31 verbose stack at Async._drainQueues (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
31 verbose stack at Immediate.Async.drainQueues (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
31 verbose stack at runCallback (timers.js:789:20)
31 verbose stack at tryOnImmediate (timers.js:751:5)
31 verbose stack at processImmediate [as _immediateCallback] (timers.js:722:5)
32 verbose cwd /var/jenkins_home/jobs/CUSTOM/workspace
33 verbose Linux 4.4.21-69-default
34 verbose argv "/var/jenkins_home/tools /jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/bin/node" "/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/bin/npm" "i"
35 verbose node v8.9.4
36 verbose npm v5.6.0
37 error code E403
38 error 403 Forbidden: express#^4.16.3
39 verbose exit [ 1, true ]
I looked for this packages on my Nexus Repo
express#^4.16.3
http-server#^0.11.1
swagger-ui-express#^4.0.1
multi-file-swagger#2.2.0
And found that I did not got some of those, so I downloaded them and uploaded to the repo.
I have also rerun the job, but still got the same error.

Even configuring the proxy at server and container level didn't worked.
I'd found out that Jenkins has a proxy configuration at the application level.
So I went into Jenkins, Administration section and configured the proxy properly. After that was done, it all started to work.

Related

TACO CLI - failing to build on MAC (missing write access)

I am a broken man, my builds have been working for years, and since iOS did its latest build, i have issues. I cannot for life get this to work.
MAC is catilina, i cannot believe all of this was working and then a simple version update and i cannot get it to build. I use command line for android (it still works and build successfully). I used the gui for iOS but am now getting a vsTAC issue immediately, so changed to use TACO-cli and was able to connect to mac and start the build process. It fails with this error, my build is all there as id expect except the platform folder where id navigate to open the xcode as normal. But i assume this is because my build is failing. I have updated the mac to be on the exact versions windows is on, i have give all the files the correct permissions. I am totally at a loss. I have been on higher versions before and had it working in past, i wasnt able to update to cordova 9 as one of those plugins didnt support 9 yet.
Currently running:
npm 6.7.0
node 11.15.0
cordova 8.1.2
cordova-android 9.0.0
cordova-ios 6.1.0
23 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-android-permissions
24 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-app-version
25 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-bluetoothclassic-serial
26 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-device
27 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-dialogs
28 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-file
29 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-file-opener2
30 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-file-transfer
31 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-geolocation
32 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-inappbrowser
33 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-navigationbar
34 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-network-information
35 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-screen-orientation
36 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-statusbar
37 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-whitelist
38 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-wkwebview-engine
39 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-wkwebview-file-xhr
40 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-sqlite-storage
41 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/es6-promise-plugin
42 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/ionic-plugin-keyboard
43 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/uk.co.workingedge.cordova.plugin.sqliteporter
44 timing stage:rollbackFailedOptional Completed in 1ms
45 timing stage:runTopLevelLifecycles Completed in 1869ms
46 warn VetIMPRESS#3.0.0 No repository field.
47 verbose stack Error: ENOENT: no such file or directory, access '/Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-android-permissions'
48 verbose cwd /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp
49 verbose Darwin 19.6.0
50 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "cordova-plugin-vs-taco-support" "--production" "--no-save"
51 verbose node v11.15.0
52 verbose npm v6.14.6
53 error code ENOENT
54 error syscall access
55 error path /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-android-permissions
56 error errno -2
57 error enoent ENOENT: no such file or directory, access '/Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-android-permissions'
58 error enoent This is related to npm not being able to find a file.
59 verbose exit [ -2, true ]

edgelet_utils... Get https://warlibregistry.azurecr.io/v2/iot-edge-engine-simulator/manifests/0.0.1-amd64: unauthorized: authentication required

I get a quite strange error message after executing Install-SecurityDaemon.
I deployed the IoT Edge module image to Azure Registry using Visual Studio Code. Then, I try to execute the IoT Edge solution in the simulator. Everything is ok.
I executed Install-SecurityDaemon. Everything went ok. But when I exec "iotedge list" command, I saw that only two main modules arrived but there is no module developed by me
PS C:\WINDOWS\system32> iotedge list
NAME STATUS DESCRIPTION CONFIG
edgeHub failed Failed (137) an hour ago mcr.microsoft.com/azureiotedge-hub:1.0
edgeAgent running Up 1 second mcr.microsoft.com/azureiotedge-agent:1.0
I'd seen the log and found only one error message:
11.11.2018 22:52:37 warn: edgelet_docker::runtime -- Attempt to pull image failed.
11.11.2018 22:52:42 info: edgelet_core::watchdog -- Checking edge runtime status
11.11.2018 22:52:42 info: edgelet_core::watchdog -- Edge runtime is running.
11.11.2018 22:52:43 warn: edgelet_docker::runtime -- Attempt to pull image failed.
11.11.2018 22:52:43 info: edgelet_http::logging -- [mgmt] - - - [2018-11-11 19:52:43.487711600 UTC] "POST /modules?api-version=2018-06-28 HTTP/1.1" 500 Internal Server Error 141 "-" "-" pid(any)
11.11.2018 22:52:43 warn: edgelet_utils::logging -- Get https://warlibregistry.azurecr.io/v2/iot-edge-engine-simulator/manifests/0.0.1-amd64: unauthorized: authentication required
11.11.2018 22:52:55 info: edgelet_http::logging -- [mgmt] - - - [2018-11-11 19:52:55.502141500 UTC] "POST /modules?api-version=2018-06-28 HTTP/1.1" 500 Internal Server Error 141 "-" "-" pid(any)
11.11.2018 22:52:55 warn: edgelet_utils::logging -- Get https://warlibregistry.azurecr.io/v2/iot-edge-engine-simulator/manifests/0.0.1-amd64: unauthorized: authentication required
Then I execute "docker login" command to be sure, that docker properly authorized in Azure registry. Everything was ok. Then, I reinstall SecurityDaemon. I got the same error.
Executing command
PS C:\WINDOWS\system32> docker pull warlibregistry.azurecr.io/iot-edge-engine-simulator:0.0.1-amd64
0.0.1-amd64: Pulling from iot-edge-engine-simulator
Digest: sha256:4ba6ae6442ca974b2c52459b85c0861e9664f26990c6e87f20829954f4d67d09
Status: Image is up to date for warlibregistry.azurecr.io/iot-edge-engine-simulator:0.0.1-amd64
return no errors. But if try to get manifest https://warlibregistry.azurecr.io/v2/iot-edge-engine-simulator/manifests/0.0.1-amd64 I really got the JSON with the error "unauthorized: authentication required".
In the Azure Portal after adding my module engineSimulator I saw another one iot_edge_engine_simulator with type "Module identity" which is not created by me. When I installed e.g. Microsoft module termoSensor - there is no such additional module.
So, I'm stuck, I don't know why the error occurs and what to do further.
Thank you for a help!
I found the mistake. When I set the module I missed filling "Container Registry Settings". In the case of using your own container registry (not Microsoft), you MUST fill authorization parameters.
In my case:
NAME: WarlibRegistry
ADDRESS: warlibregistry.azurecr.io
USERNAME & PASSWORD from the "Access keys" section of your container registry.

Verdaccio Bitbucket Error 400

I've tried to make verdaccio work with bibucket.
I've modified the config.yaml
But I only get this error
7 http request → POST https://fabienc974#bitbucket.org/-/v1/login
8 http 400 ← Bad Request (https://fabienc974#bitbucket.org/-/v1/login)
I've use '..' instead og '#' in my user name, but I've n'ever succeed login.
Has anyone maked it work?
Could someone help me please ? 4 days of seach, but it's not working
Update from my log file
here is the complete log file
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'adduser',
1 verbose cli '--registry',
1 verbose cli 'https://fabienc974#bitbucket.org/fabienc974/lionjar-master' ]
2 info using npm#5.7.1
3 info using node#v8.9.3
4 verbose config Skipping project config: /Users/slizee/.npmrc. (matches userconfig)
5 verbose npm-session eb79804c963f0c18
6 verbose web login before first POST
7 http request → POST https://fabienc974#bitbucket.org/fabienc974/-/v1/login
8 http 400 ← Bad Request (https://fabienc974#bitbucket.org/fabienc974/-/v1/login)
9 verbose web login not supported, trying couch
10 verbose login before first PUT { _id: 'org.couchdb.user:fabien.clotilde..gmail.com',
10 verbose login name: 'fabien.clotilde..gmail.com',
10 verbose login password: 'XXXXX',
10 verbose login type: 'user',
10 verbose login roles: [],
10 verbose login date: '2018-03-13T21:35:53.622Z' }
11 http request → PUT https://fabienc974#bitbucket.org/fabienc974/-/user/org.couchdb.user:fabien.clotilde..gmail.com
12 http 400 ← Bad Request (https://fabienc974#bitbucket.org/fabienc974/-/user/org.couchdb.user:fabien.clotilde..gmail.com)
13 verbose adduser before first PUT { _id: 'org.couchdb.user:fabien.clotilde..gmail.com',
13 verbose adduser name: 'fabien.clotilde..gmail.com',
13 verbose adduser password: 'XXXXX',
13 verbose adduser email: 'fabien.clotilde#gmail.com',
13 verbose adduser type: 'user',
13 verbose adduser roles: [],
13 verbose adduser date: '2018-03-13T21:35:54.309Z' }
14 http request → PUT https://fabienc974#bitbucket.org/fabienc974/-/user/org.couchdb.user:fabien.clotilde..gmail.com
15 http 400 ← Bad Request (https://fabienc974#bitbucket.org/fabienc974/-/user/org.couchdb.user:fabien.clotilde..gmail.com)
16 verbose stack Error: Registry returned 400 for PUT on https://fabienc974#bitbucket.org/fabienc974/-/user/org.couchdb.user:fabien.clotilde..gmail.com
16 verbose stack at fetch.defaults.catch.then.then.result (/usr/local/lib/node_modules/npm/node_modules/npm-profile/index.js:376:13)
16 verbose stack at <anonymous>
16 verbose stack at process._tickCallback (internal/process/next_tick.js:188:7)
17 verbose statusCode 400
18 verbose pkgid org.couchdb.user:fabien.clotilde..gmail.com
19 verbose cwd /Users/slizee
20 verbose Darwin 17.3.0
21 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "adduser" "--registry" "https://fabienc974#bitbucket.org/fabienc974/lionjar-master"
22 verbose node v8.9.3
23 verbose npm v5.7.1
24 error code E400
25 error Registry returned 400 for PUT on https://fabienc974#bitbucket.org/fabienc974/-/user/org.couchdb.user:fabien.clotilde..gmail.com
26 verbose exit [ 1, true ]
Always the same error, even if I change my config.yaml !
Thank you
Fabien
Author of verdaccio-bitbucket here.
Seems like it was an issue on v1 API, I recently released a new version of the plugin which is using bitbucket v2 API.
Thanks.

Elastic beanstalk deployment failing on npm install

I'm currently working on deploying a project to Elastic Beanstalk, but I'm getting a failure when trying to run npm install from my config file in the .ebextensions folder. The project's backend is using Rails in API mode, while the frontend is served from the app/client folder with React. I can deploy successfully and open routes served from the Rails API(..table_1/all), but nothing is rendered by React. In local testing I use 'yarn start' in the app/client folder.
As I'm a beginner when it comes to deployment and use of react I would appreciate all the help I can get fixing this. Based on the logs below I'm not really sure what to do.
This is my config file in .ebextensions
container_commands:
01_npm_install:
cwd: '/var/app/ondeck/client/'
command: 'npm install --timeout 30'
leader_only: 'false'
This is the error displayed in the EB CLI:
_ucsb_class_scheduler/Command 01_npm_install] : Activity execution failed, because: npm ERR! Linux 4.9.58-18.55.amzn1.x86_64
npm ERR! argv "/opt/elasticbeanstalk/support/node-install/node-v4.6.0-linux-x64/bin/node" "/usr/bin/npm" "install" "--timeout" "30"
npm ERR! node v4.6.0
npm ERR! npm v2.15.9
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/30
npm ERR! 404
npm ERR! 404 '30' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'client'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR! /var/app/ondeck/client/npm-debug.log
(ElasticBeanstalk::ExternalInvocationError)
And /var/app/ondeck/client/npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/opt/elasticbeanstalk/support/node-install/node-v4.6.0-linux-x64/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'install',
1 verbose cli '--timeout',
1 verbose cli '30' ]
2 info using npm#2.15.9
3 info using node#v4.6.0
4 verbose install initial load of /var/app/ondeck/client/package.json
5 verbose readDependencies loading dependencies from /var/app/ondeck/client/package.json
6 silly cache add args [ '30', null ]
7 verbose cache add spec 30
8 silly cache add parsed spec Result {
8 silly cache add raw: '30',
8 silly cache add scope: null,
8 silly cache add name: '30',
8 silly cache add rawSpec: '',
8 silly cache add spec: 'latest',
8 silly cache add type: 'tag' }
9 silly addNamed 30#latest
10 verbose addNamed "latest" is being treated as a dist-tag for 30
11 info addNameTag [ '30', 'latest' ]
12 silly mapToRegistry name 30
13 silly mapToRegistry using default registry
14 silly mapToRegistry registry https://registry.npmjs.org/
15 silly mapToRegistry data Result {
15 silly mapToRegistry raw: '30',
15 silly mapToRegistry scope: null,
15 silly mapToRegistry name: '30',
15 silly mapToRegistry rawSpec: '',
15 silly mapToRegistry spec: 'latest',
15 silly mapToRegistry type: 'tag' }
16 silly mapToRegistry uri https://registry.npmjs.org/30
17 verbose addNameTag registry:https://registry.npmjs.org/30 not in flight; fetching
18 verbose request uri https://registry.npmjs.org/30
19 verbose request no auth needed
20 info attempt registry request try #1 at 7:33:50 AM
21 verbose request id b42d3e8383778fa0
22 http request GET https://registry.npmjs.org/30
23 http 404 https://registry.npmjs.org/30
24 verbose headers { 'content-type': 'application/json',
24 verbose headers 'cache-control': 'max-age=0',
24 verbose headers 'content-length': '2',
24 verbose headers 'accept-ranges': 'bytes',
24 verbose headers date: 'Thu, 16 Nov 2017 07:33:50 GMT',
24 verbose headers via: '1.1 varnish',
24 verbose headers age: '0',
24 verbose headers connection: 'keep-alive',
24 verbose headers 'x-served-by': 'cache-sea1028-SEA',
24 verbose headers 'x-cache': 'MISS',
24 verbose headers 'x-cache-hits': '0',
24 verbose headers 'x-timer': 'S1510817631.695604,VS0,VE146',
24 verbose headers vary: 'Accept-Encoding' }
25 silly get cb [ 404,
25 silly get { 'content-type': 'application/json',
25 silly get 'cache-control': 'max-age=0',
25 silly get 'content-length': '2',
25 silly get 'accept-ranges': 'bytes',
25 silly get date: 'Thu, 16 Nov 2017 07:33:50 GMT',
25 silly get via: '1.1 varnish',
25 silly get age: '0',
25 silly get connection: 'keep-alive',
25 silly get 'x-served-by': 'cache-sea1028-SEA',
25 silly get 'x-cache': 'MISS',
25 silly get 'x-cache-hits': '0',
25 silly get 'x-timer': 'S1510817631.695604,VS0,VE146',
25 silly get vary: 'Accept-Encoding' } ]
26 verbose stack Error: Registry returned 404 for GET on https://registry.npmjs.org/30
26 verbose stack at makeError (/opt/elasticbeanstalk/support/node-install/node-v4.6.0-linux-x64/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:264:12)
26 verbose stack at CachingRegistryClient.<anonymous> (/opt/elasticbeanstalk/support/node-install/node-v4.6.0-linux-x64/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:242:14)
26 verbose stack at Request._callback (/opt/elasticbeanstalk/support/node-install/node-v4.6.0-linux-x64/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:172:14)
26 verbose stack at Request.self.callback (/opt/elasticbeanstalk/support/node-install/node-v4.6.0-linux-x64/lib/node_modules/npm/node_modules/request/request.js:200:22)
26 verbose stack at emitTwo (events.js:87:13)
26 verbose stack at Request.emit (events.js:172:7)
26 verbose stack at Request.<anonymous> (/opt/elasticbeanstalk/support/node-install/node-v4.6.0-linux-x64/lib/node_modules/npm/node_modules/request/request.js:1067:10)
26 verbose stack at emitOne (events.js:82:20)
26 verbose stack at Request.emit (events.js:169:7)
26 verbose stack at IncomingMessage.<anonymous> (/opt/elasticbeanstalk/support/node-install/node-v4.6.0-linux-x64/lib/node_modules/npm/node_modules/request/request.js:988:12)
27 verbose statusCode 404
28 verbose pkgid 30
29 verbose cwd /var/app/ondeck/client
30 error Linux 4.9.58-18.55.amzn1.x86_64
31 error argv "/opt/elasticbeanstalk/support/node-install/node-v4.6.0-linux-x64/bin/node" "/usr/bin/npm" "install" "--timeout" "30"
32 error node v4.6.0
33 error npm v2.15.9
34 error code E404
35 error 404 Registry returned 404 for GET on https://registry.npmjs.org/30
35 error 404
35 error 404 '30' is not in the npm registry.
35 error 404 You should bug the author to publish it (or use the name yourself!)
35 error 404 It was specified as a dependency of 'client'
35 error 404
35 error 404 Note that you can also install from a
35 error 404 tarball, folder, http url, or git url.
36 verbose exit [ 1, true ]

Why are Google Pipeline VM instances hanging indefinitely?

I am using Dockerflow to run parallel tasks through the Google Pipelines API on Google Cloud Platform. I started a single-step task running 1389 VMs in parallel and found that 233 of the VMs were apparently doing nothing and hanging indefinitely.
I did a spot check of the serial console output and repeatedly saw the VMs running into "Getting controller config failed" errors.
When I tried logging into the VMs I received the error: "Connection Failed. We are unable to connect to the VM on port 22".
I am wondering why my VM instances are hanging, and if there is something I can do to avoid running into these issues.
I've included a snippet of the serial console output below
startupscript: +++ readlink -f /usr/share/google-genomics/startup.sh
startupscript: ++ dirname /usr/share/google-genomics/startup.sh
startupscript: + cd /usr/share/google-genomics
startupscript: + ./controller --operation_id <id> --validation_token <token> --base_path https://genomics.googleapis.com
create controller[2905]: Getting controller config
create controller[2905]: Getting controller config failed, will retry: Get <link>: Get <service_account_token_link>: net/http: timeout awaiting response headers
create controller[2905]: Getting controller config failed, will retry: Get <link>: dial tcp 74.125.26.95:443: i/o timeout
collectd[2342]: write_gcm: Asking metadata server for auth token
collectd[2342]: write_gcm: curl_easy_perform() failed: Couldn't connect to server
collectd[2342]: write_gcm: Error -1 from wg_curl_get_or_post
collectd[2342]: write_gcm: wg_transmit_unique_segment failed.
collectd[2342]: write_gcm: wg_transmit_unique_segments failed. Flushing.
there was a temporary networking issue in us-east1-b. All 3 above VMs were in us-east1-b. These minor incidents do not appear in https://status.cloud.google.com/
Serial console output for a successful run looks like:
A Feb 21 19:05:06 ggp-5629907348021283130 startupscript: + ./controller --operation_id --validation_token --base_path https://autopush-genomics.sandbox.googleapis.com
A Feb 21 19:05:06 ggp-5629907348021283130 create controller[2689]: Getting controller config
A Feb 21 19:05:36 ggp-5629907348021283130 create controller[2689]: Getting controller config failed, will retry: Get https://genomics.googleapis.com/v1alpha2/pipelines:getControllerConfig?alt=json&operationId=&validationToken=: dial tcp 173.194.212.81:443: i/o timeout
A Feb 21 19:05:43 ggp-5629907348021283130 controller[2689]: Switching to status: pulling-image
A Feb 21 19:05:43 ggp-5629907348021283130 controller[2689]: Calling SetOperationStatus(pulling-image)
A Feb 21 19:05:44 ggp-5629907348021283130 controller[2689]: SetOperationStatus(pulling-image) succeeded
The "Getting controller config failed, will retry" is fine. It succeeded upon retry. The "SetOperationStatus(pulling-image) succeeded" indicates networking is working.
In theory, you can submit any number of jobs to Pipelines API and the API will take care of queueing.
If these temporary networking hiccups become common, we may consider changing Pipelines API to somehow detect and retry.
there may have been a temporary networking issue. Can you give me some failed operation ids (or failed VM names)?
Have you tried again since then; can you reproduce the problem?

Resources