You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/02/24 10:45:00 UTC
[jira] [Closed] (FLINK-16237) Several places missing Log4j2
configuration property
[ https://issues.apache.org/jira/browse/FLINK-16237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-16237.
------------------------------------
Fix Version/s: 1.11.0
Resolution: Fixed
master: 99690832d812ca883bab1df9f96ffc523320438d
> Several places missing Log4j2 configuration property
> ----------------------------------------------------
>
> Key: FLINK-16237
> URL: https://issues.apache.org/jira/browse/FLINK-16237
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Reporter: Yangze Guo
> Assignee: Chesnay Schepler
> Priority: Blocker
> Labels: pull-request-available, test-stability
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Wordcount on Docker test (custom fs plugin) fails on Travis. [https://travis-ci.org/KarmaGYZ/flink/builds/653829954]
> {code:bash}
> pass WordCount
> Checking for errors...
> Found error in log files:
> Attaching to docker_job-cluster_1
> job-cluster_1 | Starting the job-cluster
> job-cluster_1 | Starting standalonejob as a console application on host 042c3c490edc.
> job-cluster_1 | ERROR StatusLogger No Log4j 2 configuration file found. Using default configuration (logging only errors to the console), or user programmatically provided configurations. Set system property 'log4j2.debug' to show Log4j 2 internal initialization logging. See https://logging.apache.org/log4j/2.x/manual/configuration.html for instructions on how to configure Log4j 2
> Attaching to docker_taskmanager_1
> taskmanager_1 | Starting the task-manager
> taskmanager_1 | Starting taskexecutor as a console application on host 059bd37e4232.
> taskmanager_1 | ERROR StatusLogger No Log4j 2 configuration file found. Using default configuration (logging only errors to the console), or user programmatically provided configurations. Set system property 'log4j2.debug' to show Log4j 2 internal initialization logging. See https://logging.apache.org/log4j/2.x/manual/configuration.html for instructions on how to configure Log4j 2
> Checking for exceptions...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)