Thanks. It seems to fail every time. I googled a bit and found a couple of different causes. The short version is something was wrong on my machine and 8080 was already used and didn't lead to a good error message.
The longer version starts here: http://www.panozzaj.com/blog/2015/02/28/debugging-and-fixing-local-karma-phantomjs-issue/ When accessing 8080 from Chrome I get ERR_EMPTY_RESPONSE. Unfortunately I don't know what it is. The following commands don't return a result: netstat -a | grep LISTEN | grep 8080 lsof -n -i4TCP:8080 Ignoring the cause and just changing the port from 8080 to something else in zeppelin-web/test/karma.conf.js did work however. Now it got it build ;) Wish me luck for the next steps ;) Thanks. On Fri, Sep 18, 2015 at 6:00 AM Corneau Damien <cornead...@gmail.com> wrote: > This happened a few times recently (even on CI) > Running it manually in the folder always works, but tends to fails without > error (kinda time out) from maven. > You can try to clean and run it again > > On Fri, Sep 18, 2015 at 12:16 PM, Alexander Bezzubov <abezzu...@nflabs.com > > wrote: > >> Hi, >> >> thank you for interest in Zeppelin! >> >> It looks like frontend webapp build failed on executing the grunt task (a >> build system we use in web app). Can you try running it manually (instead >> of using maven) >> >> ``` >> cd zepelin-web >> ./grunt >> ``` >> >> and let me know if that works? >> >> It suppose to print smth like this at the end >> >> ``` >> Done, without errors. >> >> Execution Time (2015-09-18 03:12:36 UTC) >> jshint:all 616ms ▇▇▇ 2% >> wiredep:app 334ms ▇▇ 1% >> concurrent:test 1.3s ▇▇▇▇▇▇ 4% >> karma:unit 3.3s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 11% >> concurrent:dist 1.6s ▇▇▇▇▇▇▇▇ 6% >> ngAnnotate:dist 3.7s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 13% >> uglify:generated 17.1s >> >> ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ >> 59% >> Total 29s >> ``` >> >> -- >> Alex. >> >> On Fri, Sep 18, 2015 at 6:07 AM, Mariano Kamp <mariano.k...@gmail.com> >> wrote: >> >>> Hi. >>> >>> I am trying to install Zeppelin and so far this didn't work for me. >>> >>> I am sure this is just my own stupidity, but still could you please >>> point me in the right direction? >>> >>> I tried a couple of different things, but to make things simple I ran a >>> scenario again that I suspect should be fairly common: Starting from zero >>> and installing the current version of Zeppelin, Spark and Hadoop. >>> >>> >>> snow:~ mkamp$ git clone https://github.com/apache/incubator-zeppelin.git >>> && cd incubator-zeppelin/ && mvn clean package -X -Pspark-1.5 >>> -Dhadoop.version=2.6.0 -Phadoop-2.6 -DskipTests >>> ... >>> I get this result: >>> >>> [INFO] Reactor Summary: >>> >>> [INFO] >>> >>> [INFO] Zeppelin .......................................... SUCCESS >>> [7.798s] >>> >>> [INFO] Zeppelin: Interpreter ............................. SUCCESS >>> [15.299s] >>> >>> [INFO] Zeppelin: Zengine ................................. SUCCESS >>> [4.090s] >>> >>> [INFO] Zeppelin: Spark dependencies ...................... SUCCESS >>> [42.389s] >>> >>> [INFO] Zeppelin: Spark ................................... SUCCESS >>> [38.540s] >>> >>> [INFO] Zeppelin: Markdown interpreter .................... SUCCESS >>> [0.912s] >>> >>> [INFO] Zeppelin: Angular interpreter ..................... SUCCESS >>> [0.644s] >>> >>> [INFO] Zeppelin: Shell interpreter ....................... SUCCESS >>> [0.583s] >>> >>> [INFO] Zeppelin: Hive interpreter ........................ SUCCESS >>> [4.171s] >>> >>> [INFO] Zeppelin: Apache Phoenix Interpreter .............. SUCCESS >>> [7.083s] >>> >>> [INFO] Zeppelin: Apache Geode interpreter ................ SUCCESS >>> [4.097s] >>> >>> [INFO] Zeppelin: PostgreSQL interpreter .................. SUCCESS >>> [0.843s] >>> >>> [INFO] Zeppelin: Tajo interpreter ........................ SUCCESS >>> [1.055s] >>> >>> [INFO] Zeppelin: Flink ................................... SUCCESS >>> [10.731s] >>> >>> [INFO] Zeppelin: Apache Ignite interpreter ............... SUCCESS >>> [1.338s] >>> >>> [INFO] Zeppelin: Kylin interpreter ....................... SUCCESS >>> [0.763s] >>> >>> [INFO] Zeppelin: Lens interpreter ........................ SUCCESS >>> [3.754s] >>> >>> [INFO] Zeppelin: Cassandra ............................... SUCCESS >>> [1:02.923s] >>> >>> [INFO] Zeppelin: web Application ......................... FAILURE >>> [4:43.080s] >>> >>> [INFO] Zeppelin: Server .................................. SKIPPED >>> >>> [INFO] Zeppelin: Packaging distribution .................. SKIPPED >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> >>> [INFO] BUILD FAILURE >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> >>> [INFO] Total time: 8:11.183s >>> >>> [INFO] Finished at: Thu Sep 17 23:02:29 CEST 2015 >>> >>> [INFO] Final Memory: 162M/1712M >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> >>> [ERROR] Failed to execute goal >>> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt build) on >>> project zeppelin-web: Failed to run task: 'grunt --no-color' failed. (error >>> code 3) -> [Help 1] >>> >>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to >>> execute goal com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt >>> build) on project zeppelin-web: Failed to run task >>> >>> at >>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) >>> >>> at >>> >>> [...] >>> >>> ... 19 more >>> >>> Caused by: >>> com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'grunt >>> --no-color' failed. (error code 3) >>> >>> at >>> com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:38) >>> >>> at >>> com.github.eirslett.maven.plugins.frontend.mojo.GruntMojo.execute(GruntMojo.java:69) >>> >>> ... 21 more >>> >>> [ERROR] >>> >>> [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 >>> Many thanks. >>> >>> Mariano >>> >>> >>> >> >> >> -- >> -- >> Kind regards, >> Alexander. >> >> >
