Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Statsd package performs an npm install that requires internet connectivity #3

Open
bonzofenix opened this issue Aug 13, 2015 · 1 comment

Comments

@bonzofenix
Copy link

Error 450001: Action Failed get_task: Task 707c37fa-09e5-44fa-5215-f8bee11969d2 result: Compiling package statsd: Running packaging script: Command exited with 1; Stdout:
 , Stderr: + export PATH=/var/vcap/packages/node/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
+ PATH=/var/vcap/packages/node/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
+ tar -zxf statsd/statsd-0.7.2.tar.gz
+ cd statsd-0.7.2
+ npm install
npm WARN optional dep failed, continuing [email protected]
npm WARN optional dep failed, continuing winser@=0.1.6
npm WARN optional dep failed, continuing [email protected]
npm ERR! Linux 3.16.0-33-generic
npm ERR! argv "/var/vcap/packages/node/bin/node" "/var/vcap/packages/node/bin/npm" "install"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ETIMEDOUT
npm ERR! errno ETIMEDOUT
npm ERR! syscall connect

npm ERR! network connect ETIMEDOUT
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!     /var/vcap/data/compile/statsd/statsd-0.7.2/npm-debug.log

@teddyking
Copy link
Contributor

There should be a fix for this issue on the master branch (see here for the fix and here for context).

I'm aiming to get a concourse pipeline setup for this release soon, at which point I'll release the next version including the fix.

Thanks!
Ed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants