OT - running shell script displays an error message while it should not

[philippe.camelio_3885]

Hello

I have a shell script, which clone a git repo and run few command.
Directly from the server, it is working properly.

From Otter, as SHCall, it reports ERROR while is it just echo or result of the command line.
Results below of a small script shell

echo ==>  install-monitor sur $(hostname)
git clone https://oauth:********@********/monitor.git /opt/monitor

DEBUG: 2023-07-17 11:54:18Z - Job will be run against servers sequentially (not asynchronously).
DEBUG: 2023-07-17 11:54:18Z - Targeting servers: VMXXXXXX
DEBUG: 2023-07-17 11:54:18Z - Beginning execution run...
INFO : 2023-07-17 11:54:19Z - ==> install-monitor sur VMXXXXXX
ERROR: 2023-07-17 11:54:20Z - Cloning into '/opt/monitor'...

How to avoid such behaviour and keep real ERROR

I have plenty of working shell scripts I have to run through Otter

Best regards
Philippe

Running : Otter Version 2022.11 / docker

[atripp]

Hi @philippe-camelio_3885 ,

When text is written to the stderr stream, Otter will interpret this as an error. Unfortunately a few tools (including git) like to write to the stderr, even though it's not an error, and will use the exit code to indicate an error instead.

There are a handful of ways to deal with this:

• set ErrorOutputLogLevel in the SHExec operation
• use try/catch/force normal in OtterScript
• modify your script to redirect output

Redirecting is strongly recommended, and you can do it with 2>&1 in your script. Then you can test the exit code of the tool, and write to the error stream so Otter can pick it up as an error.

Cheers,
Alana

[philippe.camelio_3885]

Hi @atripp
Thanks for the tips.

Best regards

Philippe