[
https://issues.apache.org/jira/browse/AMBARI-12563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-12563:
-------------------------------------
Description:
User has a third party monitoring tool that, whenever user do a
'su' it prints out the following message
Therefore, for example when customer starts up namenode, Ambari is not able to
phrase the status codes after executing the curl call for webHDFS, and throw
error message and indicates the operation as fail. Meanwhile, the namenode is
actually up and running.
This behavior also happens across other services, such as HBase.
This issue is causing confusion upon starting of
services/components.
was:
PROBLEM: Customer has a third party monitoring tool that, whenever user do a
'su' it prints out the following message
FANNIE MAE MANAGEMENT APPROVED PURPOSES ONLY\n**** SYSTEM ACTIVITIES MAY BE
MONITORED
Therefore, for example when customer starts up namenode, Ambari is not able to
phrase the status codes after executing the curl call for webHDFS, and throw
error message and indicates the operation as fail. Meanwhile, the namenode is
actually up and running.
This behavior also happens across other services, such as HBase.
BUSINESS IMPACT: This issue is causing confusion upon starting of
services/components.
> Ambari return fail upon service check
> --------------------------------------
>
> Key: AMBARI-12563
> URL: https://issues.apache.org/jira/browse/AMBARI-12563
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>
> User has a third party monitoring tool that, whenever user do a
> 'su' it prints out the following message
> Therefore, for example when customer starts up namenode, Ambari is not able to
> phrase the status codes after executing the curl call for webHDFS, and throw
> error message and indicates the operation as fail. Meanwhile, the namenode is
> actually up and running.
> This behavior also happens across other services, such as HBase.
> This issue is causing confusion upon starting of
> services/components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
