Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Wed, 2 Nov 2016 13:04:58 +0000 (UTC)
From: "Arne Bachmann (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.13017218.1478091844000.157677.1478091898729@Atlassian.JIRA>
In-Reply-To: <JIRA.13017218.1478091844000@Atlassian.JIRA>
References: <JIRA.13017218.1478091844000@Atlassian.JIRA> <JIRA.13017218.1478091844302@arcas>
Subject: [jira] [Created] (ZOOKEEPER-2626) log4j.properties don't get
 respected
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 02 Nov 2016 13:05:05 -0000

Arne Bachmann created ZOOKEEPER-2626:
----------------------------------------

             Summary: log4j.properties don't get respected
                 Key: ZOOKEEPER-2626
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2626
             Project: ZooKeeper
          Issue Type: Bug
          Components: scripts
    Affects Versions: 3.5.2
         Environment: Linux vagrant-ubuntu-trusty-32 3.13.0-100-generic #147-Ubuntu SMP Tue Oct 18 16:49:53 UTC 2016 i686 i686 i686 GNU/Linux
            Reporter: Arne Bachmann


I put the log4j.properties into the conf folder, plus a symlink to the base zookeeper folder, as described in the documentation.
Neither of them seem to be picked up, as my rolling logger is not recognized (no logs created), and also bin/zkServer.sh print-cmd shows wrong logger configuration. Is that a problem of the start script or did I put the properties file into the wrong place?

Note however, that also my additional java command-line options (from JAVA_TOOL_OPTIONS) don't get picked up by the start script, as can be seen by ps aux | grep java (e.g. -Xmx1000m instead of -Xmx500 as I defined it).
The script's refer to a lot of environment variables that aren't explained in the documentation and nowhere defined; I can't get it to run.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)