berg-xu opened a new issue #7881:
URL: https://github.com/apache/dolphinscheduler/issues/7881


   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   
按照[官方开发者文档](https://dolphinscheduler.apache.org/zh-cn/development/development-environment-setup.html)描述,IDEA本地启动DS,并创建简单的工作流SHELL任务,最终任务执行状态为失败。查看日志的时候,明确指出日志文件所在路径,但是IDEA
 控制台提示该日志文件不存在,导致页面查询不到日志信息。 请教该如何处理???
   
   
![d20f62b4033b5013dd74e76db7e293a](https://user-images.githubusercontent.com/45385723/148523973-42af9014-668f-4d47-9762-a594d10e1b50.png)
   
   
![1e976581d1cea966eaf0509245831da](https://user-images.githubusercontent.com/45385723/148523992-bbf491e6-2e3f-494a-be0d-dec7fd0300f4.png)
   
   
![2e23ab6c3391f21757f30770652b614](https://user-images.githubusercontent.com/45385723/148524016-27907b1c-6c90-4dcb-914d-7c220ae37078.png)
   
   
   该如何解决这个问题?
   
   
   
   ### What you expected to happen
   
   
按照[官方开发者文档](https://dolphinscheduler.apache.org/zh-cn/development/development-environment-setup.html)描述,IDEA本地启动DS,并创建简单的工作流SHELL任务,最终任务执行状态为失败。查看日志的时候,明确指出日志文件所在路径,但是IDEA
 控制台提示该日志文件不存在,导致页面查询不到日志信息。 请教该如何处理???
   
   ### How to reproduce
   
   
按照[官方开发者文档](https://dolphinscheduler.apache.org/zh-cn/development/development-environment-setup.html)描述,IDEA本地启动DS,并创建简单的工作流SHELL任务,最终任务执行状态为失败。查看日志的时候,明确指出日志文件所在路径,但是IDEA
 控制台提示该日志文件不存在,导致页面查询不到日志信息。 请教该如何处理???
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   2.0.1
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to