ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srimanth Gunturi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-9075) Alerts after move Oozie Server
Date Fri, 09 Jan 2015 18:53:38 GMT

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

Srimanth Gunturi updated AMBARI-9075:
-------------------------------------
    Attachment: Screen Shot 2015-01-09 at 10.52.34 AM.png

> Alerts after move Oozie Server
> ------------------------------
>
>                 Key: AMBARI-9075
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9075
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 2.0.0
>
>         Attachments: Screen Shot 2015-01-09 at 10.52.34 AM.png
>
>
> ● Fresh install of the ambari­server.
> ● Create a new cluster with specific services. Oozie with new derby database
> ● Move the Oozie Server to another host machine. :
> # Select Move Oozie Server from the Service Actions drop down box
> # select the host to assign the new master to
> # click next.
> # click Deploy.
> # execute the manual steps as instructed on the wizard
> # click next
> # click Complete to exit the wizard.
> *Expected*
> no alerts
> *Actual*
> 2 alerts 
> Oozie Server Web UI 
> * Connection failed to http://c6401.ambari.apache.org:11000
> Oozie Server Status
> * Error: IO_ERROR : java.net.MalformedURLException



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message