rmetzger commented on pull request #12240: URL: https://github.com/apache/flink/pull/12240#issuecomment-669188970
While testing the change, I found that I can not access the TaskManager logs: ``` $ kubectl logs yolo-taskmanager-1-1 Start command : /bin/bash -c $JAVA_HOME/bin/java -classpath $FLINK_CLASSPATH -Xmx205520892 -Xms205520892 -XX:MaxDirectMemorySize=202165453 -XX:MaxMetaspaceSize=268435456 org.apache.flink.kubernetes.taskmanager.KubernetesTaskExecutorRunner -D taskmanager.memory.framework.off-heap.size=134217728b -D taskmanager.memory.network.max=67947725b -D taskmanager.memory.network.min=67947725b -D taskmanager.memory.framework.heap.size=134217728b -D taskmanager.memory.managed.size=271790903b -D taskmanager.cpu.cores=1.0 -D taskmanager.memory.task.heap.size=71303164b -D taskmanager.memory.task.off-heap.size=0b --configDir /opt/flink/conf -Dweb.tmpdir='/tmp/flink-web-dca91753-58da-4d06-90e3-31ae03e17931' 1> /opt/flink/log/taskmanager.out 2> /opt/flink/log/taskmanager.err ``` also via the JobManager Web UI, the TM logs are not accessible. It seems that not .log file has been created. The taskmanger.err contains: ``` # more taskmanager.err ERROR StatusLogger No Log4j 2 configuration file found. Using default configuration (logging only errors to the conso le), or user programmatically provided configurations. Set system property 'log4j2.debug' to show Log4j 2 internal in itialization logging. See https://logging.apache.org/log4j/2.x/manual/configuration.html for instructions on how to c onfigure Log4j 2 ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
