Support Center > Search Results > SecureKnowledge Details
Stability fix for CPUSE build 839
Solution

CPUSE build 839 requires a stability fix for online self-update to the next CPUSE build.

Relevant fix (shell script) was downloaded to Gaia machines running CPUSE build 839 that are connected to Internet, if the following option was enabled (by default, it is enabled) in SmartDashboard: "Automatically download Contracts and other important data" (go to "Policy" menu - click on "Global Properties" - go to "Security Management Access").

Important Note: During the download of this shell script, no process is stopped/restarted on Gaia machine.

Notes:

  • This shell script will be executed in the next CPUSE online self-update to prevent the stability issue.
  • Manual offline update of CPUSE Agent per sk92449 from build 839 to a next build is not affected.
  • CPUSE builds other than 839 are not affected.

The downloaded shell script /opt/CPda/bin/DAClient:

OLD_DACLIENT=/opt/CPda/bin/bck_DAClient
DBGET=/bin/dbget
ECHO=/bin/echo
if [ "X$1" == "Xself_update" ]
  then
    for pkg in `$DBGET installer:packages -ic`
    do
      status=`$DBGET installer:packages:$pkg`
      type=`$DBGET installer:packages:$pkg:pkg_type`
      if [ "X$type" == "X3" -a "X$status" == "X4" ]
        then
          new_DA_filename=$pkg
          new_DA_pkgkey=`$DBGET installer:packages:$pkg:pkgkey`
      fi
    done
    if [ "X$new_DA_filename" == "X" -o "X$new_DA_pkgkey" == "X" ]
      then
        $ECHO "Error: Could not find currently installing DA"
        exit 1
    fi
    rpm_name=/opt/CPda/repository/$new_DA_pkgkey/CPda-00-00.i386.rpm
    file_name=/opt/CPda/repository/$new_DA_pkgkey/$new_DA_filename
    /opt/CPda/bin/su_script $rpm_name $file_name &
fi
$OLD_DACLIENT "$@"

 

Related solutions:

This solution is about products that are no longer supported and it will not be updated

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment