Thanks, I'm over that hurdle.  What about configuring PutHDFS then?  Still
pretty lost here.

-Chris

On Wed, Sep 16, 2015 at 1:28 PM, Matt Gilman <[email protected]>
wrote:

> Does the user you specified have access to the directory structure where
> NiFi is installed? Specifically do they have access to
> lib/bootstrap/nifi-bootstrap-<version>.jar? Are there any more details with
> that error message?
>
> Just to be sure, do they have access to all paths configured in
> conf/nifi.properties (assuming you've changed them from defaults)?
>
> Matt
>
>
> On Wed, Sep 16, 2015 at 1:21 PM, Christopher Wilson <[email protected]>
> wrote:
>
>> What version are you running?  I'm getting "Error: Could not find or load
>> class org.apache.nifi.bootstrap.RunNiFi" when I change to a different user.
>>
>> -Chris
>>
>> On Wed, Sep 16, 2015 at 12:52 PM, Matt Gilman <[email protected]>
>> wrote:
>>
>>> Chris,
>>>
>>> You shouldn't need to run NiFi as root. What is currently preventing you
>>> from doing so? Are you setting the run.as user in the
>>> conf/bootstrap.conf file?
>>>
>>> Matt
>>>
>>> On Wed, Sep 16, 2015 at 12:42 PM, Christopher Wilson <
>>> [email protected]> wrote:
>>>
>>>> I have a question regarding configuration of PutHDFS.  I'm running NiFi
>>>> as root (because I can't find how not to) and I've installed NiFi on a
>>>> client node in my Hadoop cluster (HDP 2.3).  I can't find where to tell
>>>> PutHDFS to put files as a specific user.  Not that strong on Hadoop
>>>> configuration so any help appreciated.
>>>>
>>>> Thanks in advance.
>>>>
>>>> Nifi version 0.2.1
>>>> Java version 1.7
>>>> RedHat 6.7
>>>>
>>>> PutHDFS[id=65cf6d5a-d5fb-4b77-82b5-f1d71a80ef72] Failed to write to
>>>> HDFS due to org.apache.nifi.processor.exception.ProcessException:
>>>> IOException thrown from PutHDFS[id=65cf6d5a-d5fb-4b77-82b5-f1d71a80ef72]:
>>>> org.apache.hadoop.security.AccessControlException: Permission denied:
>>>> user=root, access=WRITE,
>>>> inode="/user/NOT-ROOT/.file.log":not-root:hdfs:drwxrwxr-x
>>>>
>>>> -Chris
>>>>
>>>
>>>
>>
>

Reply via email to