It looks like / is owned by hadoop.supergroup and the perms are 755. You could
precreate /accumulo and chown it appropriately, or set the perms for / to 775.
Init is trying to create /accumulo in hdfs as the accumulo user and your perms
dont allow it.
Do you have instance.volumes set in accumulo-site.xml?
<div>-------- Original message --------</div><div>From: David Patterson
<patt...@gmail.com> </div><div>Date:03/01/2015 3:36 PM (GMT-05:00)
</div><div>To: user@hadoop.apache.org </div><div>Cc: </div><div>Subject:
Permission Denied </div><div>
</div>
I'm trying to create an Accumulo/Hadoop/Zookeeper configuration on a single
(Ubuntu) machine, with Hadoop 2.6.0, Zookeeper 3.4.6 and Accumulo 1.6.1.
I've got 3 userids for these components that are in the same group and no
other users are in that group.
I have zookeeper running, and hadoop as well.
Hadoop's core-site.xml file has the hadoop.tmp.dir set to
/app/hadoop/tmp.The /app/hadoop/tmp directory is owned by the hadoop user
and has permissions that allow other members of the group to write
(drwxrwxr-x).
When I try to initialize Accumulo, with bin/accumulo init, I get FATAL:
Failed to initialize filesystem.
org.apache.hadoop.security.AccessControlException: Permission denied:
user=accumulo, access=WRITE, inode="/":hadoop:supergroup:drwxr-xr-x
So, my main question is which directory do I need to give group-write
permission so the accumulo user can write as needed so it can initialize?
The second problem is that the Accumulo init reports
[Configuration.deprecation] INFO : fs.default.name is deprecated. Instead
use fs.defaultFS. However, the hadoop core-site.xml file contains:
<name>fs.defaultFS</name>
<value>hdfs://localhost:9000</value>
Is there somewhere else that this value (fs.default.name) is specified?
Could it be due to Accumulo having a default value and not getting the
override from hadoop because of the problem listed above?
Thanks
Dave Patterson
patt...@gmail.com
