what's your running mode?
if your flink cluster is on yarn mode,then the output you need has no relation 
to $FLINK_HOME/logs/*.out




------------------ ???????? ------------------
??????:                                                                         
                                               "sidhant gupta"                  
                                                                  
<sidhan...@gmail.com&gt;;
????????:&nbsp;2020??10??7??(??????) ????11:33
??????:&nbsp;"??????"<appleyu...@foxmail.com&gt;;"user"<user@flink.apache.org&gt;;

????:&nbsp;Re: The file STDOUT does not exist on the TaskExecutor



Hi,&nbsp;

I'm running flink cluster in ecs. There is a pipeline which creates the job 
manager and then the task manager using the docker image.


Not sure if we would want to restart the cluster in production.&nbsp;


Is there any way we can make sure the .out files will be created without 
restart ?&nbsp;


I am able to see the logs in the logs tab but not the stdout logs in the web ui 
and getting the below mentioned error after running the job.


Thanks
Sidhant Gupta


On Wed, Oct 7, 2020, 8:00 PM ?????? <appleyu...@foxmail.com&gt; wrote:

it's easy,
just restart your flink cluster(standalone mode)


if you run flink in yarn mode,then the result will display on 
$HADOOP/logs/*.out files


------------------&nbsp;????????&nbsp;------------------
??????:                                                                         
                                               "sidhant gupta"                  
                                                                  
<sidhan...@gmail.com&gt;;
????????:&nbsp;2020??10??7??(??????) ????9:52
??????:&nbsp;"??????"<appleyu...@foxmail.com&gt;;
????:&nbsp;"user"<user@flink.apache.org&gt;;
????:&nbsp;Re: The file STDOUT does not exist on the TaskExecutor



++ user

On Wed, Oct 7, 2020, 6:47 PM sidhant gupta <sidhan...@gmail.com&gt; wrote:

Hi&nbsp;

I checked in the&nbsp;$FLINK_HOME/logs. The .out file was not there. Can you 
suggest what should be the action item ?


Thanks
Sidhant Gupta


On Wed, Oct 7, 2020, 7:17 AM ?????? <appleyu...@foxmail.com&gt; wrote:



check if the .out file is in $FLINK_HOME/logs&nbsp; please.


------------------&nbsp;????????&nbsp;------------------
??????:                                                                         
                                               "sidhant gupta"                  
                                                                  
<sidhan...@gmail.com&gt;;
????????:&nbsp;2020??10??7??(??????) ????1:52
??????:&nbsp;"??????"<appleyu...@foxmail.com&gt;;

????:&nbsp;Re: The file STDOUT does not exist on the TaskExecutor



Hi,&nbsp;


I am just running the docker container as it is by adding just the 
conf/flink.yaml .
I am not sure if the .out file got deleted. Do we need to expose some ports ?


Thanks
Sidhant Gupta




On Tue, Oct 6, 2020, 8:51 PM ?????? <appleyu...@foxmail.com&gt; wrote:



Hi,I guess you may deleted .out file in $FLINK_HOME/logs.
you can just use your default log settings.
------------------&nbsp;????????&nbsp;------------------
??????:                                                                         
                                               "sidhant gupta"                  
                                                                  
<sidhan...@gmail.com&gt;;
????????:&nbsp;2020??10??6??(??????) ????10:59
??????:&nbsp;"user"<user@flink.apache.org&gt;;

????:&nbsp;The file STDOUT does not exist on the TaskExecutor



Hi,

I am running dockerized&nbsp;flink:1.11.0-scala_2.11&nbsp;container in ecs. I 
am getting the following&nbsp;error after the job runs:&nbsp;

ERROR 
org.apache.flink.runtime.rest.handler.taskmanager.TaskManagerStdoutFileHandler 
[] - Unhandled exception.
org.apache.flink.util.FlinkException: The file STDOUT does not exist on the 
TaskExecutor.
&nbsp;&nbsp;&nbsp;&nbsp;at 
org.apache.flink.runtime.taskexecutor.TaskExecutor.lambda$requestFileUploadByFilePath$25(TaskExecutor.java:1742)
 ~[flink-dist_2.11-1.11.0.jar:1.11.0]
&nbsp;&nbsp;&nbsp;&nbsp;at 
java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1604)
 ~[?:1.8.0_262]
&nbsp;&nbsp;&nbsp;&nbsp;at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
~[?:1.8.0_262]
&nbsp;&nbsp;&nbsp;&nbsp;at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
~[?:1.8.0_262]
&nbsp;&nbsp;&nbsp;&nbsp;at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_262]


I guess "file" needs to be added in log4j.properties in the docker container 
e.g. log4j.rootLogger=INFO, file
Are there any other properties which needs to be configured in any of the other 
property files or any jar needs to be added in the /opt/flink path ?
 Thanks
Sidhant Gupta

Reply via email to