Build Zeppelin for Spark 1.5 on OSX

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Build Zeppelin for Spark 1.5 on OSX

Mariano Kamp
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


Reply | Threaded
Open this post in threaded view
|

Re: Build Zeppelin for Spark 1.5 on OSX

Alexander Bezzubov
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 <[hidden email]> 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.

Reply | Threaded
Open this post in threaded view
|

Re: Build Zeppelin for Spark 1.5 on OSX

Corneau Damien
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 <[hidden email]> 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 <[hidden email]> 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.


Reply | Threaded
Open this post in threaded view
|

Re: Build Zeppelin for Spark 1.5 on OSX

Mariano Kamp
In reply to this post by Alexander Bezzubov
Thank you Alex.

Zeppelin looks awesome.

It seems to also fail manually: 

snow:incubator-zeppelin mkamp$ cd zeppelin-web/

snow:zeppelin-web mkamp$ ./grunt 

Running "newer:jshint" (newer) task


Running "newer:jshint:all" (newer) task

No newer files to process.


Running "newer:jshint:test" (newer) task

No newer files to process.


Running "clean:server" (clean) task

Cleaning .tmp...OK


Running "wiredep:app" (wiredep) task


Running "wiredep:test" (wiredep) task


Running "concurrent:test" (concurrent) task

    

    Running "copy:styles" (copy) task

    Copied 6 files

    

    Done, without errors.

    

    

    Execution Time (2015-09-18 05:25:56 UTC)

    loading tasks   3ms  ▇▇▇▇▇▇ 11%

    copy:styles    23ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 85%

    Total 27ms

    

Running "autoprefixer:dist" (autoprefixer) task

File .tmp/styles/custom-font.css created.

File .tmp/styles/font-awesome.min.css created.

File .tmp/styles/home.css created.

File .tmp/styles/interpreter.css created.

File .tmp/styles/notebook.css created.

File .tmp/styles/simple-line-icons.css created.


Running "connect:test" (connect) task

Started connect web server on http://localhost:9001


Running "karma:unit" (karma) task

INFO [karma]: Karma v0.12.37 server started at http://localhost:8080/

INFO [launcher]: Starting browser PhantomJS

WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.

INFO [launcher]: Trying to start PhantomJS again (1/2).

WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.

INFO [launcher]: Trying to start PhantomJS again (2/2).

WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.

ERROR [launcher]: PhantomJS failed 2 times (timeout). Giving up.

Warning: Task "karma:unit" failed. Use --force to continue.


Aborted due to warnings.



Execution Time (2015-09-18 05:25:54 UTC)

karma:unit     3m 0.2s  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 99%

Total 3m 2.7s


snow:zeppelin-web mkamp$


On Fri, Sep 18, 2015 at 5:16 AM Alexander Bezzubov <[hidden email]> 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 <[hidden email]> 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.

Reply | Threaded
Open this post in threaded view
|

Re: Build Zeppelin for Spark 1.5 on OSX

Mariano Kamp
In reply to this post by Corneau Damien
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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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.


Reply | Threaded
Open this post in threaded view
|

Re: Build Zeppelin for Spark 1.5 on OSX

Alexander Bezzubov
Good to know, thank you for sharing, 
may be it worth changing defaults to a different port, which has less probability of being busy.

Wish you a good luck for your further research!

--
Kind regards,
Alexander

On 18 Sep 2015, at 15:08, Mariano Kamp <[hidden email]> wrote:

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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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.


Reply | Threaded
Open this post in threaded view
|

Re: Build Zeppelin for Spark 1.5 on OSX

madhuka udantha
In reply to this post by Mariano Kamp
(grunt test) karma is able to pick next port (off set will be +1)  if default port (8080) is used. 

some case karma is not able to find that port 8080 is busy. (not sure how mac os handle it)

Wish you all the best for your next steps. 
--
Reply | Threaded
Open this post in threaded view
|

Re: Build Zeppelin for Spark 1.5 on OSX

Randy Gelhausen-2
I'm running into the same problem. I'm also using -DskipTests, so I'm not sure why karma tests are even running.

Is this something that can be fixed in some way?

On Fri, Sep 18, 2015 at 2:36 AM, madhuka udantha <[hidden email]> wrote:
(grunt test) karma is able to pick next port (off set will be +1)  if default port (8080) is used. 

some case karma is not able to find that port 8080 is busy. (not sure how mac os handle it)

Wish you all the best for your next steps. 
--

Reply | Threaded
Open this post in threaded view
|

Re: Build Zeppelin for Spark 1.5 on OSX

Randy Gelhausen-2
I was able to get the build to complete by changing the port in test/karma.conf.js.

Since it starts a server successfully on 9001, I edited the PhantomJS port to use 9002. There will still be an issue if OSX user has a running process listening on port 9002, but at least this is less common than 8080.

I'm creating an issue and PR to address this shortly.

On Sat, Sep 26, 2015 at 2:36 PM, Randy Gelhausen <[hidden email]> wrote:
I'm running into the same problem. I'm also using -DskipTests, so I'm not sure why karma tests are even running.

Is this something that can be fixed in some way?

On Fri, Sep 18, 2015 at 2:36 AM, madhuka udantha <[hidden email]> wrote:
(grunt test) karma is able to pick next port (off set will be +1)  if default port (8080) is used. 

some case karma is not able to find that port 8080 is busy. (not sure how mac os handle it)

Wish you all the best for your next steps. 
--