treasure-data / digdag

Workload Automation System
https://www.digdag.io/
Apache License 2.0
1.3k stars 221 forks source link

Failed to run workflow on Digdag server #27

Closed komamitsu closed 8 years ago

komamitsu commented 8 years ago

When I ran a workflow on Digdag server running in localhost, this error occurred.

2016-04-05 11:21:09 +0900 [INFO] (0037@+main+step1): sh>: ./tasks/bin/enc-tool -e development-ec2 -a 1 -c ENCRYPT -t 200
/bin/sh: ./tasks/bin/enc-tool: Permission denied
2016-04-05 11:21:09 +0900 [ERROR] (0037@+main+step1): Task failed
java.lang.RuntimeException: Command failed with code 126
        at io.digdag.standards.operator.ShOperatorFactory$ShOperator.runTask(ShOperatorFactory.java:115)
        at io.digdag.standards.operator.BaseOperator.run(BaseOperator.java:49)
        at io.digdag.core.agent.OperatorManager.callExecutor(OperatorManager.java:241)
        at io.digdag.core.agent.OperatorManager.runWithWorkspace(OperatorManager.java:196)
        at io.digdag.core.agent.OperatorManager.lambda$runWithHeartbeat$1(OperatorManager.java:133)
        at io.digdag.core.agent.LocalWorkspaceManager.withExtractedArchive(LocalWorkspaceManager.java:63)
        at io.digdag.core.agent.OperatorManager.runWithHeartbeat(OperatorManager.java:132)
        at io.digdag.core.agent.OperatorManager.run(OperatorManager.java:109)
        at io.digdag.core.agent.LocalAgent.lambda$run$0(LocalAgent.java:61)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

It works in local mode.

frsyuki commented 8 years ago

The cause is that push command (and archive command) doesn't save file modes (like 0755). Server also ignores the modes. This needs to be fixed...

frsyuki commented 8 years ago

cd41657123fb8cf20b9d487aea9ea1a4cf3e0569 and 1373dd341460b66771f69b4487d0b6f71325197c fix this issue. v0.5.7 includes those commits.