You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2016/01/08 04:47:40 UTC
[jira] [Updated] (GEODE-232) gfsh prints ERROR StatusLogger
log4j2-cli.xml not found in file system or classpath
[ https://issues.apache.org/jira/browse/GEODE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Baker updated GEODE-232:
--------------------------------
Fix Version/s: (was: 1.0.0-incubating)
1.0.0-alpha1
> gfsh prints ERROR StatusLogger log4j2-cli.xml not found in file system or classpath
> -----------------------------------------------------------------------------------
>
> Key: GEODE-232
> URL: https://issues.apache.org/jira/browse/GEODE-232
> Project: Geode
> Issue Type: Bug
> Reporter: Eric Shu
> Assignee: Kirk Lund
> Priority: Critical
> Labels: gfsh
> Fix For: 1.0.0-alpha1
>
>
> ./open/gemfire-assembly/build/install/apache-geode/bin/gfsh
> ERROR StatusLogger File not found in file system or classpath: /com/gemstone/gemfire/internal/logging/log4j/log4j2-cli.xml
> ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
> _________________________ __
> / _____/ ______/ ______/ /____/ /
> / / __/ /___ /_____ / _____ /
> / /__/ / ____/ _____/ / / / /
> /______/_/ /______/_/ /_/ v1.0.0-incubating-SNAPSHOT
> Monitor and Manage GemFire
> gfsh>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)