How to get more detailed log info? Modifying log4j.properties doesn't appear to have any effect

[James Adams <mo...@gmail.com>]

My question is whether or not the log4j.properties file has an effect on
Zeppelin logging, and if so why do the log messages in
logs/zeppelin--myhost.out not reflect the layout specified therein?

Some background:

I have built Zeppelin 0.5.6 from source on Windows 7.

When I launch Zeppelin (bin/zeppelin-daemon start) it fails after a couple
of seconds. When I look into the log file I see the following message:

Error: Could not find or load main class
org.apache.zeppelin.server.ZeppelinServer

I want to find out more about why this error is happening. To this end I've
tried setting the log level to DEBUG in conf/log4j.properties, but when I
relaunch the Zeppelin daemon and it fails again I don't see any additional
information. This may be normal as there may not be any debug level logging
going on before it croaks with this error, I'm not sure.

However the messages in the log file don't appear to adhere to the format
specified in the log4j.properties file. Maybe the log messages are going to
another log file (i.e. to someplace other than logs/zeppelin--myhost.out)?
If not then I would expect for the log messages in that file to follow the
format laid out in log4j.properties.

All of this assumes that the log file being produced is
logs/zeppelin--myhost.out, as there are no other files in the logs
directory. Looking in the zeppelin-daemon.sh file it looks like there
should also be a *.log file which is used as ${ZEPPELIN_LOGFILE}, this is
actually the log file and what I've assumed is the log file is actually
Zeppelin output. Is this the case?

Thanks in advance for any help understanding this.

--James

Re: How to get more detailed log info? Modifying log4j.properties doesn't appear to have any effect

[moon soo Lee <mo...@apache.org>]

Hi,

Thanks for sharing the problem.
org.apache.zeppelin.server.ZeppelinServer is entry point of Zeppelin.
So if it couldn't find the class, even log4j will not be initialized and
produce the log.

By the way, aren't you trying windows script (*.cmd)? which is available
since 0.6.0 release.

Thanks,
moon

On Mon, Jul 25, 2016 at 12:02 PM James Adams <mo...@gmail.com> wrote:

> My question is whether or not the log4j.properties file has an effect on
> Zeppelin logging, and if so why do the log messages in
> logs/zeppelin--myhost.out not reflect the layout specified therein?
>
> Some background:
>
> I have built Zeppelin 0.5.6 from source on Windows 7.
>
> When I launch Zeppelin (bin/zeppelin-daemon start) it fails after a couple
> of seconds. When I look into the log file I see the following message:
>
> Error: Could not find or load main class
> org.apache.zeppelin.server.ZeppelinServer
>
> I want to find out more about why this error is happening. To this end
> I've tried setting the log level to DEBUG in conf/log4j.properties, but
> when I relaunch the Zeppelin daemon and it fails again I don't see any
> additional information. This may be normal as there may not be any debug
> level logging going on before it croaks with this error, I'm not sure.
>
> However the messages in the log file don't appear to adhere to the format
> specified in the log4j.properties file. Maybe the log messages are going to
> another log file (i.e. to someplace other than logs/zeppelin--myhost.out)?
> If not then I would expect for the log messages in that file to follow the
> format laid out in log4j.properties.
>
> All of this assumes that the log file being produced is
> logs/zeppelin--myhost.out, as there are no other files in the logs
> directory. Looking in the zeppelin-daemon.sh file it looks like there
> should also be a *.log file which is used as ${ZEPPELIN_LOGFILE}, this is
> actually the log file and what I've assumed is the log file is actually
> Zeppelin output. Is this the case?
>
> Thanks in advance for any help understanding this.
>
> --James
>