You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Rick Moritz (JIRA)" <ji...@apache.org> on 2015/10/31 16:33:27 UTC

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

Rick Moritz created ZEPPELIN-380:
------------------------------------

             Summary: node version pulled during build of zeppelin-web segfaults on pure 64bit system
                 Key: ZEPPELIN-380
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-380
             Project: Zeppelin
          Issue Type: Bug
         Environment: 64 bit kernel with no multilib environment, Gentoo.
            Reporter: Rick Moritz


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)