From dev-return-12941-apmail-nifi-dev-archive=nifi.apache.org@nifi.apache.org Mon Jan 9 21:18:14 2017 Return-Path: X-Original-To: apmail-nifi-dev-archive@minotaur.apache.org Delivered-To: apmail-nifi-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2E00A192FE for ; Mon, 9 Jan 2017 21:18:14 +0000 (UTC) Received: (qmail 95306 invoked by uid 500); 9 Jan 2017 21:18:14 -0000 Delivered-To: apmail-nifi-dev-archive@nifi.apache.org Received: (qmail 95222 invoked by uid 500); 9 Jan 2017 21:18:10 -0000 Mailing-List: contact dev-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list dev@nifi.apache.org Received: (qmail 95188 invoked by uid 99); 9 Jan 2017 21:18:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2017 21:18:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 2F436C162F for ; Mon, 9 Jan 2017 21:18:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.972 X-Spam-Level: X-Spam-Status: No, score=0.972 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id tPU6rDF0sywE for ; Mon, 9 Jan 2017 21:18:06 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 323575FBCF for ; Mon, 9 Jan 2017 21:18:06 +0000 (UTC) Received: from mtom.nabble.com (unknown [162.253.133.81]) by mbob.nabble.com (Postfix) with ESMTP id F41BE39E6FA6 for ; Mon, 9 Jan 2017 13:01:35 -0800 (PST) Date: Mon, 9 Jan 2017 12:43:12 -0700 (MST) From: bmichaud To: dev@nifi.apache.org Message-ID: <1483990992289-14416.post@n7.nabble.com> In-Reply-To: References: <1483970153864-14413.post@n7.nabble.com> Subject: Re: NiFi cannot start due to log permissions error MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Aldrin Piri wrote > Currently, NIFI_HOME is determined via the physical location of the script > and thus the reason why it is picking up the other path. Typically, the > bin directory is not one that is suggested to be configured external to > the > distribution in the interest of facilitating upgrade processes. I can see that in the nifi.sh script. Aldrin Piri wrote > I see throughout the logs and final stacktrace that the path > /app_2/software/nifi/nifi-1.1.0/ is listed, but do not see that in either > of the listings you provided. Could you please provide how that > relates to /app_2/software/nifi/latest? > Another symlink? Yes, "latest" is a symlink pointing to the latest nifi-1.*.* directory installed in the /app_2/software/nifi directory. Aldrin Piri wrote > Does explicitly setting your NIFI_HOME (/app_2/runtime/nifi) in > nifi-env.sh > resolve this issue for you? I did not try that, but, when I tried to change the nifi.sh to take the PHYS_DIR variable to be the dirname of $0, but that did not work. However, my current work-around is to have a copy of the bin directory in the runtime/nifi directory. I would prefer not to do this, as it does make upgrades messier, but I am currently more concerned about the next error I got: InvalidKeyException: Illegal key size and I am trying to resolve that with a smaller password on my keystore and truststore files. (https://issues.apache.org/jira/browse/NIFI-3062) -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/NiFi-cannot-start-due-to-log-permissions-error-tp14413p14416.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.