I see no error in the logs.

I am using the binary from the official website and for v0.6.0 the one
from
http://people.apache.org/~moon/zeppelin/builds/0.6.0-incubating-SNAPSHOT/
I did nothing more than renaming conf/zeppelin-env.sh.template to
conf/zeppelin-env.sh an added "export
ZEPPELIN_SERVER_CONTEXT_PATH=/zeppelin"

The parameter seems to be ignored but others are not (I changed, e.g.,
the notebook dir).


On 08.01.2016 17:48, moon soo Lee wrote:
> Hi,
>
> I tried
> export ZEPPELIN_SERVER_CONTEXT_PATH=/zeppelin
> in zeppelin-env.sh and it worked for me.
>
> Do you see any error in your log file under /logs ?
>
> Thanks,
> moon
>
> On Fri, Jan 8, 2016 at 12:42 AM on <schueler_1...@web.de
> <mailto:schueler_1...@web.de>> wrote:
>
>
>     Hi,
>
>     moon, thanks very much for answering!
>
>     I tried export ZEPPELIN_SERVER_CONTEXT_PATH="/zeppelin"  in
>     zeppelin-env.sh and
>     <property>
>         <name>zeppelin.server.context.path</name>
>         <value>/zeppelin/</value>
>         <description>Context Path of the Web Application</description>
>     </property>
>     in zeppelin-site.xml.
>
>     Result is:
>
>     Problem accessing /zeppelin/. Reason:
>
>         Not Found
>
>     ------------------------------------------------------------------------
>     /Powered by Jetty://
>
>     /I tried this in both 0.5.5 and 0.6.
>
>     What am I doing wrong?
>
>     Best regards,
>     on
>
>
>     On 08.01.2016 09:34, moon soo Lee wrote:
>>     Hi,
>>
>>     I think ZEPPELIN_SERVER_CONTEXT_PATH environment variable or
>>     zeppelin.server.context.path jvm property is related option.
>>
>>     Please take a look configure section on
>>     http://zeppelin.incubator.apache.org/docs/latest/install/install.html
>>
>>     Thanks,
>>     moon
>>
>>     On Thu, Jan 7, 2016 at 11:57 PM on <schueler_1...@web.de
>>     <mailto:schueler_1...@web.de>> wrote:
>>
>>         Hi,
>>
>>         is it possible to change Zeppelin's HTTP-ROOT, so that it
>>         runs, e.g.,
>>         under http://localhost:80/zeppelin/#/?
>>
>>         Thanks and best regards,
>>         on
>>
>

Reply via email to