search

yudai / cf_nise_installer

Cloud Foundry v2 installer with Nise BOSH and Vagrant
Apache License 2.0
84 stars 57 forks source link

Unable to deploy the applciation -npm ERR! code ETIMEDOUT #166

Open gowrisankar22 opened 8 years ago

gowrisankar22 commented 8 years ago

Hi,

while deploying the node.js application deployment fails. Can you check the error log below and let me knoe how to solve this issue?

C:\Gowrisankar_backupfiles\2016\Learning_OS_CF_DOC\CloudFoundry\techtalks-demo\mathematics-service-broker>cf push Using manifest file C:\Gowrisankar_backupfiles\2016\Learning_OS_CF_DOC\CloudFoundry\techtalks-demo\mathematics-service-broker\manifest.yml

Creating app mathematics-broker-app in org DevBox / space gowri as admin... OK

Creating route mathematics-broker-app.10.97.156.146.xip.io... OK

Binding mathematics-broker-app.10.97.156.146.xip.io to mathematics-broker-app... OK

Uploading mathematics-broker-app... Uploading app files from: C:\Gowrisankar_backupfiles\2016\Learning_OS_CF_DOC\CloudFoundry\techtalks-demo\mathematics-service-broker Uploading 3.6K, 3 files Done uploading OK

Starting app mathematics-broker-app in org DevBox / space gowri as admin... -----> Downloaded app package (4.0K) -------> Buildpack version 1.5.14 -----> Creating runtime environment NPM_CONFIG_LOGLEVEL=error NPM_CONFIG_PRODUCTION=true NODE_ENV=production NODE_MODULES_CACHE=true -----> Installing binaries engines.node (package.json): unspecified engines.npm (package.json): unspecified (use default) Downloading and installing node 4.4.4... Downloaded [file:///var/vcap/data/dea_next/admin_buildpacks/0d2f5efa-e433-4991-bc26-01a3140193b5_ddfaa3b5c17aba2d9303306fb1fbae9aa2574b74/dependencies/https___pivotal-buildpacks.s3.amazonaws.com_concourse-binaries_node_node-4.4.4-linux-x64.tgz] Using default npm version: 2.15.1 -----> Restoring cache Skipping cache restore (new runtime signature) -----> Building dependencies Pruning any extraneous modules Installing node modules (package.json) npm ERR! Linux 4.2.0-27-generic npm ERR! argv "/tmp/staged/app/.heroku/node/bin/node" "/tmp/staged/app/.heroku/node/bin/npm" "install" "--unsafe-perm" "--userconfig" "/tmp/staged/app/.npmrc" npm ERR! node v4.4.4 npm ERR! npm v2.15.1 npm ERR! code ETIMEDOUT npm ERR! errno ETIMEDOUT npm ERR! syscall connect npm ERR! network connect ETIMEDOUT 151.101.12.162:443 npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is 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! Please include the following file with any support request: npm ERR! /tmp/staged/app/npm-debug.log -----> Build failed We're sorry this build is failing! You can troubleshoot common issues here: https://devcenter.heroku.com/articles/troubleshooting-node-deploys Some possible problems:

FAILED BuildpackCompileFailed

TIP: use 'cf logs mathematics-broker-app --recent' for more information

C:\Gowrisankar_backupfiles\2016\Learning_OS_CF_DOC\CloudFoundry\techtalks-demo\mathematics-service-broker>cf logs mathematics-broker-app --recent Connected, dumping recent logs for app mathematics-broker-app in org DevBox / space gowri as admin...

2016-07-23T08:46:23.75+0530 [API/0] OUT Created app with guid 2fb0add0-3da3-49f6-81b9-0305ab6fde88 2016-07-23T08:46:29.84+0530 [API/0] OUT Updated app with guid 2fb0add0-3da3-49f6-81b9-0305ab6fde88 ({"route"=>"710c608e-1092-4a4e-8115-6b257e29cfa2"}) 2016-07-23T08:46:36.43+0530 [DEA/0] OUT Got staging request for app with id 2fb0add0-3da3-49f6-81b9-0305ab6fde88 2016-07-23T08:46:37.56+0530 [API/0] OUT Updated app with guid 2fb0add0-3da3-49f6-81b9-0305ab6fde88 ({"state"=>"STARTED"}) 2016-07-23T08:46:37.61+0530 [STG/0] OUT -----> Downloaded app package (4.0K) 2016-07-23T08:46:38.27+0530 [STG/0] OUT -------> Buildpack version 1.5.14 2016-07-23T08:46:38.29+0530 [STG/0] OUT -----> Creating runtime environment 2016-07-23T08:46:38.29+0530 [STG/0] OUT NPM_CONFIG_LOGLEVEL=error 2016-07-23T08:46:38.29+0530 [STG/0] OUT NPM_CONFIG_PRODUCTION=true 2016-07-23T08:46:38.29+0530 [STG/0] OUT NODE_ENV=production 2016-07-23T08:46:38.29+0530 [STG/0] OUT NODE_MODULES_CACHE=true 2016-07-23T08:46:38.29+0530 [STG/0] OUT -----> Installing binaries 2016-07-23T08:46:38.30+0530 [STG/0] OUT engines.node (package.json): unspecified 2016-07-23T08:46:38.30+0530 [STG/0] OUT engines.npm (package.json): unspecified (use default) 2016-07-23T08:46:38.43+0530 [STG/0] OUT Downloading and installing node 4.4.4... 2016-07-23T08:46:38.57+0530 [STG/0] OUT Downloaded [file:///var/vcap/data/dea_next/admin_buildpacks/0d2f5efa-e433-4991-bc26-01a3140193b5_ddfaa3b5c17aba2d9303306fb1fbae9aa2574b74/dependencies/https___pivotal-buildpacks.s3.amazonaws.com_concourse-binaries_node_node-4.4.4-linux-x64.tgz] 2016-07-23T08:46:39.27+0530 [STG/0] OUT Using default npm version: 2.15.1 2016-07-23T08:46:39.50+0530 [STG/0] OUT -----> Restoring cache 2016-07-23T08:46:39.71+0530 [STG/0] OUT Skipping cache restore (new runtime signature) 2016-07-23T08:46:39.71+0530 [STG/0] OUT -----> Building dependencies 2016-07-23T08:46:39.71+0530 [STG/0] OUT Pruning any extraneous modules 2016-07-23T08:46:40.21+0530 [STG/0] OUT Installing node modules (package.json) 2016-07-23T08:54:12.91+0530 [STG/0] OUT npm ERR! Linux 4.2.0-27-generic 2016-07-23T08:54:12.91+0530 [STG/0] OUT npm ERR! argv "/tmp/staged/app/.heroku/node/bin/node" "/tmp/staged/app/.heroku/node/bin/npm" "install" "--unsafe-perm" "--userconfig" "/tmp/staged/app/.npmrc" 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! node v4.4.4 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! npm v2.15.1 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! code ETIMEDOUT 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! errno ETIMEDOUT 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! syscall connect 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! network connect ETIMEDOUT 151.101.12.162:443 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! network This is most likely not a problem with npm itself 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! network and is related to network connectivity. 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! network In most cases you are behind a proxy or have bad network settings. 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! network 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! network If you are behind a proxy, please make sure that the 2016-07-23T08:54:12.92+0530 [STG/0] OUT npm ERR! network 'proxy' config is set properly. See: 'npm help config' 2016-07-23T08:54:12.93+0530 [STG/0] OUT npm ERR! Please include the following file with any support request: 2016-07-23T08:54:12.93+0530 [STG/0] OUT npm ERR! /tmp/staged/app/npm-debug.log 2016-07-23T08:54:12.93+0530 [STG/0] OUT -----> Build failed 2016-07-23T08:54:12.94+0530 [STG/0] OUT We're sorry this build is failing! You can troubleshoot common issues here: 2016-07-23T08:54:12.94+0530 [STG/0] OUT https://devcenter.heroku.com/articles/troubleshooting-node-deploys 2016-07-23T08:54:12.94+0530 [STG/0] OUT Some possible problems: 2016-07-23T08:54:12.94+0530 [STG/0] OUT - Node version not specified in package.json 2016-07-23T08:54:12.94+0530 [STG/0] OUT http://docs.cloudfoundry.org/buildpacks/node/node-tips.html 2016-07-23T08:54:12.94+0530 [STG/0] OUT Love, 2016-07-23T08:54:12.94+0530 [STG/0] OUT Heroku 2016-07-23T08:54:12.95+0530 [STG/0] OUT Staging failed: Buildpack compilation step failed 2016-07-23T08:54:12.95+0530 [STG/0] ERR 2016-07-23T08:54:13.06+0530 [API/0] ERR encountered error: App staging failed in the buildpack compile phase