Common issues with Execute Command in Duaer

Execute Command is not in the node panel

For security, Duaer does not load Execute Command or Local File Trigger by default. A self-hosted admin can change the exclusion list with NODES_EXCLUDE, for example set it to [] to load every node, then restart. The node runs any command on the machine that runs Duaer, so give it only to people you trust.

Command failed: … not found

The shell running Duaer cannot find the command. Check that:

• The command and its arguments in Command have no typos.
• The command is on the PATH of the user running Duaer.
• With Docker, the command exists in the Duaer container. Try docker exec <container> <command>. If it is missing, build a custom image from your Duaer image with the command installed.

Command failed with exit code …

The command exited with a non-zero status. Duaer uses stderr as the error message, or the exit code when stderr is empty. Run the command by hand in the same environment to see its output.

Output is cut off

Duaer keeps only the last 10 MB of stdout and of stderr. Filter what you do not need with the command’s own flags or a pipe.

PowerShell commands stop at line breaks on Windows

The Windows shell treats a line break as the end of the command and runs only the first line. Put statements on one line separated by semicolons, for example powershell -Command "Get-ChildItem C:\Data; Write-Output 'Done'". For longer scripts, save a file and run powershell -File.