git-blame commented on issue #15236:
URL:
https://github.com/apache/dolphinscheduler/issues/15236#issuecomment-1919171845
I have the same problem. The issue seems to be the file is placed with the
wrong path in the execution directory. The entire `file:/` URI is treated like
a directory path.
```log
[INFO] 2024-01-30 20:06:41.110 +0000 - get resource file from
path:file:/opt/apache-dolphinscheduler-3.2.0-bin/standalone-server/files/default/resources/hello.sh
[INFO] 2024-01-30 20:06:41.130 +0000 - Download resources:
{file:/opt/apache-dolphinscheduler-3.2.0-bin/standalone-server/files/default/resources/hello.sh=file:/opt/apache-dolphinscheduler-3.2.0-bin/standalone-server/files/default/resources/hello.sh}
successfully
...
[INFO] 2024-01-30 20:06:41.162 +0000 - Final Shell file is :
#!/bin/bash
BASEDIR=$(cd `dirname $0`; pwd)
cd $BASEDIR
echo "What's here: $BASEDIR"
find .
bash hello.sh
[INFO] 2024-01-30 20:06:41.164 +0000 - Executing shell command : sudo -u
root -i
/tmp/dolphinscheduler/exec/process/default/12443475537632/12443490756832_1/1/1/1_1.sh
[INFO] 2024-01-30 20:06:41.206 +0000 - process start, process id is: 43710
[INFO] 2024-01-30 20:06:42.204 +0000 - ->
What's here:
/tmp/dolphinscheduler/exec/process/default/12443475537632/12443490756832_1/1/1
.
./file:
./file:/opt
./file:/opt/apache-dolphinscheduler-3.2.0-bin
./file:/opt/apache-dolphinscheduler-3.2.0-bin/standalone-server
./file:/opt/apache-dolphinscheduler-3.2.0-bin/standalone-server/files
./file:/opt/apache-dolphinscheduler-3.2.0-bin/standalone-server/files/default
./file:/opt/apache-dolphinscheduler-3.2.0-bin/standalone-server/files/default/resources
./file:/opt/apache-dolphinscheduler-3.2.0-bin/standalone-server/files/default/resources/hello.sh
./1_1.sh
bash: hello.sh: No such file or directory
```
[1706645301047.log](https://github.com/apache/dolphinscheduler/files/14112667/1706645301047.log)
--
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]
