1 2 Previous Next 22 Replies Latest reply: May 16, 2012 7:53 AM by Steven Wyns RSS

    Exit Codes

    Rick L

      I am working on running an OS Patching job, I create the patch analysis job, then pull the patches which are missing from the analysis job and create a deployment job.  When I go to execute the deployment job; when it hits the "Commit" attemp I get an "Exit code = -5005"  Apply failed - any idea where #1 I can look up some of the most common exit codes; and #2 why this is occurring?  Thanks in advance - Rick L.

        • 1. Re: Exit Codes
          Paul Seager-Smith

          Rick,

           

          Which OS is this? Windows and each Unix variant are all handled slightly differently. You should also get a few more clues in the logs to try and identify the root cause. Can you paste the log file entries just before and including this entry?

           

          Rgds,

           

          Paul

          • 2. Re: Exit Codes
            Young So

            Can you post the job logs?

            • 3. Re: Exit Codes

              I'm getting the same 5005 exit code on some of my Windows servers when I deploy a BLpackage.  The package gets pushed successfully via repeater (I can see it in the staging folder), but then it nothing else happens.  Here are the three relevant lines from the (cleaned up) rscd.log:

               

              09/17/09 19:54:20.813 INFO1    rscd -  x.x.x.x 7724 BladeLogicRSCD@Host_Name->default_admin@Host_Name:PrivilegeMapped (Role:User): Remote File Server: > Remote File Server: Copying from ---Staging_Server---:/REPEATER_STAGING/blpackages/V0017341---All-78-@2009.09.16-09.27.08.502-0500-2075386.1 to the target //Host_Name/tmp/stage/V0017341---All-78-@2009.09.16-09.27.08.502-0500-2075386.1-2106826.9
              09/17/09 19:54:34.485 INFO1    rscd -  x.x.x.x 8064 BladeLogicRSCD@Host_Name->default_admin@Host_Name:PrivilegeMapped (Role:User): CM: > [Deploy] Job 'V0017341 - All @2009-09-16 09:27:56:864-0500' is applying
              09/17/09 19:54:39.704 INFO1    rscd -  x.x.x.x 8064 BladeLogicRSCD@Host_Name->default_admin@Host_Name:PrivilegeMapped (Role:User): CM: > [Deploy] Deleting //Host_Name/C/Program Files/BladeLogic/RSC/Transactions/log/tmp/bldeploy-V0017341---All-78-@2009.09.16-09.27.08.502-0500-2075386.1-2106826.9.log

               

              And here's the log from the BL CM:

               

              Error Sep 17, 2009 2:53:44 PM Application terminated unexpectedly 
              Error Sep 17, 2009 2:53:46 PM Apply failed for server target_server. Exit code = -5005 
              Info Sep 17, 2009 2:53:40 PM Started running the deploy step job 'V0017341 - All @2009-09-16 09:27:56:864-0500->V0017341 - All @2009-09-16 09:27:56:864-0500 (Apply)' on application server 'blapp3_2JobServer'(2,023,000) against target server 'target_server' 
              Info Sep 17, 2009 2:53:44 PM Package V0017341---All-78-@2009.09.16-09.27.08.502-0500-2075386.1-2106826.9 started 
              Info Sep 17, 2009 2:53:45 PM exitCode = -5005 (Application terminated unexpectedly) 
              Info Sep 17, 2009 2:53:46 PM The job 'V0017341 - All @2009-09-16 09:27:56:864-0500->V0017341 - All @2009-09-16 09:27:56:864-0500 (Apply)' has failed on server target_server 
              Info Sep 17, 2009 7:54:35 PM Deployment job not in single-job mode. Reboot is not allowed. Any reboot requests by certain file operations will be ignored.
               

              • 4. Re: Exit Codes
                Benjamin Turner

                Hi,

                 

                Did anyone have an answer to this issue as I’m getting this error deploying Control M, it goes through the staging area fine but when it goes to do the final deploy it errors with exit code 5005.

                 

                any help on this error would be appreciated.

                 

                cheers Ben

                • 5. Re: Exit Codes
                  Greg Kullberg

                  I take it you're getting this during the simulate phase of the deploy?  I know there was a hotfix that addressed a 5005 error code.  What version of BL are you running?

                  • 6. Re: Exit Codes
                    Benjamin Turner

                    Hi,

                     

                    I’m running version 7.6.0 and this errors occurs when the deploy job commits...

                     

                    any ideas would be appreciated.

                     

                    cheers

                    • 7. Re: Exit Codes
                      Adam Bowen

                      I can try and assist.

                       

                       

                      Is this a new install or an upgrade? Can you post the lines from your rscd.log for the deploy job. Also, can you post your exports, users, and users.local file? I would also open a ticket with BMC support, if you have not already done so.

                      • 8. Re: Exit Codes
                        Steven Wyns

                        I wonder if it was solved. It would at least be nice to post the soluion then

                         

                        Anyway, I'm recieveing the same error:

                        Also the bltargetjobmanager log states:

                        04/12/12 07:45:27.809 DEBUG    bldeploy - TJM invoked with arguments:

                        04/12/12 07:45:27.809 DEBUG    bldeploy - args 0 = bltargetjobmanager

                        04/12/12 07:45:27.809 DEBUG    bldeploy - args 1 = -start

                        04/12/12 07:45:27.809 DEBUG    bldeploy - args 2 = -cmd

                        04/12/12 07:45:27.809 DEBUG    bldeploy - args 3 = bldeploy BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -N=/temp/stage/BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -P=target1 -Q=params.txt -V2 -RegAllCOM -TreatLockedAsErr -js0 -jr0 -jc0

                        04/12/12 07:45:27.809 DEBUG    bldeploy - args 4 = -me

                        04/12/12 07:45:27.809 DEBUG    bldeploy - args 5 = BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22

                        04/12/12 07:45:27.809 DEBUG    bldeploy - args 6 = -mp

                        04/12/12 07:45:27.809 DEBUG    bldeploy - args 7 = -sp

                        04/12/12 07:45:27.809 DEBUG    bldeploy - args 8 = -ps

                        04/12/12 07:45:27.809 DEBUG    bldeploy - args 9 = -h60

                        04/12/12 07:45:27.809 DEBUG    bldeploy - BlTargetJobManager started

                        04/12/12 07:45:27.809 DEBUG    bldeploy - Commandline: bltargetjobmanager -start -cmd bldeploy BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -N=/temp/stage/BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -P=target1 -Q=params.txt -V2 -RegAllCOM -TreatLockedAsErr -js0 -jr0 -jc0  -me BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -mp -sp -ps -h60

                        04/12/12 07:45:29.075 DEBUG    bldeploy - Executing "C:\Program Files\BMC BladeLogic\RSC\sbin\bldeploy.exe" BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -N=/temp/stage/BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -P=target1 -Q=params.txt -V2 -RegAllCOM -TreatLockedAsErr -js0 -jr0 -jc0  -StartNew

                        04/12/12 07:45:29.075 DEBUG    bldeploy - ProcessExecutor::createProcess batchFile=, cmd="C:\Program Files\BMC BladeLogic\RSC\sbin\bldeploy.exe" BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -N=/temp/stage/BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -P=target1 -Q=params.txt -V2 -RegAllCOM -TreatLockedAsErr -js0 -jr0 -jc0  -StartNew, cmdDir=

                        04/12/12 07:45:29.684 DEBUG    bldeploy - _bl_get_proc_list did not return a valid list. User permissions may not allow access, switching to ValidatePIDActive(PID) function

                        04/12/12 07:45:29.684 DEBUG    bldeploy - Command has started

                        04/12/12 07:45:30.184 DEBUG    bldeploy - _bl_get_proc_list did not return a valid list. User permissions may not allow access, switching to ValidatePIDActive(PID) function

                        04/12/12 07:45:31.684 DEBUG    bldeploy - Received from PID=5660 EVENT=STARTED MSG=Package BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 started

                        04/12/12 07:45:32.200 DEBUG    bldeploy - _bl_get_proc_list did not return a valid list. User permissions may not allow access, switching to ValidatePIDActive(PID) function

                        04/12/12 07:45:33.700 DEBUG    bldeploy - _bl_get_proc_list did not return a valid list. User permissions may not allow access, switching to ValidatePIDActive(PID) function

                        04/12/12 07:45:34.700 DEBUG    bldeploy - PID not valid 5660 for bldeploy

                        04/12/12 07:45:34.731 ERROR    bldeploy - Application terminated unexpectedly

                        04/12/12 07:45:35.231 DEBUG    bldeploy - Deleted event file: C:\Program Files\BMC BladeLogic\RSC\Transactions\events\BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22.out

                        04/12/12 07:45:35.747 DEBUG    bldeploy - Deleted event file: C:\Program Files\BMC BladeLogic\RSC\Transactions\events\BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22.in

                        04/12/12 07:45:35.747 DEBUG    bldeploy - TJM generated Exit message: exitCode=-5005: MSG=exitCode = -5005 (Application terminated unexpectedly):

                        04/12/12 07:45:35.747 DEBUG    bldeploy - Operation complete return code -5005

                         

                        We get this on one 2008 server. I would expect something has changed in the security settings since all other servers don't complain. And it worked before 15th of january.

                         

                        It seems the bldeploy.exe just segfaults.

                         

                        Has anyone seen this before?

                        • 9. Re: Exit Codes
                          Bill Robinson

                          can you paste the bldeploy log ?

                          • 10. Re: Exit Codes
                            Steven Wyns

                            Offcource.

                             

                            Iv'e started from the moment the dryrun succeeded and the actual commit starts.

                             

                            04/12/12 07:45:16.716 INFO     bldeploy - Dryrun succeeded
                            04/12/12 07:45:16.747 DEBUG    bldeploy - Dryrun does not delete staging nor rollback directories
                            04/12/12 07:45:16.747 DEBUG    bldeploy - DeletePkg = 0 DeleteUndo = 0
                            04/12/12 07:45:17.263 DEBUG    bldeploy - Bldeploy done - nRet = 3 (DryRun successful) exitCode = 0 (Deployment succeeded)

                            04/12/12 07:45:29.356 INFO     bldeploy - Bldeploy started for package: BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22
                            04/12/12 07:45:29.356 DEBUG    bldeploy - Bldeploy Arguments:
                            04/12/12 07:45:29.356 DEBUG    bldeploy - C:\Program Files\BMC BladeLogic\RSC\sbin\bldeploy.exe
                            04/12/12 07:45:29.356 DEBUG    bldeploy - BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22
                            04/12/12 07:45:29.356 DEBUG    bldeploy - -N=/temp/stage/BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22
                            04/12/12 07:45:29.356 DEBUG    bldeploy - -P=target1
                            04/12/12 07:45:29.356 DEBUG    bldeploy - -Q=params.txt
                            04/12/12 07:45:29.356 DEBUG    bldeploy - -V2
                            04/12/12 07:45:29.356 DEBUG    bldeploy - -RegAllCOM
                            04/12/12 07:45:29.356 DEBUG    bldeploy - -TreatLockedAsErr
                            04/12/12 07:45:29.356 DEBUG    bldeploy - -js0
                            04/12/12 07:45:29.356 DEBUG    bldeploy - -jr0
                            04/12/12 07:45:29.356 DEBUG    bldeploy - -jc0
                            04/12/12 07:45:29.356 DEBUG    bldeploy - -StartNew
                            04/12/12 07:45:29.356 DEBUG    bldeploy - C:\Program Files\BMC BladeLogic\RSC\sbin\bldeploy.exe  - 7.6.0.115
                            04/12/12 07:45:29.356 INFO     bldeploy - Deployment job not in single-job mode. Reboot is not allowed. Any reboot requests by certain file operations will be ignored.
                            04/12/12 07:45:29.372 DEBUG    bldeploy - Cleanup staging area on failure
                            04/12/12 07:45:32.137 DEBUG    bldeploy - Utilizing configuration file: C:\temp\stage\BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22\BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22.cfg
                            04/12/12 07:45:32.137 DEBUG    bldeploy - Fresh start of deployment, deleting any pre-existing configuration file
                            04/12/12 07:45:34.387 DEBUG    bldeploy - Could not open file "C:\Program Files\BMC BladeLogic\RSC\params.txt" for reading
                            04/12/12 07:45:34.387 DEBUG    bldeploy -
                            DEPLOYNAME = BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22:
                            DEPLOYPATH = C:\temp\stage\BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22:
                            FQHOST = target1:
                            HOST = S0A00097:
                            HOSTIP = 10.208.131.12:
                            NAMESPACE = target1:
                            ROLLBACKPATH = C:\Program Files\BMC BladeLogic\RSC\Transactions\BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22:
                            RSCDIR = C:\Program Files\BMC BladeLogic\RSC:
                            WINDIR = C:\Windows:
                            XMLFILEPATH = C:\temp\stage\BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22\bldeploy.xml:
                            04/12/12 07:45:34.403 DEBUG    bldeploy - Full command line C:\Program Files\BMC BladeLogic\RSC\sbin\bldeploy.exe BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -N=/temp/stage/BLP-PT3-DummyA0-v1.0.2-2000896.1-2000185.22 -P=target1 -Q=params.txt -V2 -RegAllCOM -TreatLockedAsErr -js0 -jr0 -jc0
                            04/12/12 07:45:34.403 DEBUG    bldeploy -  Running as User: BladeLogicRSCD
                            04/12/12 07:45:34.403 DEBUG    bldeploy -  Privileges:
                            04/12/12 07:45:34.403 DEBUG    bldeploy -   SeAssignPrimaryTokenPrivilege - Disabled
                            04/12/12 07:45:34.403 DEBUG    bldeploy -   SeIncreaseQuotaPrivilege - Disabled
                            04/12/12 07:45:34.403 DEBUG    bldeploy -   SeTcbPrivilege - Disabled
                            04/12/12 07:45:34.403 DEBUG    bldeploy -   SeSecurityPrivilege - Disabled
                            04/12/12 07:45:34.403 DEBUG    bldeploy -   SeTakeOwnershipPrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeLoadDriverPrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeSystemProfilePrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeSystemtimePrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeProfileSingleProcessPrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeIncreaseBasePriorityPrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeCreatePagefilePrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeBackupPrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeRestorePrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeShutdownPrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeDebugPrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeSystemEnvironmentPrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeChangeNotifyPrivilege - Enabled by default
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeRemoteShutdownPrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeUndockPrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeManageVolumePrivilege - Disabled
                            04/12/12 07:45:34.418 DEBUG    bldeploy -   SeImpersonatePrivilege - Enabled by default
                            04/12/12 07:45:34.434 DEBUG    bldeploy -   SeCreateGlobalPrivilege - Enabled by default
                            04/12/12 07:45:34.434 DEBUG    bldeploy -   SeIncreaseWorkingSetPrivilege - Disabled
                            04/12/12 07:45:34.434 DEBUG    bldeploy -   SeTimeZonePrivilege - Disabled
                            04/12/12 07:45:34.434 DEBUG    bldeploy -   SeCreateSymbolicLinkPrivilege - Disabled

                             

                            And suddenly the logging stops. The next lines are from later deployment tests. I've tried to follow the deployment via procmon (pstools) but I'm unable to find the cause. The system was working before and an audit to compare hotfixes, applications and security setting with a working machine doesn't give much either.

                            • 11. Re: Exit Codes
                              Prabhat Handoo

                              What is the version of the appserver here? The agent is 7.6, there might be compatiablity issues. The fact 5005 is quite a generic error.

                              • 12. Re: Exit Codes
                                Prabhat Handoo

                                Also it seems that you have the GA build of 7.6. You may want to upgrade the agent to the latest fix for 7.6 if your appserver is also on 7.6

                                • 13. Exit Codes
                                  Steven Wyns

                                  Appserver is 7.6.0.313 en agent 7.6.0.115 but that agent version is on almost all the machines. I've even reïnstalled the agent. Maybe I should try a later fix.

                                  • 14. Re: Exit Codes
                                    Monoj Padhy

                                    just try it out by selecting "copy loked file option" and uncheck registry COM component in the phasse option o the deploy job.

                                     

                                    find the attched screenshot and let me know if it works for you.

                                    1 2 Previous Next