Re: Failed to start namenode.

is JIRA gives you some >> background. https://issues.apache.org/jira/browse/HADOOP-4487 >> >> >> >> After the setup of your cluster, if you are still having issues with >> other services or HDFS – This is a diagnostic tool that can help you. >> https://github.com/stevelough

Re: Failed to start namenode.

t; > After the setup of your cluster, if you are still having issues with other > services or HDFS – This is a diagnostic tool that can help you. > https://github.com/steveloughran/kdiag > > > > Thanks > > Anu > > > > > > *From: *Rakesh Radhakrishnan

Re: Failed to start namenode.

: Hafiz Mujadid Cc: "user@hadoop.apache.org" Subject: Re: Failed to start namenode. Hi, Could you please check kerberos principal name is specified correctly in "hdfs-site.xml", which is used to authenticate against Kerberos. If using _HOST variable in hdfs-site.xml, ens

Re: Failed to start namenode.

g file to know more about your configurations. Regards, Rakesh On Thu, Jun 9, 2016 at 6:21 PM, Hafiz Mujadid wrote: > Hi, > > I have setup kerbores with hadoop and I am facing following exception when > i start hadoop. > > ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: Failed t

Failed to start namenode.

Hi, I have setup kerbores with hadoop and I am facing following exception when i start hadoop. ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: Failed to start namenode. java.io.IOException: Login failure for admin/admin@queryiorealm from keytab /usr/local/var/krb5kdc/kadm5.keytab

Re: failed to start namenode

Hi Daniel, My host is up and running. On 11/20/15, Daniel Haviv wrote: > Are you sure the host is up? > > On Friday, 20 November 2015, siva kumar wrote: > >> Hi Sandeep, >> Im tryning to start using cloudera manager . This >> is the error message im getting

Re: failed to start namenode

Are you sure the host is up? On Friday, 20 November 2015, siva kumar wrote: > Hi Sandeep, > Im tryning to start using cloudera manager . This > is the error message im getting. The log is not getting generated in the > log directory. > > Supervisor returned FATAL. Please

Re: failed to start namenode

Hi Sandeep, Im tryning to start using cloudera manager . This is the error message im getting. The log is not getting generated in the log directory. Supervisor returned FATAL. Please check the role log file, stderr, or stdout. HTTP ERROR 502 Problem accessing /cmf/proce

Re: failed to start namenode

Its surprising that no logs are created. How are you trying to start Name node? If you are starting using cloudera manager then logs can be seen found out on screen as well. On Thu, Nov 19, 2015 at 11:36 AM, siva kumar wrote: > Hi Sandeep, > The log is not getting genera

Re: failed to start namenode

Hi Sandeep, The log is not getting generated for the name node. On Wed, Nov 18, 2015 at 5:53 PM, sandeep das wrote: > At least share some excerpts from log of name node log file. > > On Wed, Nov 18, 2015 at 5:46 PM, siva kumar wrote: > >> Hi Folks, >>

Re: failed to start namenode

At least share some excerpts from log of name node log file. On Wed, Nov 18, 2015 at 5:46 PM, siva kumar wrote: > Hi Folks, > I'm trying to install a fresh hadoop cluster. But > then,namenode is not is not starting up because of which hdfs service is > not started during my fir

failed to start namenode

Hi Folks, I'm trying to install a fresh hadoop cluster. But then,namenode is not is not starting up because of which hdfs service is not started during my first run. Can anyone help me out? I'm trying this using parcels(CDH-5). Any help?