incubator-ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sumit Mohanty <smoha...@hortonworks.com>
Subject Re: problems with upgrade to 1.2.3.7
Date Fri, 07 Jun 2013 17:24:29 GMT
They do. However, as the rrd file structure changed the over-all structure
of the API response remains in the old format till you restart the
service. The old response structure results in some broken display.

On 6/7/13 10:11 AM, "Hitesh Shah" <hitesh@hortonworks.com> wrote:

>@Sumit, shouldn't the hostnames for the ganglia server and jobtracker be
>coming from the DB/configs? Is there a relation to the service being
>started and the resolution of the hostname where the service is installed?
>
>-- Hitesh
>
>On Jun 7, 2013, at 9:54 AM, Sumit Mohanty wrote:
>
>> Artem,
>> 
>> You may need to restart few services.
>> 
>> [From the doc:]
>> Re-start the Ganglia, Nagios, and MapReduce services. In Ambari Web.
>> 
>> 	€ Go to the Services View and select each service.
>> 
>> 	€ Use the Management Header to stop and re-start each service.
>> 
>> Thanks
>> Sumit
>> From: Artem Ervits <are9004@nyp.org>
>> Reply-To: <ambari-user@incubator.apache.org>
>> Date: Friday, June 7, 2013 9:39 AM
>> To: "ambari-user@incubator.apache.org"
>><ambari-user@incubator.apache.org>
>> Subject: problems with upgrade to 1.2.3.7
>> 
>> Hello all, I just upgrade my server and agents to 1.2.3.7 and I noticed
>>that all UI links are missing. For example: ganglia Web UI says
>>³:/ganglia² instead of ³servername/ganglia² and jobtracker says ³:50030²
>>instead of ³servername:50030². Ganglia metrics also shows 404 error Not
>>found where metrics would show.
>>  
>> Any idea?
>> 
>> This electronic message is intended to be for the use only of the named
>>recipient, and may contain information that is confidential or
>>privileged. If you are not the intended recipient, you are hereby
>>notified that any disclosure, copying, distribution or use of the
>>contents of this message is strictly prohibited. If you have received
>>this message in error or are not the named recipient, please notify us
>>immediately by contacting the sender at the electronic mail address
>>noted above, and delete and destroy all copies of this message. Thank
>>you.
>



Mime
View raw message