(node-gyp rebuild 2> builderror.log) || (exit 0) #1126

ghost · 2013-01-04T04:36:25Z

# npm install socket.io
npm http GET https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/base64id/0.1.0
npm http GET https://registry.npmjs.org/redis/0.7.3
npm http GET https://registry.npmjs.org/socket.io-client/0.9.11
npm http GET https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/base64id/0.1.0
npm http 304 https://registry.npmjs.org/redis/0.7.3
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/socket.io-client/0.9.11
npm http GET https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http GET https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/ws
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http 304 https://registry.npmjs.org/ws
npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/zeparser/0.0.5
npm http GET https://registry.npmjs.org/options
npm http GET https://registry.npmjs.org/tinycolor
npm http GET https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/zeparser/0.0.5
npm http 304 https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/tinycolor
npm http 304 https://registry.npmjs.org/commander

> ws@0.4.25 install /root/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

socket.io@0.9.13 node_modules/socket.io
├── base64id@0.1.0
├── policyfile@0.0.4
├── redis@0.7.3
└── socket.io-client@0.9.11 (xmlhttprequest@1.4.2, uglify-js@1.2.5, ws@0.4.25, active-x-obfuscator@0.0.1)

The text was updated successfully, but these errors were encountered:

ghost · 2013-01-04T04:38:48Z

Hack Trick work:

# cd ~
# npm install -g node-gyp
# npm install socket.io

https://github.com/TooTallNate/node-gyp#readme

eupharis · 2013-01-27T19:00:54Z

I too had this issue. Using Ubuntu 12.04.

I fixed it by removing all the testacular installs from my system (both as user and superuser) and deleting all the symlinks.

Then I did the manual install steps:

replace x.y.z with latest version

$ curl http://registry.npmjs.org/testacular/-/testacular-x.y.z.tgz | tar -xvz && mv package testacular

create symlinks (optional)

$ cd testacular
$ sudo ln -s $PWD/bin/testacular /usr/local/bin/testacular

Works great.

Is the problem with testacular's installation of socket.io in npm, rather than socket.io itself?

apptous-max · 2013-01-28T14:30:04Z

I had the same problem when installing node-inspector (Ubuntu 12.04):


...
npm http 304 https://registry.npmjs.org/tinycolor
> ws@0.4.25 install /usr/lib/node_modules/node-inspector/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)
make: Вход в каталог `/usr/lib/node_modules/node-inspector/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node: Finished
  COPY Release/bufferutil.node
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/obj.target/validation.node
  SOLINK_MODULE(target) Release/obj.target/validation.node: Finished
  COPY Release/validation.node
make: Выход из каталога `/usr/lib/node_modules/node-inspector/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build'
/usr/bin/node-inspector -> /usr/lib/node_modules/node-inspector/bin/inspector.js
node-inspector@0.2.0beta3 /usr/lib/node_modules/node-inspector
├── async@0.1.22
├── connect@1.8.7 (mime@1.2.9, formidable@1.0.11, qs@0.5.3)
└── socket.io@0.9.13 (base64id@0.1.0, policyfile@0.0.4, redis@0.7.3, socket.io-client@0.9.11)

3rd-Eden · 2013-01-28T14:35:07Z

I don't see any error here, it's an optional build step for WS so it do some faster buffer stuff. All the installations are correct without any errors.

If you would like to see this resolved, open an issue in the correct repo and that is over at github.com/einaros/ws

marols · 2013-02-03T16:06:30Z

Same issue fo me on OS X Lion 10.7.5. The following solved it for me (almost same as @PGBI)

cd ~

npm install -g node-gyp

npm install -g socket.io

a9entropy · 2013-02-09T12:27:19Z

I get the same error as @PGBI. I am on Ubuntu 12.04

mindaslab · 2013-02-13T10:53:12Z

Got this error using Ubuntu 12.10 , hasn't node got any dependency management like .deb files or something?

cowboybkit · 2013-02-23T09:18:48Z

Not work with me. Cannot install

jakobloekke · 2013-03-01T10:52:03Z

I have this issue as well. None of the mentioned tricks seem to resolve it.

3rd-Eden · 2013-03-01T11:46:12Z

As I said before, the logs that are posted here show no error. The compilation is an OPTIONAL step, the ws module will still be correctly installed when it fails to compile.

jewelsjacobs · 2013-03-19T22:36:07Z

Just an FYI, if your on Windows you can install this error free by following the instructions on running node-gyp for Windows: https://github.com/TooTallNate/node-gyp/wiki/Visual-Studio-2010-Setup

Otherwise the install will barf when building node-gyp.

rogerz · 2013-03-24T11:16:29Z

The same error on Ubuntu 12.10. It stopped in postinstall active-x-obfuscator@0.0.1

npm install --verbose socket.io

npm verb about to build /usr/lib/node_modules/node-inspector/node_modules/socket.io/node_modules/socket.io-client/node_modules/active-x-obfuscator
npm info build /usr/lib/node_modules/node-inspector/node_modules/socket.io/node_modules/socket.io-client/node_modules/active-x-obfuscator
npm verb from cache /usr/lib/node_modules/node-inspector/node_modules/socket.io/node_modules/socket.io-client/node_modules/active-x-obfuscator/package.json
npm verb linkStuff [ true,
npm verb linkStuff   '/usr/lib/node_modules',
npm verb linkStuff   false,
npm verb linkStuff   '/usr/lib/node_modules/node-inspector/node_modules/socket.io/node_modules/socket.io-client/node_modules' ]
npm info linkStuff active-x-obfuscator@0.0.1
npm verb linkBins active-x-obfuscator@0.0.1
npm verb linkMans active-x-obfuscator@0.0.1
npm verb rebuildBundles active-x-obfuscator@0.0.1
npm verb rebuildBundles [ 'zeparser' ]
npm info install active-x-obfuscator@0.0.1
npm info postinstall active-x-obfuscator@0.0.1

deanshelton913 · 2013-04-18T18:53:26Z

Also have issue when installing Karma (which testacular was renamed to) https://github.com/karma-runner/karma.

npm install -g karma
...
....huge list of packages...
...

npm http 304 https://registry.npmjs.org/amdefine
npm http 304 https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/tinycolor

> ws@0.4.25 install /Users/<myusername>/.rvm/share/npm/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished
/Users/<myusername>/.rvm/share/npm/bin/karma -> /Users/<myusername>/.rvm/share/npm/lib/node_modules/karma/bin/karma
karma@0.8.5 /Users/<myusername>/.rvm/share/npm/lib/node_modules/karma
├── pause@0.0.1
├── dateformat@1.0.2-1.2.3
├── xmlbuilder@0.4.2
├── colors@0.6.0-1
├── chokidar@0.6.2
├── growly@1.1.1
├── mime@1.2.9
├── q@0.9.3
├── coffee-script@1.6.2
├── rimraf@2.1.4 (graceful-fs@1.2.0)
├── optimist@0.3.5 (wordwrap@0.0.2)
├── glob@3.1.21 (inherits@1.0.0, graceful-fs@1.2.0)
├── LiveScript@1.0.1 (prelude-ls@0.6.0)
├── lodash@1.1.1
├── log4js@0.6.3 (dequeue@1.0.3, semver@1.1.4, async@0.1.15, readable-stream@1.0.2)
├── minimatch@0.2.12 (sigmund@1.0.0, lru-cache@2.3.0)
├── http-proxy@0.10.1 (pkginfo@0.2.3, utile@0.1.7)
├── istanbul@0.1.22 (abbrev@1.0.4, which@1.0.5, fileset@0.1.5, nopt@2.0.0, wordwrap@0.0.2, async@0.1.22, mkdirp@0.3.5, esprima@0.9.9, handlebars@1.0.10, escodegen@0.0.21)
└── socket.io@0.9.14 (base64id@0.1.0, policyfile@0.0.4, redis@0.7.3, socket.io-client@0.9.11)
<myusername> in ~/development_area/angular-testbed/angular-phonecat on (step-2) %

3rd-Eden · 2013-04-18T19:50:46Z

I'm just gonna gently post this again.

There is no error, if you would have actually read the stack trace and checked the result you should have seen that socket.io is installed.

jackbillstrom · 2013-05-08T05:43:24Z

My console says the exact same thing as the opening post. When I try "node server.js" om my appliction, and opens the localhost:PORT in my browser, my browser just keeps on loading and nothing really shows up. As if I would connect to a really slow server :/

d4tech · 2013-06-06T05:30:04Z

Got the same issue,while trying to install node-inspector on OSX:10.8.3 fixed it by:
1)npm install -g node-gyp
2)git clone https://github.com/einaros/ws.git
3)npm install
4)npm install ws
5)npm install -g node-inspector

vlad-shatskyi · 2014-01-23T14:16:05Z

In my case it happened because I had python 3.3, which isn't supported. There is a parameter --python to node-gyp which you can point to your python2, but I simply renamed /usr/bin/python2 to python temporarily.

bcherny · 2014-11-02T03:55:39Z

Issue persists on centos, @ghost and @marols's fixes do not work. Here's my Dockerfile that reliably reproduces it:

# DOCKER-VERSION 1.1.2
FROM centos:latest

# install nodejs
RUN yum -y update
RUN yum groupinstall -y "Development Tools"
RUN curl -sL https://rpm.nodesource.com/setup | bash -
RUN yum install -y nodejs

# install git
RUN yum install -y git

# bundle
COPY . home

# install deps
WORKDIR home
RUN npm install

# expose a port
EXPOSE 3000

# start the app
CMD npm start

kaishin · 2014-12-31T14:14:09Z

@3rd-Eden If it's not an error then I don't need to see it.

3rd-Eden · 2015-01-01T11:26:13Z

@kaishin Then you should turn off logging while installing modules as npm decides what to show and what not to show.

Injac · 2015-01-01T17:44:53Z

@3rd-Eden Glad it is not an error. Installed node 0.10.35 on my Galileo and tried to install socket.io as well (and I am a starter, not much experience). That got me confused a bit. But thanks for the clarification.

barneycarroll · 2015-02-18T15:54:49Z

'Not an error' is fair enough and a lot of these logs don't describe any real world problem, but I've got my build executing in Docker like @bcherny – intermittently the Docker boot process goes into an infinite loop immediately after logging the line in the title.

barneycarroll · 2015-02-18T16:06:11Z

FYI in my case it turns out socket.io is just one of several packages whose optional native dependencies crash Docker in certain combinations with other native dependencies being installed concurrently by NPM. So those who are actually suffering from a crash might be looking for this NPM bug.

intec-co · 2015-02-22T18:13:44Z

I solved the error in Ubuntu 14.04 with
apt-get install nodejs-legancy

danielreisti · 2015-03-10T14:07:32Z

In my mac, install xcode solved the problem.

ghost · 2015-03-22T21:33:11Z

on ubuntu 14.04 I needed to create a link in /usr/bin because /usr/bin/env was looking for /usr/bin/node

ln -s /usr/bin/nodejs /usr/bin/node

3rd-Eden closed this as completed Jan 28, 2013

This was referenced Feb 19, 2013

It has stopped working! instant-markdown/vim-instant-markdown#24

Closed

Just doesn't do anything instant-markdown/vim-instant-markdown#25

Closed

shakyShane mentioned this issue Feb 20, 2014

npm update BrowserSync/browser-sync#75

Closed

maxfadeev pushed a commit to yegor86/my-cloud-client that referenced this issue Sep 23, 2015

Fix Dockerfile to get round socketio/socket.io#1126

cd09a00

lopelex mentioned this issue Feb 1, 2020

Unable to update to 2.2.1 lopelex/node-red-contrib-harmony#9

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

(node-gyp rebuild 2> builderror.log) || (exit 0) #1126

(node-gyp rebuild 2> builderror.log) || (exit 0) #1126

ghost commented Jan 4, 2013

ghost commented Jan 4, 2013

eupharis commented Jan 27, 2013

replace x.y.z with latest version

create symlinks (optional)

apptous-max commented Jan 28, 2013

3rd-Eden commented Jan 28, 2013

marols commented Feb 3, 2013

a9entropy commented Feb 9, 2013

mindaslab commented Feb 13, 2013

cowboybkit commented Feb 23, 2013

jakobloekke commented Mar 1, 2013

3rd-Eden commented Mar 1, 2013

jewelsjacobs commented Mar 19, 2013

rogerz commented Mar 24, 2013

deanshelton913 commented Apr 18, 2013

3rd-Eden commented Apr 18, 2013

jackbillstrom commented May 8, 2013

d4tech commented Jun 6, 2013

vlad-shatskyi commented Jan 23, 2014

bcherny commented Nov 2, 2014

kaishin commented Dec 31, 2014

3rd-Eden commented Jan 1, 2015

Injac commented Jan 1, 2015

barneycarroll commented Feb 18, 2015

barneycarroll commented Feb 18, 2015

intec-co commented Feb 22, 2015

danielreisti commented Mar 10, 2015

ghost commented Mar 22, 2015

(node-gyp rebuild 2> builderror.log) || (exit 0) #1126

(node-gyp rebuild 2> builderror.log) || (exit 0) #1126

Comments

ghost commented Jan 4, 2013

ghost commented Jan 4, 2013

eupharis commented Jan 27, 2013

replace x.y.z with latest version

create symlinks (optional)

apptous-max commented Jan 28, 2013

3rd-Eden commented Jan 28, 2013

marols commented Feb 3, 2013

cd ~

npm install -g node-gyp

npm install -g socket.io

a9entropy commented Feb 9, 2013

mindaslab commented Feb 13, 2013

cowboybkit commented Feb 23, 2013

jakobloekke commented Mar 1, 2013

3rd-Eden commented Mar 1, 2013

jewelsjacobs commented Mar 19, 2013

rogerz commented Mar 24, 2013

deanshelton913 commented Apr 18, 2013

3rd-Eden commented Apr 18, 2013

jackbillstrom commented May 8, 2013

d4tech commented Jun 6, 2013

vlad-shatskyi commented Jan 23, 2014

bcherny commented Nov 2, 2014

kaishin commented Dec 31, 2014

3rd-Eden commented Jan 1, 2015

Injac commented Jan 1, 2015

barneycarroll commented Feb 18, 2015

barneycarroll commented Feb 18, 2015

intec-co commented Feb 22, 2015

danielreisti commented Mar 10, 2015

ghost commented Mar 22, 2015