JobHistory Service Logs not Available From the HistoryServer Web UI on BDA V3.*/CDH 5.*

(Doc ID 1922338.1)

Last updated on SEPTEMBER 02, 2014

Applies to:

Big Data Appliance Integrated Software - Version 3.0.1 and later
Linux x86-64

Symptoms


JobHistory service logs are not available from the HistoryServer Web UI on BDA V3.*/CDH 5.*.  Instead of log files the following is observed:

HTTP ERROR 404

Problem accessing /logs/. Reason:

    NOT_FOUND

Powered by Jetty://


The problem can be seen any time logs are attempted to be viewed from the HistoryServer.  For example:

1. Navigate directly to the JobHistory Server: http://bdanode03.example.com:19888/logs/

HTTP ERROR 404

Problem accessing /logs/. Reason:

    NOT_FOUND

Powered by Jetty://


2. From the HistoryServer Web UI (bdanode03)

a) Navigate to http://bdanode03.example.com:19888/jobhistory

From CM: Home > yarn > WebUI > HistoryServer Web UI (bdanode03)
or
Navigate directly to: http://bdanode03.example.com:19888/jobhistory

b) On the left select: Tools > Local Logs

Tools > Local Logs:

 

HTTP ERROR 404

Problem accessing /logs/. Reason:

    NOT_FOUND

Powered by Jetty://


3. From the ResourceManger UI:
a) Navigate to http://<activeRMnode>.example.com:8088/cluster

From CM: Home > yarn > WebUI > ResourceManager Web UI (active RM node)
or
Navigate directly to: http://<activeRMnode>.example.com:8088/cluster

b) Select an application id within the viewable timeframe (7 days) e.g. like:  application_1408586853492_0052

c) Select "logs" on the lower right

d) Then from the left pane: Tools > Local logs

HTTP ERROR 404

Problem accessing /logs/. Reason:

    NOT_FOUND

Powered by Jetty://

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms