1 2 3 Previous Next 40 Replies Latest reply: Dec 31, 2012 9:29 AM by Naren S Go to original post RSS
  • 15. Re: deploy failed exit code 11
    Jude Seth

    could you post the output of agentinfo on the target box?

  • 16. Re: deploy failed exit code 11
    Alessandro Iacopetti

    10.99.4.65:
      Agent Release   : 8.0.0.396
      Hostname        : s49mfced
      Operating System: WindowsNT 5.0
      User Permissions: BladeLogicRSCD@S49MFCED->Administrator@S49MFCED:PrivilegeMapped (Identity via trust)
      Security        : Protocol=5, Encryption=TLS1
      Host ID         : B8484E4A
      # of Processors : 2
      License Status  : Licensed for NSH/CM

     

    it's a citrix metaframe win2000 server

  • 17. Re: deploy failed exit code 11
    Kin Yiu

    Could you please post the content of the deploy log?

  • 18. Re: deploy failed exit code 11
    Alessandro Iacopetti

    this is the bldeploy-xxxx.log of the job run

    it failed the simulate stage with exit code 11

     

    10/14/10 09:02:38.662 INFO     bldeploy - Bldeploy started for package: 2e3b595a84ad3bc5af838eaa8a5df471
    10/14/10 09:02:38.662 DEBUG    bldeploy - Bldeploy Arguments:
    10/14/10 09:02:38.662 DEBUG    bldeploy - C:\Program Files\BladeLogic\RSC\sbin\bldeploy.exe
    10/14/10 09:02:38.662 DEBUG    bldeploy - 2e3b595a84ad3bc5af838eaa8a5df471
    10/14/10 09:02:38.662 DEBUG    bldeploy - -N=/tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471
    10/14/10 09:02:38.662 DEBUG    bldeploy - -P=10.99.4.65
    10/14/10 09:02:38.662 DEBUG    bldeploy - -Q=params.txt
    10/14/10 09:02:38.662 DEBUG    bldeploy - -DryRun
    10/14/10 09:02:38.662 DEBUG    bldeploy - -Xr
    10/14/10 09:02:38.662 DEBUG    bldeploy - -V1
    10/14/10 09:02:38.677 DEBUG    bldeploy - -js0
    10/14/10 09:02:38.677 DEBUG    bldeploy - -jr0
    10/14/10 09:02:38.677 DEBUG    bldeploy - -jc0
    10/14/10 09:02:38.677 DEBUG    bldeploy - -StartNew
    10/14/10 09:02:38.677 DEBUG    bldeploy - C:\Program Files\BladeLogic\RSC\sbin\bldeploy.exe  - 8.0.0.396
    10/14/10 09:02:38.677 INFO     bldeploy - Deployment job not in single-job mode. Reboot is not allowed. Any reboot requests by certa
    in file operations will be ignored.
    10/14/10 09:02:38.677 DEBUG    bldeploy - Cleanup staging area on failure
    10/14/10 09:03:08.677 DEBUG    bldeploy - Utilizing configuration file: C:\tmp\stage\2e3b595a84ad3bc5af838eaa8a5df471\2e3b595a84ad3b
    c5af838eaa8a5df471.cfg
    10/14/10 09:03:08.677 DEBUG    bldeploy - Fresh start of deployment, deleting any pre-existing configuration file
    10/14/10 09:03:10.927 DEBUG    bldeploy - Could not open file "C:\Program Files\BladeLogic\RSC\params.txt" for reading
    10/14/10 09:03:10.927 DEBUG    bldeploy -
    DEPLOYNAME = 2e3b595a84ad3bc5af838eaa8a5df471:
    DEPLOYPATH = C:\tmp\stage\2e3b595a84ad3bc5af838eaa8a5df471:
    FQHOST = s49mfced.ced.it:
    HOST = s49mfced:
    HOSTIP = 10.99.4.65:
    NAMESPACE = 10.99.4.65:
    ROLLBACKPATH = C:\Program Files\BladeLogic\RSC\Transactions\2e3b595a84ad3bc5af838eaa8a5df471:
    RSCDIR = C:\Program Files\BladeLogic\RSC:
    WINDIR = C:\WINNT:
    XMLFILEPATH = C:\tmp\stage\2e3b595a84ad3bc5af838eaa8a5df471\bldeploy.xml:
    10/14/10 09:03:10.927 DEBUG    bldeploy - Full command line C:\Program Files\BladeLogic\RSC\sbin\bldeploy.exe 2e3b595a84ad3bc5af838e
    aa8a5df471 -N=/tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471 -P=10.99.4.65 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0
    10/14/10 09:03:10.927 DEBUG    bldeploy -  Running as User: x☺É
    10/14/10 09:03:10.927 DEBUG    bldeploy -  Privileges:
    10/14/10 09:03:10.927 DEBUG    bldeploy -   SeChangeNotifyPrivilege - Enabled by default
    10/14/10 09:03:10.927 DEBUG    bldeploy -   SeUndockPrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeSecurityPrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeBackupPrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeRestorePrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeSystemtimePrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeShutdownPrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeRemoteShutdownPrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeTakeOwnershipPrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeDebugPrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeSystemEnvironmentPrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeSystemProfilePrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeProfileSingleProcessPrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeIncreaseBasePriorityPrivilege - Disabled
    10/14/10 09:03:10.943 DEBUG    bldeploy -   SeLoadDriverPrivilege - Disabled
    10/14/10 09:03:10.958 DEBUG    bldeploy -   SeCreatePagefilePrivilege - Disabled
    10/14/10 09:03:10.958 DEBUG    bldeploy -   SeIncreaseQuotaPrivilege - Disabled
    10/14/10 09:03:10.958 DEBUG    bldeploy -   SeCreateGlobalPrivilege - Enabled by default
    10/14/10 09:03:10.958 DEBUG    bldeploy - Validating existence of wait lock C:\Program Files\BladeLogic\RSC\Transactions\locks\reboo
    t.lck
    10/14/10 09:03:10.958 DEBUG    bldeploy - Deployment running in multi-job mode
    10/14/10 09:03:10.958 DEBUG    bldeploy - Read lock acquired release write lock
    10/14/10 09:03:10.958 DEBUG    bldeploy - Acquired appropriate lock: C:\Program Files\BladeLogic\RSC\Transactions\locks\reader\2e3b5
    95a84ad3bc5af838eaa8a5df471.lck
    10/14/10 09:03:10.958 DEBUG    bldeploy - Creating directory C:\Program Files\BladeLogic\RSC\Transactions\2e3b595a84ad3bc5af838eaa8a
    5df471
    10/14/10 09:03:10.974 INFO     bldeploy - Metabase initialization failed: 0x80040154
    10/14/10 09:03:10.974 INFO     bldeploy - Bldeploy 2e3b595a84ad3bc5af838eaa8a5df471 started using file C:\tmp\stage\2e3b595a84ad3bc5
    af838eaa8a5df471\bldeploy.xml with rollback directory C:\Program Files\BladeLogic\RSC\Transactions\2e3b595a84ad3bc5af838eaa8a5df471
    10/14/10 09:03:10.990 INFO     bldeploy - Starting dryRun
    10/14/10 09:03:10.990 DEBUG    bldeploy - [][] Dryrun id =
    10/14/10 09:03:10.990 DEBUG    bldeploy - [1][C:/cedacri-testfile-deploybl] Dryrun id = 1
    10/14/10 09:03:10.990 INFO     bldeploy - Dryrun succeeded
    10/14/10 09:03:10.990 DEBUG    bldeploy - Dryrun does not delete staging nor rollback directories
    10/14/10 09:03:10.990 DEBUG    bldeploy - DeletePkg = 0 DeleteUndo = 0
    10/14/10 09:03:10.990 DEBUG    bldeploy - Bldeploy done - nRet = 3 (DryRun successful) exitCode = 0 (Deployment succeeded)

     

     

     

     

     

     

     

    and this is the bltargetjobmanager-xxxx.log

     

    10/14/10 09:02:38.599 DEBUG    bldeploy - TJM invoked with arguments:
    10/14/10 09:02:38.599 DEBUG    bldeploy - args 0 = bltargetjobmanager
    10/14/10 09:02:38.599 DEBUG    bldeploy - args 1 = -start
    10/14/10 09:02:38.599 DEBUG    bldeploy - args 2 = -cmd
    10/14/10 09:02:38.599 DEBUG    bldeploy - args 3 = bldeploy 2e3b595a84ad3bc5af838eaa8a5df471 -N=/tmp/stage/2e3b595a84ad3bc5af838eaa8
    a5df471 -P=10.99.4.65 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0
    10/14/10 09:02:38.599 DEBUG    bldeploy - args 4 = -me
    10/14/10 09:02:38.599 DEBUG    bldeploy - args 5 = 2e3b595a84ad3bc5af838eaa8a5df471
    10/14/10 09:02:38.599 DEBUG    bldeploy - args 6 = -mp
    10/14/10 09:02:38.599 DEBUG    bldeploy - args 7 = -sp
    10/14/10 09:02:38.599 DEBUG    bldeploy - args 8 = -ps
    10/14/10 09:02:38.599 DEBUG    bldeploy - args 9 = -h60
    10/14/10 09:02:38.599 DEBUG    bldeploy - BlTargetJobManager started
    10/14/10 09:02:38.599 DEBUG    bldeploy - Commandline: bltargetjobmanager -start -cmd bldeploy 2e3b595a84ad3bc5af838eaa8a5df471 -N=/
    tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471 -P=10.99.4.65 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0  -me 2e3b595a84ad3bc5af838eaa8
    a5df471 -mp -sp -ps -h60
    10/14/10 09:02:38.615 DEBUG    bldeploy - Executing "C:\Program Files\BladeLogic\RSC\sbin\bldeploy.exe" 2e3b595a84ad3bc5af838eaa8a5d
    f471 -N=/tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471 -P=10.99.4.65 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0  -StartNew
    10/14/10 09:02:38.615 DEBUG    bldeploy - ProcessExecutor::createProcess batchFile=, cmd="C:\Program Files\BladeLogic\RSC\sbin\bldep
    loy.exe" 2e3b595a84ad3bc5af838eaa8a5df471 -N=/tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471 -P=10.99.4.65 -Q=params.txt -DryRun -Xr -V1
    -js0 -jr0 -jc0  -StartNew, cmdDir=

  • 19. Re: deploy failed exit code 11
    Kin Yiu

    Sorry to ask you to post the deploy log again, I just realized it is included in your original message already.

     

    The deploy log looks fine, but the Target Job Manager logs is incomplete, which is a sign of it terminated abnormally probably due to memory violation (which is also exit code 11). There should be an event logged in the Windows Event Log. If that's the case, then I am afraid that you'd need to file a ticket with support. Sorry.

  • 20. Re: deploy failed exit code 11
    Alessandro Iacopetti

    nothing's in the evenlog

    i will open a ticket

  • 21. deploy failed exit code 11
    David Hawkes

    Did you ever get this fixed?

  • 22. Re: deploy failed exit code 11
    adoneo

    Be sure that you dont have a bad automation principal in the RBAC manager for mapping the rol  that you are using to deploy the jos, in case that you have something, remove first the automation principal just to test the Deploy Job Again.

  • 23. Re: deploy failed exit code 11
    Lazar NameToUpdate

    When Deploy Job is executed, the RSCD Agent launches bltargetjobmanager.exe (tjm), which launches bldeploy.exe. Once tjm launches bldeploy, it awaits for the bldeploy pid. In your case, in tjm log you do not see the PID of bldeploy returned, so tjm assumes that something went wrong and returns exit code 11 to RSCD, which returns 11 to the Job. In the mean time bldeploy.exe actually runs and completes the DRYRUN (simulate phase) successfully. This is why you do not see exit code 11 in bldeploy log.

     

    The fact that tjm failed to acquire pid of the bldeploy.exe is the issue here, and we're presently working on a fix. No ETA at this time yet.

     

    ---------

    EDIT:

     

    all relevant information can be found here:

     

    KA375237 - BBSA Windows Deploy Job error: DRYRUN failed for server [target]. Exit code = 11

    https://kb.bmc.com/infocenter/index?page=content&id=KA375237

     

    Message was edited by: Lazar

  • 24. Re: deploy failed exit code 11
    Lazar NameToUpdate

    Since there was no ETA at the time of "correct answer", felt obligated to pass this along...

     

    This issue to be resolved on the agent side in versions:

    8.2 SP3

    8.1 SP6

    8.1 SP5 Patch 2

     

    The fix is only within one file - bladmin.dll in rscd_dir folder, so you can simply replace the file to resolve the issue. This is how we intend to deliver this fix for all other versions. If immediate fix required by anyone, feel free to respond here (or file a ticket) with your agent version and windows os version/arch. I'll provide the ftp location for the dll files.

  • 25. Re: deploy failed exit code 11
    William L. Thomas, Jr.

    When will BSA 8.2 SP3 be released?

     

    Wasn't BSA 8.2 SP1 released just a couple of months ago?

  • 26. Re: deploy failed exit code 11
    Lazar NameToUpdate

    8.2 SP3 will probably be out within 3 months (not really sure)

    Yes - about 8.2 SP1

    8.2 SP2 will be out very soon.

     

    the dlls can also be available for 8.2 ga/sp1/sp2

  • 27. Re: deploy failed exit code 11
    Kyle.Sorg NameToUpdate

    In the job options if you set it to commit only the job will stage but fail on commit.  Is there a work around to install the patches?  This seems to only happen on a few servers.

  • 28. Re: deploy failed exit code 11
    Lazar NameToUpdate

    Hi Kyle, it's the same issue. You need the fixed dll. I've already provided you teh dll, but if you have new agents where this happens, tell me the agent version and arch, and I'll provide correct bladmin.dll.

  • 29. Re: deploy failed exit code 11
    Kyle.Sorg NameToUpdate

    We are using 8.2.1.288.  So far we only found two servers to have this problem.  Why would it occur on only two out of hundreds?

     

    Can you send me that file?