1 2 3 Previous Next 40 Replies Latest reply on Dec 31, 2012 9:29 AM by Naren S

deploy failed exit code 11

Alessandro Iacopetti Sep 23, 2010 3:34 AM

i'm having troubles deploying blpackages on a server

i've tried even with a test blpackage that only contains an empty file

deploy job fails with exit code 11

here is the job log

it fails even the simulate stage

Info    Sep 23, 2010 10:01:17 AM    Deploy Dry Run Job:TestDeploy; Server:10.99.4.65; PkgID:"TestDeploy-22732.1-65143.4"; UUID:2e3b595a84ad3bc5af838eaa8a5df471
Info    Sep 23, 2010 10:01:17 AM    Started running the deploy step job 'TestDeploy->TestDeploy' on application server 'bl01ap1c'(1) against target server '10.99.4.65'
Error    Sep 23, 2010 10:01:18 AM    DRYRUN failed for server 10.99.4.65. Exit code = 11
Error    Sep 23, 2010 10:01:18 AM    TestDeploy->TestDeploy failed on server 10.99.4.65 exit code = 11
Info    Sep 23, 2010 10:01:18 AM    The job 'TestDeploy->TestDeploy' has failed on server 10.99.4.65

on the agent, here are the transactions logs

i don't see where the exit code 11 comes from

it seems successfull

10# cat bltargetjobmanager-2e3b595a84ad3bc5af838eaa8a5df471.log
09/23/10 10:01:18.581 DEBUG    bldeploy - TJM invoked with arguments:
09/23/10 10:01:18.581 DEBUG    bldeploy - args 0 = bltargetjobmanager
09/23/10 10:01:18.581 DEBUG    bldeploy - args 1 = -start
09/23/10 10:01:18.581 DEBUG    bldeploy - args 2 = -cmd
09/23/10 10:01:18.581 DEBUG    bldeploy - args 3 = bldeploy 2e3b595a84ad3bc5af838eaa8a5df471 -N=/tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471 -P=10.99.4.65 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0
09/23/10 10:01:18.581 DEBUG    bldeploy - args 4 = -me
09/23/10 10:01:18.581 DEBUG    bldeploy - args 5 = 2e3b595a84ad3bc5af838eaa8a5df471
09/23/10 10:01:18.581 DEBUG    bldeploy - args 6 = -mp
09/23/10 10:01:18.581 DEBUG    bldeploy - args 7 = -sp
09/23/10 10:01:18.581 DEBUG    bldeploy - args 8 = -ps
09/23/10 10:01:18.581 DEBUG    bldeploy - args 9 = -h60
09/23/10 10:01:18.581 DEBUG    bldeploy - BlTargetJobManager started
09/23/10 10:01:18.581 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 2e3b595a84ad3bc5af838eaa8a5df471 -mp -sp -ps -h60
09/23/10 10:01:18.597 DEBUG    bldeploy - Executing "C:\Program Files\BladeLogic\RSC\sbin\bldeploy.exe" 2e3b595a84ad3bc5af838eaa8a5df471 -N=/tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471 -P=10.99.4.65 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0 -StartNew
09/23/10 10:01:18.597 DEBUG    bldeploy - ProcessExecutor::createProcess batchFile=, cmd="C:\Program Files\BladeLogic\RSC\sbin\bldeploy.exe" 2e3b595a84ad3bc5af838eaa8a5df471 -N=/tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471 -P=10.99.4.65 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0 -StartNew, cmdDir=
10# cat bldeploy-2e3b595a84ad3bc5af838eaa8a5df471.log
09/23/10 10:01:18.691 INFO     bldeploy - Bldeploy started for package: 2e3b595a84ad3bc5af838eaa8a5df471
09/23/10 10:01:18.691 DEBUG    bldeploy - Bldeploy Arguments:
09/23/10 10:01:18.691 DEBUG    bldeploy - C:\Program Files\BladeLogic\RSC\sbin\bldeploy.exe
09/23/10 10:01:18.691 DEBUG    bldeploy - 2e3b595a84ad3bc5af838eaa8a5df471
09/23/10 10:01:18.691 DEBUG    bldeploy - -N=/tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471
09/23/10 10:01:18.691 DEBUG    bldeploy - -P=10.99.4.65
09/23/10 10:01:18.691 DEBUG    bldeploy - -Q=params.txt
09/23/10 10:01:18.691 DEBUG    bldeploy - -DryRun
09/23/10 10:01:18.691 DEBUG    bldeploy - -Xr
09/23/10 10:01:18.691 DEBUG    bldeploy - -V1
09/23/10 10:01:18.691 DEBUG    bldeploy - -js0
09/23/10 10:01:18.691 DEBUG    bldeploy - -jr0
09/23/10 10:01:18.691 DEBUG    bldeploy - -jc0
09/23/10 10:01:18.691 DEBUG    bldeploy - -StartNew
09/23/10 10:01:18.691 DEBUG    bldeploy - C:\Program Files\BladeLogic\RSC\sbin\bldeploy.exe - 8.0.0.396
09/23/10 10:01:18.706 INFO     bldeploy - Deployment job not in single-job mode. Reboot is not allowed. Any reboot requests by certain file operations will be ignored.
09/23/10 10:01:18.706 DEBUG    bldeploy - Cleanup staging area on failure
09/23/10 10:01:48.722 DEBUG    bldeploy - Utilizing configuration file: C:\tmp\stage\2e3b595a84ad3bc5af838eaa8a5df471\2e3b595a84ad3bc5af838eaa8a5df471.cfg
09/23/10 10:01:48.722 DEBUG    bldeploy - Fresh start of deployment, deleting any pre-existing configuration file
09/23/10 10:01:50.972 DEBUG    bldeploy - Could not open file "C:\Program Files\BladeLogic\RSC\params.txt" for reading
09/23/10 10:01:50.972 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:
09/23/10 10:01:50.972 DEBUG    bldeploy - Full command line C:\Program Files\BladeLogic\RSC\sbin\bldeploy.exe 2e3b595a84ad3bc5af838eaa8a5df471 -N=/tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471 -P=10.99.4.65 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0
09/23/10 10:01:50.988 DEBUG    bldeploy - Running as User: x
09/23/10 10:01:50.988 DEBUG    bldeploy - Privileges:
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeChangeNotifyPrivilege - Enabled by default
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeUndockPrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeSecurityPrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeBackupPrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeRestorePrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeSystemtimePrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeShutdownPrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeRemoteShutdownPrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeTakeOwnershipPrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeDebugPrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeSystemEnvironmentPrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeSystemProfilePrivilege - Disabled
09/23/10 10:01:50.988 DEBUG    bldeploy -   SeProfileSingleProcessPrivilege - Disabled
09/23/10 10:01:51.003 DEBUG    bldeploy -   SeIncreaseBasePriorityPrivilege - Disabled
09/23/10 10:01:51.003 DEBUG    bldeploy -   SeLoadDriverPrivilege - Disabled
09/23/10 10:01:51.003 DEBUG    bldeploy -   SeCreatePagefilePrivilege - Disabled
09/23/10 10:01:51.003 DEBUG    bldeploy -   SeIncreaseQuotaPrivilege - Disabled
09/23/10 10:01:51.003 DEBUG    bldeploy -   SeCreateGlobalPrivilege - Enabled by default
09/23/10 10:01:51.003 DEBUG    bldeploy - Validating existence of wait lock C:\Program Files\BladeLogic\RSC\Transactions\locks\reboot.lck
09/23/10 10:01:51.003 DEBUG    bldeploy - Deployment running in multi-job mode
09/23/10 10:01:51.003 DEBUG    bldeploy - Read lock acquired release write lock
09/23/10 10:01:51.003 DEBUG    bldeploy - Acquired appropriate lock: C:\Program Files\BladeLogic\RSC\Transactions\locks\reader\2e3b595a84ad3bc5af838eaa8a5df471.lck
09/23/10 10:01:51.019 DEBUG    bldeploy - Creating directory C:\Program Files\BladeLogic\RSC\Transactions\2e3b595a84ad3bc5af838eaa8a5df471
09/23/10 10:01:51.035 INFO     bldeploy - Metabase initialization failed: 0x80040154
09/23/10 10:01:51.035 INFO     bldeploy - Bldeploy 2e3b595a84ad3bc5af838eaa8a5df471 started using file C:\tmp\stage\2e3b595a84ad3bc5af838eaa8a5df471\bldeploy.xml with rollback directory C:\Program Files\BladeLogic\RSC\Transactions\2e3b595a84ad3bc5af838eaa8a5df471
09/23/10 10:01:51.035 INFO     bldeploy - Starting dryRun
09/23/10 10:01:51.035 DEBUG    bldeploy - [][] Dryrun id =
09/23/10 10:01:51.035 DEBUG    bldeploy - [1][C:/cedacri-testfile-deploybl] Dryrun id = 1
09/23/10 10:01:51.035 INFO     bldeploy - Dryrun succeeded
09/23/10 10:01:51.050 DEBUG    bldeploy - Dryrun does not delete staging nor rollback directories
09/23/10 10:01:51.050 DEBUG    bldeploy - DeletePkg = 0 DeleteUndo = 0
09/23/10 10:01:51.050 DEBUG    bldeploy - Bldeploy done - nRet = 3 (DryRun successful) exitCode = 0 (Deployment succeeded)

1. Re: deploy failed exit code 11

Adam Bowen Sep 23, 2010 6:07 AM (in response to Alessandro Iacopetti)

What about the appserver logs for the deploy?
Like Show 0 Likes(0)

Actions
2. Re: deploy failed exit code 11

Alessandro Iacopetti Sep 23, 2010 7:38 AM (in response to Adam Bowen)

10# grep -e TestDeploy -e 10.99.4.65 appserver.log
[23 Sep 2010 10:01:10,788] [Job-Execution-9] [INFO] [cr10117@CEDACRISPA.CED.IT:BLAdmins:] [Deploy] Started running the job 'TestDeploy' on application server 'BL01AP1C'(1)
[23 Sep 2010 10:01:15,413] [Job-Execution-9] [INFO] [cr10117@CEDACRISPA.CED.IT:BLAdmins:] [Deploy] Invoking: "d:/BladeLogic/OM/NSH/bin/du" -s -k //10.99.3.152/s/storage/blpackages/TestDeploy-22732.1
[23 Sep 2010 10:01:15,444] [Job-Execution-9] [INFO] [cr10117@CEDACRISPA.CED.IT:BLAdmins:] [Deploy] Executing command : "d:/BladeLogic/OM/NSH/bin/du" -s -k //10.99.3.152/s/storage/blpackages/TestDeploy-22732.1
[23 Sep 2010 10:01:15,444] [Job-Execution-9] [INFO] [cr10117@CEDACRISPA.CED.IT:BLAdmins:] [Deploy] Started pid 6912: "d:/BladeLogic/OM/NSH/bin/du" -s -k //10.99.3.152/s/storage/blpackages/TestDeploy-22732.1
[23 Sep 2010 10:01:17,335] [Lightweight-WorkItem-Thread-0] [INFO] [cr10117@CEDACRISPA.CED.IT:BLAdmins:] [Deploy] Executing work item Deploy Dry Run Job:TestDeploy; Server:10.99.4.65; on application server: BL01AP1C
[23 Sep 2010 10:01:18,272] [Lightweight-WorkItem-Thread-0] [INFO] [cr10117@CEDACRISPA.CED.IT:BLAdmins:] [Deploy] executing command bltargetjobmanager -start -cmd "bldeploy 2e3b595a84ad3bc5af838eaa8a5df471 -N="/tmp/stage/2e3b595a84ad3bc5af838eaa8a5df471" -P=10.99.4.65 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0 " -me "2e3b595a84ad3bc5af838eaa8a5df471" -mp -sp -ps -h60 on server 10.99.4.65
[23 Sep 2010 10:01:18,757] [Lightweight-WorkItem-Thread-0] [ERROR] [cr10117@CEDACRISPA.CED.IT:BLAdmins:] [Deploy] DRYRUN failed for server 10.99.4.65. Exit code = 11
[23 Sep 2010 10:01:18,819] [Lightweight-WorkItem-Thread-0] [ERROR] [cr10117@CEDACRISPA.CED.IT:BLAdmins:] [Deploy] TestDeploy->TestDeploy failed on server 10.99.4.65 exit code = 11
[23 Sep 2010 10:01:19,007] [Job-Execution-3] [INFO] [cr10117@CEDACRISPA.CED.IT:BLAdmins:] [Deploy] Phase: Dry-run completed with errors for target: 10.99.4.65
[23 Sep 2010 10:01:19,491] [Job-Execution-3] [INFO] [cr10117@CEDACRISPA.CED.IT:BLAdmins:] [Deploy] The job 'TestDeploy' has failed

still no clue
Like Show 0 Likes(0)

Actions
3. Re: deploy failed exit code 11

Adam Bowen Sep 23, 2010 8:43 AM (in response to Alessandro Iacopetti)

Well, I seen in your previous log that it said it couldn’t read the params.txt What are your permissions on the target’s /tmp/stage ?
Like Show 0 Likes(0)

Actions
4. Re: deploy failed exit code 11

Paul Seager-Smith Sep 23, 2010 9:21 AM (in response to Alessandro Iacopetti)

I have sometimes had a problem similar to this where the job has incorrect information. Usually in this case, recreating the deploy job from the depot object will work. Have you tried this?

Regards,

Paul
Like Show 0 Likes(0)

Actions
5. Re: deploy failed exit code 11

Alessandro Iacopetti Sep 23, 2010 9:41 AM (in response to Adam Bowen)

/tmp/stage/xxxxxx/params.txt exists and is empty while bldeploy.xml is non-empty
Like Show 0 Likes(0)

Actions
6. Re: deploy failed exit code 11

Alessandro Iacopetti Sep 23, 2010 9:43 AM (in response to Paul Seager-Smith)

this is a brand new job, a test one, because the production one failed and i tried to reproduce the error on another job (and i succeeded :-)
Like Show 0 Likes(0)

Actions
7. Re: deploy failed exit code 11

Bill Robinson Sep 23, 2010 5:07 PM (in response to Alessandro Iacopetti)

i always get that error about params.txt, for even successful deploys btw.

can you turn up debugging on the transactions log?
Like Show 0 Likes(0)

Actions
8. Re: deploy failed exit code 11

Alessandro Iacopetti Sep 24, 2010 2:56 AM (in response to Bill Robinson)

do you mean the log4crc.tx stuff on the agent side?
Like Show 0 Likes(0)

Actions
9. Re: deploy failed exit code 11

Adam Bowen Sep 24, 2010 7:29 AM (in response to Alessandro Iacopetti)

Set your job to only do the simulate phase. If that works do the stage as well. If that works, execute the commit commands manually from DOS. That is what I normally do.
Like Show 1 Likes(1)

Actions
10. Re: deploy failed exit code 11

Alessandro Iacopetti Sep 24, 2010 7:39 AM (in response to Adam Bowen)

it already fails the simulate phase
Like Show 0 Likes(0)

Actions
11. Re: deploy failed exit code 11

Adam Bowen Sep 24, 2010 7:43 AM (in response to Alessandro Iacopetti)

Is the target a Windows or Solaris server? Simulate tests permissions of the stage director and disk space.
Like Show 0 Likes(0)

Actions
12. Re: deploy failed exit code 11

Alessandro Iacopetti Sep 28, 2010 10:22 AM (in response to Adam Bowen)

it a win server
disk space is plenty and permissions seems right
i tried to create a dummy file via nsh successfully
Like Show 0 Likes(0)

Actions
13. Re: deploy failed exit code 11

Adam Bowen Sep 28, 2010 10:26 AM (in response to Alessandro Iacopetti)

You only use nsh-install-defaults with unix servers. You have to record an iss file for Windows agents. There is a different procedure outlined for doing this in the guide.
Like Show 0 Likes(0)

Actions
14. Re: deploy failed exit code 11

Kin Yiu Oct 1, 2010 12:31 PM (in response to Alessandro Iacopetti)

Hi there,

Here is the explaination of Windows system code 11:
-----------------------------------------
ERROR_BAD_FORMAT
11 (0xB)
An attempt was made to load a program with an incorrect format.
-----------------------------------------

There may be something wrong with the installation of the agent/deploy on that target. The weird thing is the Target Job Manager said the deploy actaully started and completed successfully, so it is unclear of what "program" has an incorrect format. It'd be helpful to check the deploy log as well (if one is generated).
1 of 1 people found this helpful
Like Show 0 Likes(0)

Actions