You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Berry Österlund (JIRA)" <ji...@apache.org> on 2016/09/28 11:52:21 UTC
[jira] [Updated] (AMBARI-18479) Service check fails against Yarn
with HA and SPNEGO
[ https://issues.apache.org/jira/browse/AMBARI-18479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Berry Österlund updated AMBARI-18479:
-------------------------------------
Description:
If both HA and SPNEGO is configured for the cluster, service checks on Yarn gives a Warning on the standby node with the following message in Ambari.
HTTP 401 response from http://<HOSTNAME>:8088 in 0.000s ( % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 43 100 43 0 0 5942 0 --:--:-- --:--:-- --:--:-- 6142 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 1400 100 1400 0 0 89354 0 --:--:-- --:--:-- --:--:-- 89354 100 1400 100 1400 0 0 83086 0 --:--:-- --:--:-- --:--:-- 83086)
The problem is because we are using curl to fetch the http pages, we also enters –L to follow the location information in the header. But –L don’t forward authentication information to redirected hosts. Changing –L to --location-trusted solves the problem.
--- /tmp/service_check.py 2016-09-28 13:08:06.468192028 +0200
+++ /var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py 2016-09-28 13:17:36.810100884 +0200
@@ -129,7 +129,7 @@
for rm_webapp_address in params.rm_webapp_addresses_list:
info_app_url = params.scheme + "://" + rm_webapp_address + "/ws/v1/cluster/apps/" + application_name
- get_app_info_cmd = "curl --negotiate -u : -ksL --connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url
+ get_app_info_cmd = "curl --negotiate -u : -ks --location-trusted --connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url
return_code, stdout, _ = get_user_call_output(get_app_info_cmd,
user=params.smokeuser,
was:
If both HA and SPNEGO is configured for the cluster, service checks on Yarn gives a Warning on the standby node with the following message in Ambari.
HTTP 401 response from http://<HOSTNAME>:8088 in 0.000s ( % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 43 100 43 0 0 5942 0 --:--:-- --:--:-- --:--:-- 6142 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 1400 100 1400 0 0 89354 0 --:--:-- --:--:-- --:--:-- 89354 100 1400 100 1400 0 0 83086 0 --:--:-- --:--:-- --:--:-- 83086)
The problem is because we are using curl to fetch the http pages, we also enters –L to follow the location information in the header. But –L don’t forward authentication information to redirected hosts. Changing –L to --location-trusted solves the problem.
{{monospaced}}
--- /tmp/service_check.py 2016-09-28 13:08:06.468192028 +0200
+++ /var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py 2016-09-28 13:17:36.810100884 +0200
@@ -129,7 +129,7 @@
for rm_webapp_address in params.rm_webapp_addresses_list:
info_app_url = params.scheme + "://" + rm_webapp_address + "/ws/v1/cluster/apps/" + application_name
- get_app_info_cmd = "curl --negotiate -u : -ksL --connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url
+ get_app_info_cmd = "curl --negotiate -u : -ks --location-trusted --connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url
return_code, stdout, _ = get_user_call_output(get_app_info_cmd,
user=params.smokeuser,
{{monospaced}}
> Service check fails against Yarn with HA and SPNEGO
> ----------------------------------------------------
>
> Key: AMBARI-18479
> URL: https://issues.apache.org/jira/browse/AMBARI-18479
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.4.0
> Environment: Hortonworks HDP 2.5
> Reporter: Berry Österlund
> Priority: Minor
>
> If both HA and SPNEGO is configured for the cluster, service checks on Yarn gives a Warning on the standby node with the following message in Ambari.
> HTTP 401 response from http://<HOSTNAME>:8088 in 0.000s ( % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 43 100 43 0 0 5942 0 --:--:-- --:--:-- --:--:-- 6142 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 1400 100 1400 0 0 89354 0 --:--:-- --:--:-- --:--:-- 89354 100 1400 100 1400 0 0 83086 0 --:--:-- --:--:-- --:--:-- 83086)
> The problem is because we are using curl to fetch the http pages, we also enters –L to follow the location information in the header. But –L don’t forward authentication information to redirected hosts. Changing –L to --location-trusted solves the problem.
> --- /tmp/service_check.py 2016-09-28 13:08:06.468192028 +0200
> +++ /var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py 2016-09-28 13:17:36.810100884 +0200
> @@ -129,7 +129,7 @@
> for rm_webapp_address in params.rm_webapp_addresses_list:
> info_app_url = params.scheme + "://" + rm_webapp_address + "/ws/v1/cluster/apps/" + application_name
> - get_app_info_cmd = "curl --negotiate -u : -ksL --connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url
> + get_app_info_cmd = "curl --negotiate -u : -ks --location-trusted --connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url
> return_code, stdout, _ = get_user_call_output(get_app_info_cmd,
> user=params.smokeuser,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)