ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akhil S Naik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-22703) Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster configured and oozie has enabled SSL
Date Thu, 28 Dec 2017 10:07:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-22703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Akhil S Naik updated AMBARI-22703:
----------------------------------
    Description: 
We have a standalone ambari server with remote cluster configured,

oozie is enabled with SSL in remote cluster.

workflow manager (view) doesnt work if the view is configured as remote cluster. (attached
image of configuration and issue)

It keeps loading as shown in the image !attachment-name.jpg|thumbnail!.

possible root cause : 

The wfmanager-view.log shows the server pings on port 11000 instead it has to access the port
11443

{code:java}
28 Dec 2017 09:29:51,821  INFO [ambari-client-thread-25] [WORKFLOW_MANAGER 1.0.0 WF] OozieDelegate:149
- Proxy request for url: [GET] http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153  INFO [ambari-client-thread-30] [WORKFLOW_MANAGER 1.0.0 WF] OozieDelegate:149
- Proxy request for url: [GET] http://host6.example.com:11000/oozie/v2/jobs?filter=&offset=1&len=15&jobtype=wf
{code}


  was:
We have a standalone ambari server with remote cluster configured,

oozie is enabled with SSL in remote cluster.

workflow manager (view) doesnt work if the view is configured as remote cluster. (attached
image of configuration and issue)

It keeps loading as shown in the image .

it works if the configuration is custom configuration ( attached image)

The wfmanager-view.log shows the server pings on port 11000 instead it has to access the port
11443

{code:java}
28 Dec 2017 09:29:51,821  INFO [ambari-client-thread-25] [WORKFLOW_MANAGER 1.0.0 WF] OozieDelegate:149
- Proxy request for url: [GET] http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153  INFO [ambari-client-thread-30] [WORKFLOW_MANAGER 1.0.0 WF] OozieDelegate:149
- Proxy request for url: [GET] http://host6.example.com:11000/oozie/v2/jobs?filter=&offset=1&len=15&jobtype=wf
{code}



> Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster
configured and oozie has enabled SSL
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-22703
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22703
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.5.2
>         Environment: Ambari Version : 2.5.1.0
> ssl enabled oozie and standalone ambari with remote cluster
>            Reporter: Akhil S Naik
>         Attachments: oozie keeps loading.png, remote cluster config.png
>
>
> We have a standalone ambari server with remote cluster configured,
> oozie is enabled with SSL in remote cluster.
> workflow manager (view) doesnt work if the view is configured as remote cluster. (attached
image of configuration and issue)
> It keeps loading as shown in the image !attachment-name.jpg|thumbnail!.
> possible root cause : 
> The wfmanager-view.log shows the server pings on port 11000 instead it has to access
the port 11443
> {code:java}
> 28 Dec 2017 09:29:51,821  INFO [ambari-client-thread-25] [WORKFLOW_MANAGER 1.0.0 WF]
OozieDelegate:149 - Proxy request for url: [GET] http://host6.example.com:11000/oozie/v1/admin/configuration
> 28 Dec 2017 09:29:52,153  INFO [ambari-client-thread-30] [WORKFLOW_MANAGER 1.0.0 WF]
OozieDelegate:149 - Proxy request for url: [GET] http://host6.example.com:11000/oozie/v2/jobs?filter=&offset=1&len=15&jobtype=wf
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message