Solaris Patchadd or Bigfix?

(imported topic written by symbios91)

My environment consists of quite a no. of Solaris 10 servers and we are getting very strange results using Bigfix to patch our servers. For one instance, we are patching “SunOS 5.10: ldap tools patch” using the fixlet without any modifcations, all actions showed up as completed but relevance check fails the action. Upon checking the Solaris server, we found that the patch did not go through at all.

BES Client logs show exit code 5 while running “wait patchadd /tmp/140772-1”. We tried a few times and we just couldn’t patch it using Bigfix. When we run a manual patch on the server “patchadd /tmp/140772-1” the patch was installed. We proceeded to patchrm it and deploy the patch using Bigfix again and it goes through.

Logs didn’t tell us much about what happen and why it returned a exit code 5. We wanted to pipe the stdout and stderr out but the “wait” command don’t seems to let us do it. Does anyone know how we could determine whether this is a patchadd issue or Bigfix Client issue?

(imported comment written by brock9191)

Was curious if there was anything that you came up with that got this working. I am running into the same issue. Everything individually looks to have completed, overall says it failed, and patch is not showing up on machine.