[jira] [Updated] (HDDS-767) OM should not search for STDOUT root logger for audit logging
[
https://issues.apache.org/jira/browse/HDDS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton updated HDDS-767:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> OM should not search for STDOUT root logger for audit logging
> -
>
> Key: HDDS-767
> URL: https://issues.apache.org/jira/browse/HDDS-767
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
>Reporter: Dinesh Chitlangia
>Assignee: Dinesh Chitlangia
>Priority: Minor
> Labels: logging
> Attachments: HDDS-767.001.patch
>
>
> When we start ozone, the .out file shows the following line:
> {noformat}
> 2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
> logger config "root"{noformat}
> This is because the console appender has been disabled by default however
> incorrect log4j2 config is still trying to find the console appender.
>
> This Jira aims to comment the following config lines to avoid this issue:
> {code:java}
> rootLogger.appenderRefs=stdout
> rootLogger.appenderRef.stdout.ref=STDOUT
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-767) OM should not search for STDOUT root logger for audit logging
[
https://issues.apache.org/jira/browse/HDDS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anu Engineer updated HDDS-767:
--
Target Version/s: 0.4.0
> OM should not search for STDOUT root logger for audit logging
> -
>
> Key: HDDS-767
> URL: https://issues.apache.org/jira/browse/HDDS-767
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
>Reporter: Dinesh Chitlangia
>Assignee: Dinesh Chitlangia
>Priority: Minor
> Labels: logging
> Attachments: HDDS-767.001.patch
>
>
> When we start ozone, the .out file shows the following line:
> {noformat}
> 2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
> logger config "root"{noformat}
> This is because the console appender has been disabled by default however
> incorrect log4j2 config is still trying to find the console appender.
>
> This Jira aims to comment the following config lines to avoid this issue:
> {code:java}
> rootLogger.appenderRefs=stdout
> rootLogger.appenderRef.stdout.ref=STDOUT
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-767) OM should not search for STDOUT root logger for audit logging
[
https://issues.apache.org/jira/browse/HDDS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Chitlangia updated HDDS-767:
---
Component/s: Ozone Manager
> OM should not search for STDOUT root logger for audit logging
> -
>
> Key: HDDS-767
> URL: https://issues.apache.org/jira/browse/HDDS-767
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
>Reporter: Dinesh Chitlangia
>Assignee: Dinesh Chitlangia
>Priority: Minor
> Labels: logging
> Attachments: HDDS-767.001.patch
>
>
> When we start ozone, the .out file shows the following line:
> {noformat}
> 2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
> logger config "root"{noformat}
> This is because the console appender has been disabled by default however
> incorrect log4j2 config is still trying to find the console appender.
>
> This Jira aims to comment the following config lines to avoid this issue:
> {code:java}
> rootLogger.appenderRefs=stdout
> rootLogger.appenderRef.stdout.ref=STDOUT
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-767) OM should not search for STDOUT root logger for audit logging
[
https://issues.apache.org/jira/browse/HDDS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Chitlangia updated HDDS-767:
---
Labels: logging (was: )
> OM should not search for STDOUT root logger for audit logging
> -
>
> Key: HDDS-767
> URL: https://issues.apache.org/jira/browse/HDDS-767
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
>Reporter: Dinesh Chitlangia
>Assignee: Dinesh Chitlangia
>Priority: Minor
> Labels: logging
> Attachments: HDDS-767.001.patch
>
>
> When we start ozone, the .out file shows the following line:
> {noformat}
> 2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
> logger config "root"{noformat}
> This is because the console appender has been disabled by default however
> incorrect log4j2 config is still trying to find the console appender.
>
> This Jira aims to comment the following config lines to avoid this issue:
> {code:java}
> rootLogger.appenderRefs=stdout
> rootLogger.appenderRef.stdout.ref=STDOUT
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-767) OM should not search for STDOUT root logger for audit logging
[
https://issues.apache.org/jira/browse/HDDS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Chitlangia updated HDDS-767:
---
Attachment: HDDS-767.001.patch
Status: Patch Available (was: Open)
> OM should not search for STDOUT root logger for audit logging
> -
>
> Key: HDDS-767
> URL: https://issues.apache.org/jira/browse/HDDS-767
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
>Reporter: Dinesh Chitlangia
>Assignee: Dinesh Chitlangia
>Priority: Minor
> Attachments: HDDS-767.001.patch
>
>
> When we start ozone, the .out file shows the following line:
> {noformat}
> 2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
> logger config "root"{noformat}
> This is because the console appender has been disabled by default however
> incorrect log4j2 config is still trying to find the console appender.
>
> This Jira aims to comment the following config lines to avoid this issue:
> {code:java}
> rootLogger.appenderRefs=stdout
> rootLogger.appenderRef.stdout.ref=STDOUT
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-767) OM should not search for STDOUT root logger for audit logging
[
https://issues.apache.org/jira/browse/HDDS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Chitlangia updated HDDS-767:
---
Description:
When we start ozone, the .out file shows the following line:
{noformat}
2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
logger config "root"{noformat}
This is because the console appender has been disabled by default however
incorrect log4j2 config is still trying to find the console appender.
This Jira aims to comment the config lines to avoid this issue.
was:
When we start ozone, the .out file shows the following line:
{noformat}
2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
logger config "root"{noformat}
This is because the console appender has been disabled by default however
incorrect log4j2 config is still trying to find the console appender.
This Jira aims to remove the config lines to avoid this issue.
> OM should not search for STDOUT root logger for audit logging
> -
>
> Key: HDDS-767
> URL: https://issues.apache.org/jira/browse/HDDS-767
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
>Reporter: Dinesh Chitlangia
>Assignee: Dinesh Chitlangia
>Priority: Minor
>
> When we start ozone, the .out file shows the following line:
> {noformat}
> 2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
> logger config "root"{noformat}
> This is because the console appender has been disabled by default however
> incorrect log4j2 config is still trying to find the console appender.
>
> This Jira aims to comment the config lines to avoid this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-767) OM should not search for STDOUT root logger for audit logging
[
https://issues.apache.org/jira/browse/HDDS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Chitlangia updated HDDS-767:
---
Description:
When we start ozone, the .out file shows the following line:
{noformat}
2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
logger config "root"{noformat}
This is because the console appender has been disabled by default however
incorrect log4j2 config is still trying to find the console appender.
This Jira aims to comment the following config lines to avoid this issue:
{code:java}
rootLogger.appenderRefs=stdout
rootLogger.appenderRef.stdout.ref=STDOUT
{code}
was:
When we start ozone, the .out file shows the following line:
{noformat}
2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
logger config "root"{noformat}
This is because the console appender has been disabled by default however
incorrect log4j2 config is still trying to find the console appender.
This Jira aims to comment the config lines to avoid this issue.
> OM should not search for STDOUT root logger for audit logging
> -
>
> Key: HDDS-767
> URL: https://issues.apache.org/jira/browse/HDDS-767
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
>Reporter: Dinesh Chitlangia
>Assignee: Dinesh Chitlangia
>Priority: Minor
>
> When we start ozone, the .out file shows the following line:
> {noformat}
> 2018-10-31 00:48:04,141 main ERROR Unable to locate appender "STDOUT" for
> logger config "root"{noformat}
> This is because the console appender has been disabled by default however
> incorrect log4j2 config is still trying to find the console appender.
>
> This Jira aims to comment the following config lines to avoid this issue:
> {code:java}
> rootLogger.appenderRefs=stdout
> rootLogger.appenderRef.stdout.ref=STDOUT
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
