Installation failure on Linux when process.execPath is relative

[bobbwal]

I've been through the troubleshooting but no node-sass/vendor folder is created so that's as far as I can go. Here's my output https://gist.github.com/bobbwal/f4ce61210ff88d9f9f85

Thanks

[bobbwal]

Also the server is running Ash shell, not sure if this could be a problem. I noticed this comment in another issue:
"npm install executes a normal shell and tells it to run node scripts/install.js. If it can't find node (or this is some kind of funky restricted shell), things won't work."

[saper]

bash is by no means mandatory; I am using FreeBSD's /bin/sh without any issues. The shell needs to understand sh -c convention and be able to find node interpreter using PATH environmental variable. What is your SHELL set to? Does /bin/sh -c node invoke your node interpreter? Maybe some shell startup scripts are causing issues (like changing the current directory)?

[bobbwal]

Hi, I'm guessing that command invokes the interpreter, no errors.

$ echo $SHELL
/bin/ash

$ /bin/sh -c node
>

[saper]

@bobbwal is /bin/sh and /bin/ash the same binary? Does it help if you try bash? Is the current directory symlinked?

[bobbwal]

/bin/sh and /bin/ash are identical but I'm not sure what this means. Bash is not installed but I can have a statically compiled bash added on request. The directory is symlinked www -> /www

[saper]

This symlink is interesting - can you elaborate more on the directory structure used? Where is your node_modules directory? Is this some well-known hosting environment (maybe there are public accounts to test and try to reproduce the issue)?

[saper]

What is your process.execPath ?

[saper]

Can you try running the following snippet under your node:

var fs=require('fs'); console.log(process.execPath); console.log(fs.lstatSync(process.execPath)); fs.realpathSync(process.execPath);

[bobbwal]

Here you go:

> var fs=require('fs'); console.log(process.execPath); console.log(fs.lstatSync(process.execPath)); fs.realpathSync(process.execPath);
node
Error: ENOENT: no such file or directory, lstat 'node'
    at Error (native)
    at Object.fs.lstatSync (fs.js:839:18)
    at repl:1:69
    at REPLServer.defaultEval (repl.js:248:27)
    at bound (domain.js:280:14)
    at REPLServer.runBound [as eval] (domain.js:293:12)
    at REPLServer.<anonymous> (repl.js:412:12)
    at emitOne (events.js:82:20)
    at REPLServer.emit (events.js:169:7)
    at REPLServer.Interface._onLine (readline.js:210:10)
>

Directory structure (only included the stuff I thought was relevant):

root
├── bin
├── www
│   └── node_modules
└── home
    ├── .gem
    ├── .npm
    ├── .npmi
    ├── .ssh -> /.ssh
    ├── log -> /log
    └── www -> /www

[saper]

Do you know why your process.execPath is relative? where is your node really located?

[saper]

Do you have /proc filesystem available? What does ls -lF /proc/self/exe do when executed from the shell?

[saper]

This is most probably caused by https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt

Non-standard behavior

(...)

Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory
object in overlayfs will not contain valid absolute paths, only
relative paths leading up to the filesystem's root. This will be
fixed in the future.

(kudos to https://gist.github.com/shimarin/5c1833dcbb3ea4c04256#gistcomment-1546393)

[xzyfer]

Sounds like this should be fixed by #1322.

[saper]

Don't think so, as this is the problem occurring in our installer, not the CLI. The fix will be simple once we fully understand the issue.

[bobbwal]

Hi, not really sure about the /proc file system, appears not?

$ ls -lF /proc/self/exe
ls: /proc/self/exe: No such file or directory

[saper]

Hi, not really sure about the `/proc` file system, appears not?

Is there a `mount` command you can possibly run?

[bobbwal]

Struggling a little on this but mount doesn't appear to be an available command.

[saper]

@bobbwal can you check if #1325 fixes this for you?

[bobbwal]

can you check if #1325 fixes this for you?

@saper it works!

[saper]

Happy to hear that! Thank you for helping us to locate this issue .... and lots of luck working in your ehm environment :)

[bobbwal]

Thanks, and good work :)

[xzyfer]

This fix is on master and will be the next release.