incubator-ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mahadev Konar <maha...@hortonworks.com>
Subject Re: NameNode is failing to start
Date Thu, 14 Mar 2013 07:29:42 GMT
Yes. The start stop button should re activate is some time (usually takes seconds) if it is
1.2.1 release. 

If not can you make an API call to see what the status of Namenode is:

curl -u admin:amdin http://<ambari-server>:8080/api/v1/clusters/<clustername>/services/HDFS/components/NAMENODE?fields=*

(see https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/index.md for more
details on API's)

mahadev

On Mar 14, 2013, at 12:23 AM, Dustine Rene Bernasor <dustine@thecyberguardian.com> wrote:

> Hello,
> 
> Did you mean /var/run/hadoop/hdfs/namenode/formatted?
> 
> I cannot restart namenode from the UI. HDFS icon keeps on blinking
> but the Start and Stop buttons are disabled.
> 
> Thanks.
> 
> Dustine
> 
> 
> On 3/14/2013 3:17 PM, Mahadev Konar wrote:
>> Hi Dustine,
>>  Are you installing on a cluster that was already installed via
>> Ambari? If yes, then remove this directory in
>> /var/run/hadoop/hdfs/formatted and restart namenode from the the UI
>> and it should work.
>> 
>>  If not then its a bug and please create jira nad attach logs for
>> Namenode/amabari agent and server.
>> 
>> thanks
>> mahadev
>> 
>> On Thu, Mar 14, 2013 at 12:13 AM, Dustine Rene Bernasor
>> <dustine@thecyberguardian.com> wrote:
>>> Hello,
>>> 
>>> I was installing Ambari 1.2.1. When I reach step 9, after the services are
>>> installed,
>>> NameNode cannot be started.
>>> 
>>> The ff. exception appeared in the log
>>> 
>>> 2013-03-14 10:58:00,426 ERROR
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: FSNamesystem
>>> initialization failed.
>>> java.io.IOException: NameNode is not formatted.
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:330)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:100)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:411)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:379)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:287)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:548)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1431)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1440)
>>> 2013-03-14 10:58:00,427 ERROR
>>> org.apache.hadoop.hdfs.server.namenode.NameNode: java.io.IOException:
>>> NameNode is not formatted.
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:330)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:100)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:411)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:379)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:287)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:548)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1431)
>>>         at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1440)
>>> 
>>> 2013-03-14 10:58:00,428 INFO
>>> org.apache.hadoop.hdfs.server.namenode.NameNode: SHUTDOWN_MSG:
>>> /************************************************************
>>> SHUTDOWN_MSG: Shutting down NameNode at
>>> Crawler51.localdomain.com/192.168.3.51
>>> ************************************************************/
>>> 
>>> Thanks.
>>> 
>>> Dustine
>>> 
>>> 
> 


Mime
View raw message