wow, I met similar situation using flink 1.7 on yarn. there was no jobmanager.log on the node but jobmanager.out and jobmanager.error, and jobmanager.error contains the log message. so , there was nothing in the webUI.
I do not know why this happened. by the way, I used logback to do log staff. On Thu, Dec 20, 2018 at 12:50 AM Steven Nelson <snel...@sourceallies.com> wrote: > There is a known issue for this I believe. The problem is that the > containerized versions of Flink output logs to STDOUT instead of files > inside the node. If you pull use docker logs on the container you can see > what you’re looking for. I use the Kube dashboard to view the logs > centrally. > > Sent from my iPhone > > > On Dec 19, 2018, at 9:40 AM, William Saar <will...@saar.se> wrote: > > > > > > I'm running Flink 1.7 in ECS, is this a known issue or should I create a > jira? > > > > The web console doesn't show anything when trying to list logs or stdout > for task managers and the job manager log have stack traces for the errors > > 2018-12-19 15:35:53,498 ERROR > org.apache.flink.runtime.rest.handler.taskmanager.TaskManagerStdoutFileHandler > - Failed to transfer file from TaskExecutor > d7fd266047d5acfaddeb1156bdb23ff3. > > java.util.concurrent.CompletionException: > org.apache.flink.util.FlinkException: The file STDOUT is not available on > the TaskExecutor. > > > > 2018-12-19 15:36:02,538 ERROR > org.apache.flink.runtime.rest.handler.taskmanager.TaskManagerLogFileHandler > - Failed to transfer file from TaskExecutor > d7fd266047d5acfaddeb1156bdb23ff3. > > java.util.concurrent.CompletionException: > org.apache.flink.util.FlinkException: The file LOG is not available on the > TaskExecutor. > > >
