CODEWITHSUNDEEP
mavenbuildcloudera-cdhapache-zeppelin
DharaPPatel
DharaPPatel

Reputation: 12753

Getting error while building the Apache Zeppelin

I have my hadoop already setup with cloudera. I wanted to install zeppelin to connect with hive and build the UI for my queries. While building the zeppelin command with the following command: 

sudo mvn clean package -Pspark-1.3 -Dspark.version=1.3.0 -Dhadoop.version=2.6.0-cdh5.4.7 -Phadoop-2.6 -Pyarn -DskipTests

I get this error at the web-application module :

[ERROR] npm ERR! Linux 3.19.0-71-generic
[ERROR] npm ERR! argv "/home/zeppelin/incubator-zeppelin/zeppelin-web/node/node" "/home/zeppelin/incubator-zeppelin/zeppelin-web/node/node_modules/npm/bin/npm-cli.js" "run" "build"
[ERROR] npm ERR! node v4.6.2
[ERROR] npm ERR! npm  v3.10.9
[ERROR] npm ERR! code ELIFECYCLE
[ERROR] npm ERR! [email protected] build: `grunt build`
[ERROR] npm ERR! Exit status 3
[ERROR] npm ERR!
[ERROR] npm ERR! Failed at the [email protected] build script 'grunt build'.
[ERROR] npm ERR! Make sure you have the latest version of node.js and npm installed.
[ERROR] npm ERR! If you do, this is most likely a problem with the zeppelin-web package,
[ERROR] npm ERR! not with npm itself.
[ERROR] npm ERR! Tell the author that this fails on your system:
[ERROR] npm ERR!     grunt build
[ERROR] npm ERR! You can get information on how to open an issue for this project with:
[ERROR] npm ERR!     npm bugs zeppelin-web
[ERROR] npm ERR! Or if that isn't available, you can get their info via:
[ERROR] npm ERR!     npm owner ls zeppelin-web
[ERROR] npm ERR! There is likely additional logging output above.
[ERROR]
[ERROR] npm ERR! Please include the following file with any support request:
[ERROR] npm ERR!     /home/zeppelin/incubator-zeppelin/zeppelin-web/npm-debug.log
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin ........................................... SUCCESS [  2.527 s]
[INFO] Zeppelin: Interpreter .............................. SUCCESS [  6.355 s]
[INFO] Zeppelin: Zengine .................................. SUCCESS [  3.253 s]
[INFO] Zeppelin: Display system apis ...................... SUCCESS [  9.241 s]
[INFO] Zeppelin: Spark dependencies ....................... SUCCESS [ 16.473 s]
[INFO] Zeppelin: Spark .................................... SUCCESS [ 13.479 s]
[INFO] Zeppelin: Markdown interpreter ..................... SUCCESS [  0.270 s]
[INFO] Zeppelin: Angular interpreter ...................... SUCCESS [  0.162 s]
[INFO] Zeppelin: Shell interpreter ........................ SUCCESS [  0.211 s]
[INFO] Zeppelin: Livy interpreter ......................... SUCCESS [  2.485 s]
[INFO] Zeppelin: HBase interpreter ........................ SUCCESS [  1.742 s]
[INFO] Zeppelin: Apache Pig Interpreter ................... SUCCESS [  1.367 s]
[INFO] Zeppelin: PostgreSQL interpreter ................... SUCCESS [  0.294 s]
[INFO] Zeppelin: JDBC interpreter ......................... SUCCESS [  0.565 s]
[INFO] Zeppelin: File System Interpreters ................. SUCCESS [  0.514 s]
[INFO] Zeppelin: Flink .................................... SUCCESS [  3.358 s]
[INFO] Zeppelin: Apache Ignite interpreter ................ SUCCESS [  0.367 s]
[INFO] Zeppelin: Kylin interpreter ........................ SUCCESS [  0.218 s]
[INFO] Zeppelin: Python interpreter ....................... SUCCESS [  0.252 s]
[INFO] Zeppelin: Lens interpreter ......................... SUCCESS [  1.496 s]
[INFO] Zeppelin: Apache Cassandra interpreter ............. SUCCESS [ 29.842 s]
[INFO] Zeppelin: Elasticsearch interpreter ................ SUCCESS [  1.322 s]
[INFO] Zeppelin: BigQuery interpreter ..................... SUCCESS [  0.389 s]
[INFO] Zeppelin: Alluxio interpreter ...................... SUCCESS [  1.106 s]
[INFO] Zeppelin: Scio ..................................... SUCCESS [ 23.182 s]
[INFO] Zeppelin: web Application .......................... FAILURE [  8.124 s]
[INFO] Zeppelin: Server ................................... SKIPPED
[INFO] Zeppelin: Packaging distribution ................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:09 min
[INFO] Finished at: 2016-11-28T18:16:15-05:00
[INFO] Final Memory: 524M/2992M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.3:npm (npm build) on project zeppelin-web: Failed to run task: 'npm run build' failed. (error code 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :zeppelin-web

Several Versions on my installations :

Hadoop 2.6.0-cdh5.4.7
java version "1.7.0_111"
Hive 1.1.0-cdh5.4.7
git version 1.9.1
nodejs - v7.2.0
npm - 3.10.9
Apache Maven 3.3.9 
Spark 1.3.0

I tried lot of ways to solve this issues but no luck. Can anybody please let me out to solve this issue and run the build successfully. I really appreciate your responses and time.

Edit

my npm install in zeppelin-web gives below output:

npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: the module is now available as 'css-select'
npm WARN deprecated [email protected]: the module is now available as 'css-what'
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: use uuid module instead
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g
npm WARN lifecycle [email protected]~postinstall: cannot run in wd %s %s (wd=%s) [email protected] bower install --silent /home/zeppelin/incubator-zeppelin/zeppelin-web
[email protected] /home/zeppelin/incubator-zeppelin/zeppelin-web

I haven't copied the tree here because it's too long to copy here. Thanks.

Upvotes: 0

Views: 1568

Answers (2)

Jarek
Jarek

Reputation: 209

Problem lies in the fact that zeppelin build has been updated to v0.6.2 Please add this after you clone your incubator:

  1. git clone https://github.com/apache/incubator-zeppelin.git
  2. cd incubator-zeppelin
  3. git checkout c928f9a46ecacebc868d6dc10a95c02f9018a18e
  4. cd ../

Maven will use zeppelin build 0.6.1 and it should finish without any error.

Upvotes: 2

HyungSung Shim
HyungSung Shim

Reputation: 96

Whenever i'm getting fail about web application, I used to follow procedure.

  1. cd zeppelin-web dir
  2. remove node_modules dir
  3. type npm install

and If you want to build Zeppelin with CDH, you should add -Pvendor-repo option in your build command.

You can see some Build command examples in here

Hope this helps.

Upvotes: 0

Related Questions