7 Replies Latest reply on Apr 29, 2019 1:38 PM by Adriano Gomes

    Automatic Solaris agent upgrade issues

    Mohamed Rashid
      Share This:


      facing an issue while upgrading the Control-M agent from CCM (automatic deployment)


      OS version is Solaris : SunOS 5.11 sun4v sparc sun4v

      Upgrading from .


      Installation log s


      19-04-25 15:06:04: Communication with CTM Server using new binaries succeeded, RC=0


      19-04-25 15:06:04: Package_Install Start ... -> AGENT_HOME=/controlm/ctm700


      # A fatal error has been detected by the Java Runtime Environment:


      #  SIGSEGV (0xb) at pc=0xfb81a598, pid=16752, tid=2


      # JRE version: Java(TM) SE Runtime Environment (7.0_51-b13) (build 1.7.0_51-b13)

      # Java VM: Java HotSpot(TM) Server VM (24.51-b03 mixed mode solaris-sparc )

      # Problematic frame:

      # j  java.util.HashMap.putForCreate(Ljava/lang/Object;Ljava/lang/Object;)V+42


      # Core dump written. Default location: /controlm/ctm700/core or core.16752


      # An error report file with more information is saved as:

      # /controlm/ctm700/hs_err_pid16752.log


      # If you would like to submit a bug report, please visit:

      #   http://bugreport.sun.com/bugreport/crash.jsp


      /controlm/ctm700/ctm/temp/DRKAI.9.0.00_Solaris.tar.Z_ctm700/setup.sh: line 386: 16752: Abort(coredump)

      19-04-25 15:06:10: Install: system_rc = 134

      19-04-25 15:06:10: Function setagstate start

      Action=INSTALL, file_extension=.Z, system_rc=134, setagstate=setagstate

      19-04-25 15:06:10: "/controlm/ctm700/ctm/temp/DRKAI.9.0.00_Solaris.tar.Z_ctm700/Setup_files/setagstate" DeploymentUpdate Deployment_Failed 25 0 0 0 0 "Control-M/Agent Upgrade Failed please see installation log"

      Status 'DeploymentUpdate' sent successfully to CTM server

      Server Response:







      MsgText=Control-M/Agent Upgrade Failed please see installation log


      19-04-25 15:06:10 rc=0

      19-04-25 15:06:10: Function setagstate end

      19-04-25 15:06:10

      ERR_MSG=Control-M/Agent Upgrade process aborted due to Install of file /controlm/ctm700/ctm/temp/DRKAI.9.0.00_Solaris.tar.Z Failed


      14:38:40.248     1           IsDiskSpaceSufficient.checkDiskSpaceSufficient[72] Path /controlm/ctm700/@{INSTALL_PATH} contains -1024 bytes free.

        • 1. Re: Automatic Solaris agent upgrade issues
          Adriano Gomes

          Hi Mohamed Rashid


          I would first start by double checking file system free space for ctmagent user is enough to receive the Z file and have it extracted prior installation begin.

          Also, java version is too low.

          If this is the only one of a kind, I would do the installation manually, by scp the install file and invoking it locally thus saving time troubleshooting.



          1 of 1 people found this helpful
          • 2. Re: Automatic Solaris agent upgrade issues
            Mohamed Rashid


            Java version is latest --


            -bash-4.4$ java -version

            java version "1.8.0_191"

            Java(TM) SE Runtime Environment (build 1.8.0_191-b12)

            Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)


            Enough space as well

            -bash-4.4$ df -h .

            Filesystem             Size   Used  Available Capacity  Mounted on

            rpool/ctmarch           10G    34K        10G     1%    /ctmarch


            Still no idea what is the causing this issue


            i want to get this done through deployment tool only


            current version is

            Agent Platform Architecture    : Solaris-sparcv9

            Agent Version                  :

            • 3. Re: Automatic Solaris agent upgrade issues
              Adriano Gomes



              I am very sorry it did not helped!  Is  not clear that  diskpace is enough:


              Was df -h issued from current agent home? Can you grep ctmagent user from /etc/passw ?

              Output says mounted on /ctmarch but the path where the file is to be extracted is /controlm/ctm700/!

              The output mention this  /controlm/ctm700/hs_err_pid16752.log file? Can you attach it along with installation.log ?







              • 4. Re: Automatic Solaris agent upgrade issues
                Mohamed Rashid


                yes you are right, agent home directory has enough space , it was typo


                df -h .

                Filesystem             Size   Used  Available Capacity  Mounted on

                controlm_pool           24G   2.9G        22G    12%    /controlm

                • 5. Re: Automatic Solaris agent upgrade issues
                  Juan Pablo Ojeda

                  is agent running as root , or as a different user?


                  how about system limits?  (ulimit)


                  also, double check for any symbolic links... maybe... (just thinking out loud), somebody, made one and agent ctm/temp directory ended up outside the Control/M filesystem.

                  • 6. Re: Automatic Solaris agent upgrade issues
                    Adriano Gomes

                    Hi Mohamed Rashid


                    Thanks for clarifying!

                    Do you mind browse over the /controlm/ctm700/hs_err_pid16752.log file ?


                    I would recommend you to register BMC case ID, so you can get assisted.

                    As there is space available, and the output says there is an core dumped error on setup.sh line 386, the process may be getting wrong info from available disk space from OS.


                    If you want to get this troubleshooted, try to perform the steps manually.


                    On the deploy Activity screen , select "Transfer Package" only ind order to DEPLOY the install file and run installation the steps for yourself.

                    Extract the Z file and invoke setup.sh -silent <silent file>

                    see what will happen.


                    My Best



                    • 7. Re: Automatic Solaris agent upgrade issues
                      Adriano Gomes

                      Hi Mohamed Rashid




                      by Checking the Setup.sh installation script, it seems that it is using system java, not the Agent home Java.


                      would you be able to type "which java" and validate from which path it is being first taken?

                      You may be able to have java version (build 1.7.0_51-b13) being taken from system in order to run BMC remote java installer as of line 386.


                      In order to workaround, you may be able to change/Add JAVA_HOME to default shell profile file and also make the JAVA_HOME first in the path.


                      Lastly, the procedure also validate /tmp from 100MB free space.


                      I hope you make it.