2 Replies Latest reply on Jun 5, 2012 2:27 PM by Daniel Goetzman

    Deploying patrol agent with BBSA

    Basilio Urrutia

      Hi,

       

      I'm trying to deploy the patrol agent in a server Sparc but I coudn't have success.

       

      The install command for the custom software is: " ??SOURCE??/install.sh" -path ??SOURCE??  

      In the BLpackage in the box "Cmd" is configured with: "./install.sh"

       

      I received the following errors when I execute the job:

      Info     Jun 4, 2012 2:44:04 PM      [stdout: 1]

      1     instPatrol

      Info     Jun 4, 2012 2:44:04 PM      [stdout: 1]

      1     instPatrol

      Info     Jun 4, 2012 2:44:04 PM      [stdout: 1]      ---> Error: install.sh: "/var/tmp/stage/4adc93da0ccb3c049e3d1c7f511503bc/Install" is not a valid directory for argument "-working".

      1     instPatrol

      Info     Jun 4, 2012 2:44:04 PM     ---> Warning: install.sh: running silent install as root is not advised

       

      Error     Jun 4, 2012 2:44:04 PM     Apply failed, no rollback.

       

      Error     Jun 4, 2012 2:44:04 PM      Apply failed: id = 1

      1     instPatrol

      Error     Jun 4, 2012 2:42:24 PM     APPLY failed for server 192.168.60.41. Exit code = -4001

      Info     Jun 4, 2012 2:44:04 PM     Bldeploy "DeployPatrolAgent-2000044.5-0.13053770428760147" UUID(8fb68b21844131dc974130950bb2e162) started using file /var/tmp/stage/4adc93da0ccb3c049e3d1c7f511503bc/bldeploy.xml with rollback directory /opt/bmc/bladelogic/RSCD/Transactions/8fb68b21844131dc974130950bb2e162

       

      Error     Jun 4, 2012 2:44:04 PM      Command returned non-zero exit code: 1

      1     instPatrol

      Info     Jun 4, 2012 2:42:17 PM     Deploy Apply Job (Pre-Execute):DeployPatrolAgent; Server:192.168.60.41;  PkgID:"DeployPatrolAgent-2000044.5-0.13053770428760147-2000140.1-2000044.5"; UUID:8fb68b21844131dc974130950bb2e162

      Warning     Jun 4, 2012 2:44:04 PM     Deploy failed. Cleaning up staging area.

       

      Info     Jun 4, 2012 2:44:03 PM     Deployment job not in single-job mode. Reboot and single-user mode is not allowed

       

      Info     Jun 4, 2012 2:44:04 PM      Executing command: ""2000100.1/instPatrol/install.sh" -path 2000100.1/instPatrol"

      1     instPatrol

      Info     Jun 4, 2012 2:42:21 PM     Package "DeployPatrolAgent-2000044.5-0.13053770428760147" UUID(8fb68b21844131dc974130950bb2e162) completed. exitCode = -4001 (Apply failed no rollback was created)

      Info     Jun 4, 2012 2:42:19 PM     Package "DeployPatrolAgent-2000044.5-0.13053770428760147" UUID(8fb68b21844131dc974130950bb2e162) initialized, entering wait queue for processing

      Info     Jun 4, 2012 2:42:19 PM     Package "DeployPatrolAgent-2000044.5-0.13053770428760147" UUID(8fb68b21844131dc974130950bb2e162) processing instructions

      Info     Jun 4, 2012 2:42:18 PM     Package "DeployPatrolAgent-2000044.5-0.13053770428760147" UUID(8fb68b21844131dc974130950bb2e162) started

      Info     Jun 4, 2012 2:44:04 PM      Processing asset BLPACKAGE

       

      Info     Jun 4, 2012 2:44:04 PM      Processing asset CUSTOMSOFTWARE

      1     instPatrol

      Info     Jun 4, 2012 2:42:17 PM     Started running the deploy step job 'DeployPatrolAgent->DeployPatrolAgent' on application server 'ice-bbsa'(2,000,000) against target server '192.168.60.41'

      Info     Jun 4, 2012 2:44:04 PM     Starting apply

       

      Info     Jun 4, 2012 2:42:24 PM     The job 'DeployPatrolAgent->DeployPatrolAgent' has failed on server 192.168.60.41

      Info     Jun 4, 2012 2:44:04 PM     Unknown return code type for directory delete settings: 4

       

       

      Thanks for the help!!

        • 1. Re: Deploying patrol agent with BBSA

          Do you see a "/var/tmp/stage/ directory on the target server?

           

          Change the settings in your job to "preserve staging area on failure". Run the job again. When the job fails this time, see if you can navigate into the /var/tmp/stage//Install directory and manually kickoff the install from there. My guess is that there is a permissions issue or  some other issue with creating the directory.

          1 of 1 people found this helpful
          • 2. Re: Deploying patrol agent with BBSA
            Daniel Goetzman

            Not sure if this is exactly the same problem we had using Custom Software Packages for the Patrol installer when using a remote source (Agent mounts source at install time)…

             

            IIRC, the way the remote mount is done by the agent has several levels of sym-link redirects and the Patrol Installer is not happy with that. I had to make an adjustment to call the installer from its real mount point to get it working on Unix with Custom Package using remote source.

             

            Looking at my Custom Software package when specifying the Installable Source as a NFS mount path, I had to use the following work around in the Install Command;

             

            MNT=`ls –l ??SOURCE?? | cut –f2 –d’>’ | tail -1`

            su – patrol –c “cd $/patrol_agent/unix && ./install.sh

             

            You might have to tweak this some to match your paths under the remote SOURCE.

            Essentially it grabs where the sym-link used by the agent points to, does a cd to there and THEN calls the Patrol Installer.

             

            It’s been working AOK for us and allows us to take advantage of using Custom Software remote mount to not drop the installer on the local target disk!

            -Dan