[ZEPPELIN-380] node version pulled during build of zeppelin-web segfaults on pure 64bit system

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Labels: build maven node.js

Environment

64 bit kernel with no multilib environment, Gentoo.

• Assignee: Unassigned
• Reporter: Rick Moritz
• Created: 31/Oct/15 15:32
• Updated: 10/Feb/17 12:56
• Resolved: 10/Feb/17 12:56

Description

The node version that gets pulled in during mvn build reproducably segfaults when trying to run npm.
The installer also always downloads this specific version, when I try to use the locally built - and working - version (0.12) instead.

While I talked with Damien in Amsterdam about the fact that shipping node with Zeppelin is important, it has to be a version that runs on the underlying OS.

strace says, that node fails on
mmap(0x2df5b5c6000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = -1 EPERM (Operation not permitted)
munmap(0x2df5b5c6000, 4096) = 0
mmap(0x1e5e7515000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 EPERM (Operation not permitted)

I will see if I find a working node version, but I wonder why we overwrite a working version with a failing one.

Issue Links

• duplicates: ZEPPELIN-1928 Get a rid of preinstalled external dependencies (nodejs and npm) for maven build