Installation Fails on Ubuntu with tunneling socket could not be established #705
Comments
|
@DVG, please show the output of: # you may need to prefix these with `sudo`:
$ mkdir /temp; cd /temp
$ npm install npmconf
$ nodethen: // This is node.js REPL
// The following code is extracted from node-sass/scripts/install.js#applyProxy
// just copy/paste the whole thing in shell at once
require('npmconf').load({}, function (er, conf) {
var options = {};
var proxyUrl;
if (!er) {
proxyUrl = conf.get('https-proxy') ||
conf.get('proxy') ||
conf.get('http-proxy');
}
var env = process.env;
options.proxy = proxyUrl ||
env.HTTPS_PROXY ||
env.https_proxy ||
env.HTTP_PROXY ||
env.http_proxy;
console.log(options);
}); after exiting the REPL: # final cleanup
rm -r /temp |
|
@DVG could you also supply a gist with the output of the following two commands and |
|
The result of your script is:
|
|
|
|
So I've done some experimenting on a fork, and I can get past the tunneling socket problem, however, the build.js script still fails on the node-gyp bit: |
|
For the record, the tunneling socket seemed sensitive to the trailing slash I had in my NPM config, which was the only difference between the NPM config and the shell-level HTTPS_PROXY variable. I don't really know if that sort of thing is something you even care about, but since it doesn't seem to matter for the average NPM package I wanted to mention it. |
|
I was able to install node-sass 1.1.4 with the proxy fix. I'm still unable to install the 2.0 line with the issues above, so I'm happy to keep helping figure out what's going on there. |
|
@DVG, excellent findings and glad to know that proxy issue is sorted out. 👍 Note that not all npm packages download binary in the installation step. However, since I am not sure if the trailing slash is something unnecessary in all proxy servers scenarios? If they all defy then it is the issue when npm config are set and should be reported to https://github.com/npm/npm/issues. The node-gyp step should not be triggered in first place for Ubuntu, since we are offering pre-build binary for Linux. To help us diagnose the issue, please make a gist showing the output of this set of commands: https://gist.github.com/am11/e5de3c49c219f0811e1d#comment-1386582. |
|
Here you go: https://gist.github.com/DVG/5c965dd371bbd03ff8fc |
|
@DVG, actually we have recently change the naming convention and it seems like you are installing node-sass from fork? Can you try installing it from the # tunneling issue was sorted out,
# now lets try a clean install:
sudo mkdir /temp
cd /temp
npm install node-sass
# success!
node -p "console.log(require('node-sass').renderSync({data:'a{b:c}'}))"
# some CSS output!
# cleanup
cd ~/
sudo rm -rf /tempAlso for the forked installation, try these steps: git clone https://github.com/dvg/nodess --recursive
cd node-sass
git remote add node-sass https://github.com/sass/node-sass
git pull --rebase node-sass master
git submodule --recursive --init
npm install
# the next one requires gcc/g++ v4.6+ and python 2.7.x
node scripts/build -f
# success!
node -p "console.log(require('./').renderSync({data:'a{b:c}'}))"
# ./ because you are in the node-sass directory |
|
From a fork? I don't think so. I did temporarily to experiment with the proxy code upstream (which is how I spotted the trailing slash thing), but since then have been only trying to install the official package In any case: |
|
Ah! you mentioned you were experimenting with fork, I thought the latter error is coming from there. The fact that pangyp is not available is because I made a big blunder by adding it under dev-dependencies as opposed to main dependencies. However, I have remedied it via this PR some 15 minutes ago: #717. :) But the most important thing is; it should NOT fallback to manual build step at all (where it requires pangyp), especially on Linux, Mac and Windows. It seems like either the binary is not successfully downloaded (for some network who-knows-what issue) OR it is not compatible with glibc; the latter one is very troubling because I tested all binaries on Ubuntu which I built on old CentOS (for backward compatibility) before releasing (and it is a big hassle!): vagrant@precise64:/temp/test-install$ uname -r
3.11.0-15-generic
vagrant@precise64:/temp/test-install$ cat /etc/issue
Ubuntu 12.04.5 LTS \n \lI have checked your logs again. You can try this approach: cd into/myFav/project/dir
wget https://github.com/sass/node-sass/archive/v2.0.1.tar.gz
tar zxvf v2.0.1.tar.gz
cd node-sass
npm install
# should not try to invoke manual build! but we can just hope..
node -p "console.log(require('./').renderSync({data:'a{b:c}'}))"
# unsuccessful! :(
rm -rf vendor/lin*
mkdir vendor/linux-x64-node-0.10
wget https://github.com/sass/node-sass-binaries/blob/v2.0.1/linux-x64-node-0.10/binding.node vendor/linux-x64-node-0.10
node -p "console.log(require('./').renderSync({data:'a{b:c}'}))"
# success! :) |
|
have exactly same issue with iojs 1.4.x (from nvm) on macos 10.10.2. I assume because of the absence of the compiled binaries? When is the pangyp fixing PR getting pushed to NPM? :) |
No. The issue is that you cannot download binary for io.js 1.4, because node-sass v2.0.1 does not support io.js v1.4 but only io.js v1.2. The OP was having issue with https-proxy, which was fixed. This issue was fixed by the OP. For separate issues, please search the issue tracker and if there is no issue reported as yours, feel free to report one. |
When running npm install node-sass@2.0.1 --save-dev. it fails with the following error:
We are behind a proxy, but this is the only NPM package I've encountered that won't install with our configuration/
I've gotten a few older versions to install with a precompiled binary, but it still can't seem to find the libsass bindings and recommends reinstalling node-sass.
The text was updated successfully, but these errors were encountered: