-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Insufficient permissions after version 3.1.8 upgrade to 3.2.0 #15976
Comments
Search before asking
What happenedAfter upgrading from version 3.1.8 to 3.2.0, an error is encountered in the execution of the Datax workflow: /tmp/dolphinscheduler/exec/process/dolphinscheduler/12899597581952/13432672120965_2/2121/14362/2121_14362_job.json
What you expected to happenI hope it works out. How to reproduceversion 3.1.8 upgrade to 3.2.0 Anything elseNo response Version3.2.x Are you willing to submit PR?
Code of Conduct
|
This may be a file permission bug, please try 3.2.1. |
@ruanwenjun 3.2.1 There's a problem turning the pages. Any ideas? |
Or you can manually fix this by following the dev branch, this should already be fixed. |
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs. |
Search before asking
What happened
After upgrading from version 3.1.8 to 3.2.0, an error is encountered in the execution of the Datax workflow:
/tmp/dolphinscheduler/exec/process/dolphinscheduler/12899597581952/13432672120965_2/2121/14362/2121_14362_job.json
[INFO] 2024-05-10 14:24:08.541 +0800 - Executing shell command : sudo -u dolphinscheduler -i /tmp/dolphinscheduler/exec/process/dolphinscheduler/12899597581952/13432672120965_2/2121/14362/2121_14362.sh
[INFO] 2024-05-10 14:24:08.543 +0800 - process start, process id is: 10664
[INFO] 2024-05-10 14:24:09.548 +0800 - ->
What you expected to happen
I hope it works out.
How to reproduce
version 3.1.8 upgrade to 3.2.0
Anything else
No response
Version
3.2.x
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: