Hi All,

Apache Zeppelin still remains elusive.

I started the zeppelin daemon and opened in my browser at port 8080. I was
greeted with a blank white page. On viewing the browser console I found the
error message given below, I also tried different browsers so that is
eliminated.

Help me again please... the moment of happiness when I saw all success
during installation was short lived!!!

Error: [$injector:modulerr] Failed to instantiate module zeppelinWebApp due
to:
[$injector:modulerr] Failed to instantiate module ngTouch due to:
[$injector:nomod] Module 'ngTouch' is not available! You either misspelled
the module name or forgot to load it. If registering a module ensure that
you specify the dependencies as the second argument.
http://errors.angularjs.org/1.3.8/$injector/nomod?p0=ngTouch
d/<@http://localhost:8080/scripts/vendor.js:31:410
ka/</</<@http://localhost:8080/scripts/vendor.js:31:8675
b@http://localhost:8080/scripts/vendor.js:31:8247
ka/</<@http://localhost:8080/scripts/vendor.js:31:8559
n/<@http://localhost:8080/scripts/vendor.js:31:16993
f@http://localhost:8080/scripts/vendor.js:31:793
n@http://localhost:8080/scripts/vendor.js:31:16841
n/<@http://localhost:8080/scripts/vendor.js:31:17010
f@http://localhost:8080/scripts/vendor.js:31:793
n@http://localhost:8080/scripts/vendor.js:31:16841
Sa@http://localhost:8080/scripts/vendor.js:31:18503
_/h@http://localhost:8080/scripts/vendor.js:31:6427
_@http://localhost:8080/scripts/vendor.js:31:6737
$@http://localhost:8080/scripts/vendor.js:31:5986
@http://localhost:8080/scripts/vendor.js:35:3623
_.Callbacks/k@http://localhost:8080/scripts/vendor.js:24:22323
_.Callbacks/l.fireWith@http://localhost:8080/scripts/vendor.js:24:23140
.ready@http://localhost:8080/scripts/vendor.js:24:24933
g@http://localhost:8080/scripts/vendor.js:14:960

http://errors.angularjs.org/1.3.8/$injector/modulerr?p0=ngTouch&p1=%5B%24injector%3Anomod%5D%20Module%20'ngTouch'%20is%20not%20available!%20You%20either%20misspelled%20the%20module%20name%20or%20forgot%20to%20load%20it.%20If%20registering%20a%20module%20ensure%20that%20you%20specify%20the%20dependencies%20as%20the%20second%20argument.%0Ahttp%3A%2F%2Ferrors.angularjs.org%2F1.3.8%2F%24injector%2Fnomod%3Fp0%3DngTouch%0Ad%2F%3C%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A410%0Aka%2F%3C%2F%3C%2F%3C%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A8675%0Ab%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A8247%0Aka%2F%3C%2F%3C%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A8559%0An%2F%3C%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A16993%0Af%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A793%0An%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A16841%0An%2F%3C%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A17010%0Af%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A793%0An%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A16841%0ASa%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A18503%0A_%2Fh%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A6427%0A_%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A6737%0A%24%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A31%3A5986%0A%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A35%3A3623%0A_.Callbacks%2Fk%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A24%3A22323%0A_.Callbacks%2Fl.fireWith%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A24%3A23140%0A.ready%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A24%3A24933%0Ag%40http%3A%2F%2Flocalhost%3A8080%2Fscripts%2Fvendor.js%3A14%3A960%0A
d/<@http://localhost:8080/scripts/vendor.js:31:410
n/<@http://localhost:8080/scripts/vendor.js:31:17269
f@http://localhost:8080/scripts/vendor.js:31:793
n@http://localhost:8080/scripts/vendor.js:31:16841
n/<@http://localhost:8080/scripts/vendor.js:31:17010
f@http://localhost:8080/scripts/vendor.js:31:793
n@http://localhost:8080/scripts/vendor.js:31:16841
Sa@http://localhost:8080/scripts/vendor.js:31:18503
_/h@http://localhost:8080/scripts/vendor.js:31:6427
_@http://localhost:8080/scripts/vendor.js:31:6737
$@http://localhost:8080/scripts/vendor.js:31:5986
@http://localhost:8080/scripts/vendor.js:35:3623
_.Callbacks/k@http://localhost:8080/scripts/vendor.js:24:22323
_.Callbacks/l.fireWith@http://localhost:8080/scripts/vendor.js:24:23140
.ready@http://localhost:8080/scripts/vendor.js:24:24933
g@http://localhost:8080/scripts/vendor.js:14:960

On Tue, Oct 27, 2015 at 6:45 PM, rohit choudhary <rconl...@gmail.com> wrote:

> Naveen,
>
> Glad! Look forward to your use cases with Zeppelin.
>
> Thanks,
> Rohit.
>
> On Tue, Oct 27, 2015 at 4:37 PM, naveen xavier <naveen.xav...@gmail.com>
> wrote:
>
>> Hi Guys
>>
>> Yipee Did it
>>
>> I just figured that grunt is building only when I give the --force
>> switch. So I edited the pom.xml in zeppelin-web folder as given below and
>> added it as an argument
>>
>> <execution>
>>             <id>grunt build</id>
>>             <goals>
>>               <goal>grunt</goal>
>>             </goals>
>>
>>             <configuration>
>>               <arguments>*--force*</arguments>
>>             </configuration>
>>  </execution>
>>
>> Then I did a maven package and presto it worked. Thanks a lot guys will
>> now try and run Zeppelin which has been delayed by ONE day
>>
>> Thanks Rohit, Corneau and Renjith for all the help
>>
>> Regards,
>>
>> Naveen
>>
>> On Tue, Oct 27, 2015 at 4:14 PM, naveen xavier <naveen.xav...@gmail.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> Just another update. On carrying out activities suggested by Renjith
>>> finally my ./grunt build error has been cleared. It gave some warnings but
>>> ran with --force switch. Apparently phantomjs has been successfully
>>> installed.
>>> The current versions displayed are
>>> npm: 1.4.21
>>> node: 0.10.25
>>> phantomjs: 1.9.0
>>>
>>> However on performing a mvn install in zeppelin-web folder.... I end up
>>> with the same grunt --no-color failed error as part of installing the
>>> eirslett frontend plugin.
>>>
>>> Adamant error.Any inputs will be most appreciated.
>>>
>>>
>>> On Tue, Oct 27, 2015 at 3:31 PM, Renjith Kamath <
>>> renjith.kam...@gmail.com> wrote:
>>>
>>>> Tried again on a new vm "Ubuntu *15.04 x86_64*". This time everything
>>>> worked fine just by doing "mvn clean install" in zeppelin-web
>>>> java 1.8.0_66
>>>> maven 3.3.3
>>>> npm is supposed to install karma and other karma related deps
>>>>
>>>> may be you can delete node_modules and bower_components from
>>>> zeppelin-web
>>>> rm -rf ~/.npm
>>>> npm cache clear
>>>>
>>>> and finally mvn clean install. frontend-maven-plugin should take care
>>>> of all npm and bower deps
>>>>
>>>>
>>>>
>>>> Thanks & Regards,
>>>> RK
>>>>
>>>> On Tue, Oct 27, 2015 at 2:54 PM, naveen xavier <naveen.xav...@gmail.com
>>>> > wrote:
>>>>
>>>>> Hi Renjith,
>>>>>
>>>>> Just installed nodesjs legacy as suggested by you. Now on giving the
>>>>> command nodejs -v I am getting v0.10.25
>>>>>
>>>>> Secondly fontconfig is installed and is the latest version.
>>>>>
>>>>> The problem on running ./grunt in the zeppelin-web folder seems to be
>>>>> in the karma-phantomjs-launcher module. The node-modules folder does not
>>>>> have this folder in it. I searched and found it in the temp folder with a
>>>>> folder named as - (ie hypen). Any help on how to get the phantomjs problem
>>>>> sorted out.
>>>>>
>>>>> Thanks again
>>>>>
>>>>>
>>>>> On Tue, Oct 27, 2015 at 2:35 PM, Renjith Kamath <
>>>>> renjith.kam...@gmail.com> wrote:
>>>>>
>>>>>> I was able to see the earlier phantomjs error on a new vm and resolve
>>>>>> it by installing libfontconfig.
>>>>>> Can you check if "fontconfig" package is installed or not? sudo
>>>>>> apt-get install fontconfig
>>>>>>
>>>>>> Thanks & Regards,
>>>>>> RK
>>>>>>
>>>>>> On Tue, Oct 27, 2015 at 2:28 PM, rohit choudhary <rconl...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Naveen,
>>>>>>>
>>>>>>> Looks like there's some issue with your NodeJS installation. I
>>>>>>> looked up some links, there was a breaking change in the package 
>>>>>>> manager,
>>>>>>> and I think this would work for you sudo apt-get install nodejs-
>>>>>>> legacy.
>>>>>>>
>>>>>>>
>>>>>>> http://stackoverflow.com/questions/21168141/can-not-install-packages-using-node-package-manager-in-ubuntu
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Rohit.
>>>>>>>
>>>>>>> On Tue, Oct 27, 2015 at 1:02 PM, naveen xavier <
>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Renjith,
>>>>>>>>
>>>>>>>> Did as you suggested, it seems to already exist
>>>>>>>>
>>>>>>>> Reading package lists... Done
>>>>>>>> Building dependency tree
>>>>>>>> Reading state information... Done
>>>>>>>> Note, selecting 'libfontconfig1' instead of 'libfontconfig'
>>>>>>>> libfontconfig1 is already the newest version.
>>>>>>>> The following packages were automatically installed and are no
>>>>>>>> longer required:
>>>>>>>>   libarmadillo4 libarpack2 libdap11 libdapclient3 libepsilon1
>>>>>>>> libfreexl1 libgdal1h libgeos-3.4.2 libgeos-c1 libhawtjni-runtime-java
>>>>>>>>   libhdf4-0-alt libhdf5-8 libjansi-java libjansi-native-java
>>>>>>>> libkml0 libmysqlcppconn7 libnetcdfc7 libodbc1 libogdi3.2 libopenjp2-7
>>>>>>>>   libpq5 libproj0 libspatialite5 liburiparser1 libvsqlitepp3
>>>>>>>> libxerces-c3.1 linux-headers-3.19.0-15 linux-headers-3.19.0-15-generic
>>>>>>>>   linux-image-3.19.0-15-generic linux-image-extra-3.19.0-15-generic
>>>>>>>> mysql-utilities mysql-workbench-data odbcinst odbcinst1debian2
>>>>>>>>   proj-bin proj-data python-mysql.connector python-pexpect
>>>>>>>> python-pyodbc python-pysqlite2 scala-library
>>>>>>>> Use 'apt-get autoremove' to remove them.
>>>>>>>> 0 upgraded, 0 newly installed, 0 to remove and 50 not upgraded.
>>>>>>>>
>>>>>>>> Any reason libfontconfig1 needs to be replaced???
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Oct 27, 2015 at 12:55 PM, Renjith Kamath <
>>>>>>>> renjith.kam...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hey Naveen,
>>>>>>>>>
>>>>>>>>> The issue is in PhantomJs dep. Please try "sudo apt-get install
>>>>>>>>> libfontconfig"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks & Regards,
>>>>>>>>> RK
>>>>>>>>>
>>>>>>>>> On Tue, Oct 27, 2015 at 12:32 PM, naveen xavier <
>>>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Corneau & Rohit,
>>>>>>>>>>
>>>>>>>>>> Just as suggested I did a ./grunt in the zeppelin-web folder. It
>>>>>>>>>> ran successfully and then prompted to use the following command as 
>>>>>>>>>> the
>>>>>>>>>> module is missing:
>>>>>>>>>>
>>>>>>>>>> install karma-phantomjs-launcher --save-dev
>>>>>>>>>>
>>>>>>>>>> On attempting to install the same I received the following error:
>>>>>>>>>>
>>>>>>>>>> > phantomjs@1.9.18 install
>>>>>>>>>> /usr/local/incubator-zeppelin/zeppelin-web/node_modules/phantomjs
>>>>>>>>>> > node install.js
>>>>>>>>>>
>>>>>>>>>> sh: 1: node: not found
>>>>>>>>>> npm WARN This failure might be due to the use of legacy binary
>>>>>>>>>> "node"
>>>>>>>>>> npm WARN For further explanations, please read
>>>>>>>>>> /usr/share/doc/nodejs/README.Debian
>>>>>>>>>>
>>>>>>>>>> npm ERR! phantomjs@1.9.18 install: `node install.js`
>>>>>>>>>> npm ERR! Exit status 127
>>>>>>>>>> npm ERR!
>>>>>>>>>> npm ERR! Failed at the phantomjs@1.9.18 install script.
>>>>>>>>>> npm ERR! This is most likely a problem with the phantomjs package,
>>>>>>>>>> npm ERR! not with npm itself.
>>>>>>>>>> npm ERR! Tell the author that this fails on your system:
>>>>>>>>>> npm ERR!     node install.js
>>>>>>>>>> npm ERR! You can get their info via:
>>>>>>>>>> npm ERR!     npm owner ls phantomjs
>>>>>>>>>> npm ERR! There is likely additional logging output above.
>>>>>>>>>>
>>>>>>>>>> npm ERR! System Linux 3.19.0-30-generic
>>>>>>>>>> npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
>>>>>>>>>> "karma-phantomjs-launcher" "--save-dev"
>>>>>>>>>> npm ERR! cwd /usr/local/incubator-zeppelin/zeppelin-web
>>>>>>>>>> npm ERR! node -v v0.10.25
>>>>>>>>>> npm ERR! npm -v 1.4.21
>>>>>>>>>> npm ERR! code ELIFECYCLE
>>>>>>>>>> npm ERR!
>>>>>>>>>> npm ERR! Additional logging details can be found in:
>>>>>>>>>> npm ERR!
>>>>>>>>>> /usr/local/incubator-zeppelin/zeppelin-web/npm-debug.log
>>>>>>>>>> npm ERR! not ok code 0
>>>>>>>>>>
>>>>>>>>>> I read in some post that the temp files of phantomjs could create
>>>>>>>>>> a problem, so I deleted the same... but got the same error. I am now 
>>>>>>>>>> trying
>>>>>>>>>> to build phantomjs from source after cloning it from github.
>>>>>>>>>>
>>>>>>>>>> Let me know if I am on the right path.
>>>>>>>>>>
>>>>>>>>>> Thanks again for your interest.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Oct 27, 2015 at 2:04 AM, naveen xavier <
>>>>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Rohit,
>>>>>>>>>>>
>>>>>>>>>>> Thank you so much for your quick response.
>>>>>>>>>>>
>>>>>>>>>>> Did exactly as you suggested and successfully installed npm
>>>>>>>>>>> inside zeppelin-web folder. Now when I give the command: *npm
>>>>>>>>>>> -v*
>>>>>>>>>>> I get:  *1.4.21*
>>>>>>>>>>>
>>>>>>>>>>> However the command: *mvn package*
>>>>>>>>>>> within the zeppelin-web folder gives the same grunt build error:
>>>>>>>>>>> *'grunt --no-color' failed. (error code 3).*
>>>>>>>>>>> I also again tried the command: *mvn package -DskipTests* from
>>>>>>>>>>> incubator-zeppelin folder and received the same error!!!
>>>>>>>>>>>
>>>>>>>>>>> Also went through your trail mail with Pablo who has been
>>>>>>>>>>> graduating to new problems but my error message has just not 
>>>>>>>>>>> changed. I
>>>>>>>>>>> have tried every possible combination and end up with the same 
>>>>>>>>>>> grunt error.
>>>>>>>>>>> Please help.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Oct 26, 2015 at 11:20 PM, rohit choudhary <
>>>>>>>>>>> rconl...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Naveen,
>>>>>>>>>>>>
>>>>>>>>>>>> Can you run npm install inside you /zeppelin-web/ directory? If
>>>>>>>>>>>> that is successful you can run - mvn package -Dskiptest 
>>>>>>>>>>>> -Phadoop-2.3
>>>>>>>>>>>> -Ppyspark (or whatever else you want to configure your zeppelin 
>>>>>>>>>>>> with). You
>>>>>>>>>>>> might be missing on some npm libraries.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Rohit
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Oct 26, 2015 at 11:00 PM, naveen xavier <
>>>>>>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> My configuration is as follows:
>>>>>>>>>>>>> Ubuntu 15.04
>>>>>>>>>>>>> Spark 1.4.1
>>>>>>>>>>>>> Hadoop 2.7
>>>>>>>>>>>>> Maven 3.3.3
>>>>>>>>>>>>>
>>>>>>>>>>>>> I am trying to install Apache Zeppelin using the following
>>>>>>>>>>>>> command
>>>>>>>>>>>>>
>>>>>>>>>>>>> mvn clean package -DskipTests
>>>>>>>>>>>>>
>>>>>>>>>>>>> Despite several attempts, I am getting the following error.
>>>>>>>>>>>>>
>>>>>>>>>>>>> [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]
>>>>>>>>>>>>>
>>>>>>>>>>>>> Any help will be highly appreciated. Thanks in advance
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Naveen Xavier
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Naveen Xavier
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>>
>>>>> Naveen Xavier
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Naveen Xavier
>>>
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Naveen Xavier
>>
>>
>>
>


-- 
Regards,

Naveen Xavier

Reply via email to