NameNode :
PriviledgedActionException
what is dfs.https.address set to?
- Original Message -
> From: "ramon@accenture.com"
> To: core-u...@hadoop.apache.org
> Cc:
> Sent: Monday, June 4, 2012 4:07 AM
> Subject: SecondaryNameNode n
what is dfs.https.address set to?
- Original Message -
> From: "ramon@accenture.com"
> To: core-u...@hadoop.apache.org
> Cc:
> Sent: Monday, June 4, 2012 4:07 AM
> Subject: SecondaryNameNode not connecting to NameNode :
> PriviledgedActionException
&g
age-
> From: praveenesh kumar [mailto:praveen...@gmail.com]
> Sent: lunes, 04 de junio de 2012 14:25
> To: common-user@hadoop.apache.org
> Subject: Re: SecondaryNameNode not connecting to NameNode :
> PriviledgedActionException
>
> Its trying to connect to your NN on port 50030.. I
: SecondaryNameNode not connecting to NameNode :
PriviledgedActionException
Its trying to connect to your NN on port 50030.. I think it should be 50070. In
your hdfs-site.xml -- for dfs.http.address -- I am assuming you have given
hadoop01:50070, right ?
Regards,
Praveenesh
On Mon, Jun 4, 2012
meNode at hadoop01/192.168.0.11
> ********/
>
> -----Original Message-
> From: Pin, Ramón
> Sent: lunes, 04 de junio de 2012 14:12
> To: common-user@hadoop.apache.org
> Subject: RE: SecondaryNameNode not connecting to NameNod
2 14:12
To: common-user@hadoop.apache.org
Subject: RE: SecondaryNameNode not connecting to NameNode :
PriviledgedActionException
/etc/hosts
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
192.168.0.10 hadoop00
192.168.0.11 hadoop01
192.168.0.1
aveenesh kumar [mailto:praveen...@gmail.com]
> Sent: lunes, 04 de junio de 2012 14:09
> To: common-user@hadoop.apache.org
> Subject: Re: SecondaryNameNode not connecting to NameNode :
> PriviledgedActionException
>
> Also can you share your /etc/hosts file of both the VMs
>
> Re
14:09
To: common-user@hadoop.apache.org
Subject: Re: SecondaryNameNode not connecting to NameNode :
PriviledgedActionException
Also can you share your /etc/hosts file of both the VMs
Regards,
Praveenesh
On Mon, Jun 4, 2012 at 5:35 PM, wrote:
> Right. No firewalls. This is my 'toy'
SHUTDOWN_MSG:
> > /****************
> > SHUTDOWN_MSG: Shutting down SecondaryNameNode at hadoop01/192.168.0.11
> > /
> >
> > -Original Message--
raveenesh kumar [mailto:praveen...@gmail.com]
Sent: lunes, 04 de junio de 2012 14:02
To: common-user@hadoop.apache.org
Subject: Re: SecondaryNameNode not connecting to NameNode :
PriviledgedActionException
Try giving value to dfs.secondary.http.address in hdfs-site.xml on your SNN.
In your logs, i
MSG:
> /
> SHUTDOWN_MSG: Shutting down SecondaryNameNode at hadoop01/192.168.0.11
> /
>
> -Original Message-
> From: praveenesh kumar [mailto:praveen...@gmail.com]
> Sent: lunes, 04 de junio de 2012 13:15
> T
e junio de 2012 13:15
To: common-user@hadoop.apache.org
Subject: Re: SecondaryNameNode not connecting to NameNode :
PriviledgedActionException
I am not sure what could be the exact issue but when configuring secondary NN
to NN, you need to tell your SNN where the actual NN resides.
Try adding - d
I am not sure what could be the exact issue but when configuring secondary
NN to NN, you need to tell your SNN where the actual NN resides.
Try adding - dfs.http.address on your secondary namenode machine having
value as on hdfs-site.xml
Port should be on which your NN url is opening - means your
Hello. I'm facing a issue when trying to configure my SecondaryNameNode on a
different machine than my NameNode. When both are on the same machine
everything works fine but after moving the secondary to a new machine I get:
2012-05-28 09:57:36,832 ERROR org.apache.hadoop.security.UserGroupInform
14 matches
Mail list logo
