Inaccurate Logging for tSystem Command Execution in Talend Pipeline

[Budapati]

Dear Community,

I'm encountering an issue where the logs generated by my Talend pipeline indicate that my pipeline's commands have been executed, even though these actions have not actually occurred. What is going wrong here?

(Top) This is my pipeline as shown above.

Here is the log :

But unfortunately, nothing is created as I did a file check in my Linux system where the pipeline executes. Likewise I have tried running commands like pwd, cd, ...etc. using tSystem and even when the Log says it ran properly, there's no visible outcome.

Looking for your advice and suggestions!

[gouravdubey5]

Hello,

tSystem captures standard output (stdout) only. Messages written by the external command to standard error (stderr) are not included in the Talend logs by default. This can make the logged output appear incomplete or inaccurate.

Recommended actions:

Redirect stderr to stdout when executing the command (for example 2>&1).

Alternatively, redirect both streams to a file and review the file content.

For full control over logging, execute the command using custom Java (ProcessBuilder) instead of tSystem.

Note:
The exit code reported by tSystem is accurate; missing messages usually come from stderr not being captured.

Thanks,

Gourav