Yes, that was in the "out" file.  I dont see any errors in the "log" file,
except something about JSP which I've highlighted.  Here are the last few
lines:


INFO [2015-12-19 11:14:37,836] ({main}
SimpleThreadPool.java[initialize]:268) - Job execution threads will use
class loader of thread: main
 INFO [2015-12-19 11:14:37,888] ({main}
SchedulerSignalerImpl.java[<init>]:61) - Initialized Scheduler Signaller of
type: class org.quartz.core.SchedulerSignalerImpl
 INFO [2015-12-19 11:14:37,890] ({main} QuartzScheduler.java[<init>]:240) -
Quartz Scheduler v.2.2.1 created.
 INFO [2015-12-19 11:14:37,894] ({main} RAMJobStore.java[initialize]:155) -
RAMJobStore initialized.
 INFO [2015-12-19 11:14:37,898] ({main}
QuartzScheduler.java[initialize]:305) - Scheduler meta-data: Quartz
Scheduler (v2.2.1) 'DefaultQuartzScheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
  Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support
persistence. and is not clustered.

 INFO [2015-12-19 11:14:37,899] ({main}
StdSchedulerFactory.java[instantiate]:1339) - Quartz scheduler
'DefaultQuartzScheduler' initialized from default resource file in Quartz
package: 'quartz.properties'
 INFO [2015-12-19 11:14:37,899] ({main}
StdSchedulerFactory.java[instantiate]:1343) - Quartz scheduler version:
2.2.1
 INFO [2015-12-19 11:14:37,900] ({main} QuartzScheduler.java[start]:575) -
Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
 INFO [2015-12-19 11:14:40,149] ({main}
ServerImpl.java[initDestination]:94) - Setting the server's publish address
to be /
 INFO [2015-12-19 11:14:40,990] ({main}
StandardDescriptorProcessor.java[visitServlet]:284) - NO JSP Support for /,
did not find org.apache.jasper.servlet.JspServlet
 INFO [2015-12-19 11:14:45,154] ({main}
AbstractConnector.java[doStart]:338) - Started
SelectChannelConnector@0.0.0.0:9191
 INFO [2015-12-19 11:14:45,155] ({main} ZeppelinServer.java[main]:108) -
Started zeppelin server

On Sat, Dec 19, 2015 at 11:55 AM, Sourav Mazumder <
sourav.mazumde...@gmail.com> wrote:

> Are you seeing this in .out file ? Then it is regular.
>
>
> Can you please check what is there in .log file too ?
>
> Regards,
> Sourav
>
> On Sat, Dec 19, 2015 at 11:40 AM, Girish Reddy <gir...@springml.com>
> wrote:
>
>> Thanks for the hints.  I checked the out file and here's what I see - the
>> IO exceptions could be why the UI is returning blank.
>>
>>
>> INFO: No provider classes found.
>> Dec 19, 2015 11:14:41 AM
>> com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
>> INFO: Initiating Jersey application, version 'Jersey: 1.13 06/29/2012
>> 05:14 PM'
>> Dec 19, 2015 11:14:45 AM com.sun.jersey.spi.inject.Errors
>> processErrorMessages
>> WARNING: The following warnings have been detected with resource and/or
>> provider classes:
>>   WARNING: A HTTP GET method, public javax.ws.rs.core.Response
>> org.apache.zeppelin.rest.InterpreterRestApi.listInterpreter(java.lang.String),
>> should not consume any entity.
>>   WARNING: A sub-resource method, public javax.ws.rs.core.Response
>> org.apache.zeppelin.rest.NotebookRestApi.createNote(java.lang.String)
>> throws java.io.IOException, with URI template, "/", is treated as a
>> resource method
>>   WARNING: A sub-resource method, public javax.ws.rs.core.Response
>> org.apache.zeppelin.rest.NotebookRestApi.getNotebookList() throws
>> java.io.IOException, with URI template, "/", is treated as a resource method
>>
>>
>>
>>
>>
>> On Sat, Dec 19, 2015 at 11:29 AM, Sourav Mazumder <
>> sourav.mazumde...@gmail.com> wrote:
>>
>>> In that case check the logs folder under home for .log and .out file.
>>> There must be some hints on what is going on.
>>>
>>> Regards,
>>> Sourav
>>>
>>> On Dec 19, 2015, at 11:24 AM, Girish Reddy <gir...@springml.com> wrote:
>>>
>>> I had actually already done that since I got the "Address In Use" error
>>> in the log.
>>>
>>> I renamed zeppelin-site.xml.template to zeppelin-site.xml and changed
>>> the port as below, and restarted.
>>>
>>> <property>
>>>   <name>zeppelin.server.port</name>
>>>   <value>9191</value>
>>>   <description>Server port.</description>
>>> </property>
>>>
>>>
>>>
>>> On Sat, Dec 19, 2015 at 11:07 AM, Sourav Mazumder <
>>> sourav.mazumde...@gmail.com> wrote:
>>>
>>>> Sometimes u can see this error if the port Zeppelin started with is
>>>> already used.
>>>>
>>>> Zeppelin by default starts at 8080. But that port may be already in
>>>> use. So you need to change the port in zeppelin-site.xml and restart.
>>>>
>>>> Regards,
>>>> Sourav
>>>>
>>>> On Dec 19, 2015, at 11:00 AM, Girish Reddy <gir...@springml.com> wrote:
>>>>
>>>> Hello:
>>>>
>>>> I am building Zeppelin on Ubuntu (building Zeppelin-With-R, but I
>>>> suspect this issue is not specific to that build and more related to my
>>>> env) and the build itself goes through successfully.  However when I access
>>>> the Zeppelin URL from the browser, it's blank and I see this error in the
>>>> browser console.  Any thoughts on this please?
>>>>
>>>> GET http://localhost:9191/styles/vendor.css
>>>> scripts.js:1 Uncaught ReferenceError: angular is not defined
>>>>
>>>>
>>>> Here's the info on the successful build.
>>>>
>>>> [INFO] Reactor Summary:
>>>> [INFO]
>>>> [INFO] Zeppelin ........................................... SUCCESS
>>>> [01:05 min]
>>>> [INFO] Zeppelin: Interpreter .............................. SUCCESS [
>>>> 53.278 s]
>>>> [INFO] Zeppelin: Zengine .................................. SUCCESS [
>>>> 34.592 s]
>>>> [INFO] Zeppelin: Spark dependencies ....................... SUCCESS
>>>> [03:06 min]
>>>> [INFO] Zeppelin: Spark .................................... SUCCESS [
>>>> 57.024 s]
>>>> [INFO] Zeppelin: R Interpreter ............................ SUCCESS [
>>>> 33.774 s]
>>>> [INFO] Zeppelin: Markdown interpreter ..................... SUCCESS [
>>>>  7.987 s]
>>>> [INFO] Zeppelin: Angular interpreter ...................... SUCCESS [
>>>>  8.228 s]
>>>> [INFO] Zeppelin: Shell interpreter ........................ SUCCESS [
>>>>  8.056 s]
>>>> [INFO] Zeppelin: Hive interpreter ......................... SUCCESS [
>>>> 20.312 s]
>>>> [INFO] Zeppelin: Apache Phoenix Interpreter ............... SUCCESS [
>>>> 28.433 s]
>>>> [INFO] Zeppelin: PostgreSQL interpreter ................... SUCCESS [
>>>> 10.772 s]
>>>> [INFO] Zeppelin: Tajo interpreter ......................... SUCCESS [
>>>> 11.499 s]
>>>> [INFO] Zeppelin: Flink .................................... SUCCESS [
>>>> 20.561 s]
>>>> [INFO] Zeppelin: Apache Ignite interpreter ................ SUCCESS [
>>>> 11.795 s]
>>>> [INFO] Zeppelin: Kylin interpreter ........................ SUCCESS [
>>>>  8.670 s]
>>>> [INFO] Zeppelin: Lens interpreter ......................... SUCCESS [
>>>> 19.987 s]
>>>> [INFO] Zeppelin: Cassandra ................................ SUCCESS [
>>>> 56.145 s]
>>>> [INFO] Zeppelin: web Application .......................... SUCCESS
>>>> [03:52 min]
>>>> [INFO] Zeppelin: Server ................................... SUCCESS [
>>>> 43.173 s]
>>>> [INFO] Zeppelin: Packaging distribution ................... SUCCESS [
>>>>  8.931 s]
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] BUILD SUCCESS
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Total time: 15:30 min
>>>> [INFO] Finished at: 2015-12-19T10:52:06-08:00
>>>> [INFO] Final Memory: 84M/300M
>>>>
>>>>
>>>
>>
>

Reply via email to