Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Where are tez logs?

avatar
Expert Contributor

My Hive query fails:

java.sql.SQLException: Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask

I cannot see any logs in the tez view. It looks like the parse stage is hiding to the right but I cannot access it? How do I look at it and where are the logs?

TIA!!

For some reason I cannot upload a jpg so there is a png here.

1 ACCEPTED SOLUTION

avatar
Master Mentor

@ed day
Do you see any Tez View logs here?

# less /var/log/ambari-server/tez-view/tez-view.log


To get more details on the tez view you can also try to enable the DEBUG on tez view logs as following:


Step1. Change the Tez View logging level to DEBUG (default is INFO)

# grep 'INFO' /var/lib/ambari-server/resources/views/work/TEZ\{0.7.0.2.6.0.3-8\}/view.log4j.properties 
log4j.logger.org.apache.ambari.view.tez=INFO,tezView


Edit the above file and change the INFO to DEBUG as following:

log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView

NOTE: Similarly for the Hive View you can enable the DEBUG logging inside the following files:

# grep 'INFO' /var/lib/ambari-server/resources/views/work/HIVE\{2.0.0\}/view.log4j.properties 
log4j.logger.org.apache.ambari.view.hive20=INFO,hive20


# grep 'INFO' /var/lib/ambari-server/resources/views/work/HIVE\{1.5.0\}/view.log4j.properties 
log4j.logger.org.apache.ambari.view.hive2=INFO,hiveNextView

.
Step2. Now restart Ambari Server and the access Tez View

# ambari-server restart


Step3. Check the Tez Logs.

# tail -300f /var/log/ambari-server/tez-view/tez-view.log

.

View solution in original post

3 REPLIES 3

avatar
Master Mentor

@ed day
Do you see any Tez View logs here?

# less /var/log/ambari-server/tez-view/tez-view.log


To get more details on the tez view you can also try to enable the DEBUG on tez view logs as following:


Step1. Change the Tez View logging level to DEBUG (default is INFO)

# grep 'INFO' /var/lib/ambari-server/resources/views/work/TEZ\{0.7.0.2.6.0.3-8\}/view.log4j.properties 
log4j.logger.org.apache.ambari.view.tez=INFO,tezView


Edit the above file and change the INFO to DEBUG as following:

log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView

NOTE: Similarly for the Hive View you can enable the DEBUG logging inside the following files:

# grep 'INFO' /var/lib/ambari-server/resources/views/work/HIVE\{2.0.0\}/view.log4j.properties 
log4j.logger.org.apache.ambari.view.hive20=INFO,hive20


# grep 'INFO' /var/lib/ambari-server/resources/views/work/HIVE\{1.5.0\}/view.log4j.properties 
log4j.logger.org.apache.ambari.view.hive2=INFO,hiveNextView

.
Step2. Now restart Ambari Server and the access Tez View

# ambari-server restart


Step3. Check the Tez Logs.

# tail -300f /var/log/ambari-server/tez-view/tez-view.log

.

avatar
Master Mentor

@ed day

If you want to get more detailed information for any Tez AM related logging then please change the INFO logging level to DEBUG inside:

Ambari UI --> Tez --> Configs --> General --> "tez.am.log.level"  (INFO to DEBUG) 

.

Root Logging level passed to the Tez app master. Simple configuration: Set the log level for all loggers. e.g. INFO This sets the log level to INFO for all loggers.

.

avatar
Expert Contributor

Wow thanks. I'll try these tomorrow when my latest slow job finishes.