Support Questions

pd47 · ‎09-29-2016

I've installed Grafana through Ambari 2.4.1.0 on HDP 2.3.4. The datasource is "AMBARI_METRICS".

When I try to validate the datasource, I'm getting below error:

2016/09/28 17:05:56 [middleware.go:145 initContextWithBasicAuth()] [E] Invalid Basic Auth Header: Invalid basic auth header 2016/09/28 17:05:56 [I] Completed 10.128.211.106 admin "GET /api/datasources/proxy/1/ws/v1/timeline/metrics/metadata HTTP/1.1" 401 Unauthorized 39 bytes in 102us

datasource info:

Url = http://hostip:6188

access = proxy

http Auth = unchecked

with credentials= unchecked

-------

If I change the auth.basic=false, Grafana service fails to start. We have kerberos installed in our cluster.

avijayan · ‎10-03-2016

Hi PD,

This is a known bug in AMS.

The cause is that AMS uses its own instance of Yarn ATS as the application server, and has the cluster core-site in its conf directory (/etc/ambari-metrics-collector/conf). Since the core-site has spnego configs used by cluster Hadoop components, this ATS picks them up, and acts as a spnego enabled end point, even though AMS has no spnego support.

The workaround fix (https://issues.apache.org/jira/browse/AMBARI-18187) was recently checked into branch-2.4, and should be part of next Ambari release - 2.4.2. The long term solution of supporting SPNEGO in AMS is being worked on as part of https://issues.apache.org/jira/browse/AMBARI-14384, and is planned for Ambari-2.5.0.

View solution in original post

pd47 · ‎10-11-2016

@Aravindan Vijayan

That worked. Thanks for your help.

Cloudera Community

Support Questions

Grafana - initContextWithBasicAuth()] [E] Invalid Basic Auth Header: Invalid basic auth header