Why does the commands for changeLogSyncSQL, listLocks, etc. writes to stdErr

I am running the liquibase commands and noticing that my scripts to run liquibase commands are failing but when I looked into the log it say successful. After further investigation, it looks like the message is being routed by default to stdErr.

The engine my scripts are running fails when there is message in stdErr.

Any reason why?


Hi @leovic0101 ,

Assuming you are not using the set -e command, you can try adding this to your script. Read more about set -e here: The Linux Set Command (linuxhint.com)

If this doesn’t solve this issue, please let me know the steps to reproduce this scenario.