Usually this exit code means that some part of the job had a warning. However, the job could have done what you wanted it to do. If that is the case, I believe there is a hotfix available from Support which addresses this issue. Have you opened a ticket with them?
I'm using 184.108.40.2062 and I'm also receiving this error but the patches are being applied. Are there any updates on this. I did put in a ticket but I have had any resolution for over a month now.
Add me to the list. This is a deployment to a RHEL box using an external command. I tried a simple error trapping technique by including a "2>/dev/null" in my command & then specifying "exit 0" but still no luck. This is for a 220.127.116.116 AppServer & 18.104.22.168 agent.