nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OD Errors - I'm stumped

Lex

Let me preface this by saying that I know just enough about OpenDeploy to be dangerous. I copied an existing OD deployment configuration and then modified it for a new deployment. However, whenever I try to call this deployment (from some Perl code) the attached errors are generated in the odbase.log file. I have also attached my deployment configuration file. Does anyone have any idea what the issue might be? Thanks.

Find more posts tagged with

Comments

nipper

How are you kicking it off ? The deployment requires command line parameters for area vpapth and a few others.

Also, you are using a parameter for the Deployment name. I am not certain if that is supported (it certainly could be, but I have never implemented like that). Typically you will have multiple deployments defined (maybe Test and Prod) and use a command line switch to choose the correct one.

Andy

Lex

It's being called using the iwodstart CLT:

my $command = "d:\\od-home\\bin\\iwodstart $cfg -inst " . GetLUID() . " -k myarea=$area,mysite=$site,myfilelist=$filelist,myfarm=$farm -V verbose";

system("$command");

$cfg is d:\od-home\conf\Intranet_Immediate_Deploy.xml
$area is \default\main\Internal\Intranet\Teamsite\WORKAREA\Teamsite
$site is Teamsite
$filelist is d:\iw-home\tmp\Intranet_Deploy.5602
$farm is Deploy_Test

The idea is that I would have one single deployment configuration which handled the deployment to both test and production (which works with all of our other deployments). I can always split it out into two and see if that works.

nipper

If you say that works in another box, no biggie.

FYI, I do not know if this is the issue or not but iwodstart is old, it has been replaced with

iwod [command] deployment etc

Have you dumped the command to a log file and tried running it by hand ? Is there possibly a LF after one of the parameters so the variables are truncated ? My guess would be area.

Lex

OK, I've done what I should have done a long time ago: I hardcoded everything in the deployment configuration file and then using the OD Admin UI I started the deployment. It immediately comes back with this error:

Intranet_Immediate_Deploy
Failed to processing config file d:\od-home\conf\Intranet_Immediate_Deploy.xml

The odbase.log has this:

ENG: 2007-08-22 09:49:47 PDT GMT-07:00 Received request to start deployment Intranet_Immediate_Deploy with instance name 1234.1234 (Intranet_Immediate_Deploy1234.1234).

ENG: 2007-08-22 09:49:47 PDT GMT-07:00 Starting job m211 for deployment Intranet_Immediate_Deploy1234.1234 with parameters: {PAD6=null, DEPLOYSUFFIX=1234.1234, JOBID=m211, LOGLEVEL=VERBOSE, PAD3=null, ENDTIME=null, PAD5=null, MINUTEINV=0, HOURINV=0, SYNCH=false, REPAIR=false, VERIFY=false, EXTERNALTASKID=null, YEARINV=0, REPEAT=false, WEEKDAY=null, PAD2=null, OWNER=corp\dluther, KEYVALUES=null, DEPLOYNAME=Intranet_Immediate_Deploy, NO_RECUR=NO_RECUR, STARTTIME=Wed Aug 22 09:49:47 PDT 2007, PAD4=null, RECURSET=NO_RECUR, DAYINV=0, PAD1=null, STARTDEPLOY=true, MONTHDAYS=null, DESCRIPTION=, WEEKINV=0}
ENG: 2007-08-22 09:49:47 PDT GMT-07:00 MultiTier Latch is null
CFG: 2007-08-22 09:49:47 PDT GMT-07:00 ***ERROR - "deployment" object is invalid.
ENG: 2007-08-22 09:49:47 PDT GMT-07:00 (invalid configuration element)
Configuration information
name= : : isValid=no : use= : dictionary=
parent =
error vector=Set begin java.util.Vector [
vector size=2
(1) Element begin [Message class: 103
Message key: OdCfgE0022
Message :
Parameters : "deployment"
Details : OdCfgE0022:com.interwoven.config100.TDeploymentConfiguration
] (1) Element end
(2) Element begin [Message class: 103
Message key:
Message : CfgError: Logger was null!!!
Parameters
Details : com.interwoven.config100.TDeploymentConfiguration
] (2) Element end
] Set end java.util.Vector
CFG: 2007-08-22 09:49:47 PDT GMT-07:00 ***ERROR - "deployment" object is invalid.
ENG: 2007-08-22 09:49:47 PDT GMT-07:00 Routed Multi Tier = null
ENG: 2007-08-22 09:49:47 PDT GMT-07:00 DNR End Target = false
ENG: 2007-08-22 09:49:47 PDT GMT-07:00 DNR DeploymentJobInitialSource = false
ENG: 2007-08-22 09:49:47 PDT GMT-07:00 Is this End Node false
CFG: 2007-08-22 09:49:47 PDT GMT-07:00 ***ERROR - "deployment" object is invalid.
ENG: 2007-08-22 09:49:47 PDT GMT-07:00 ***ERROR - Failed to processing config file d:\od-home\conf\Intranet_Immediate_Deploy.xml
ENG: 2007-08-22 09:49:47 PDT GMT-07:00 Completed session queue capacity reached. Removed oldest session.

ENG: 2007-08-22 09:49:47 PDT GMT-07:00 Removing session m211
ENG: 2007-08-22 09:49:47 PDT GMT-07:00 ***ERROR - Failed starting deployment: Intranet_Immediate_Deploy1234.1234
API: 2007-08-22 09:49:47 PDT GMT-07:00 Error encountered while starting deployment Intranet_Immediate_Deploy1234.1234
Error: DEPLOY_CONFIG_FILE., Failed to processing config file d:\od-home\conf\Intranet_Immediate_Deploy.xml

What does the '***ERROR - "deployment" object is invalid.' error mean? That seems to be the root of all the issues.

nipper

The only thing I did not see (when I compared to mine) is this at the end:

[html]

[/html]

Lex

Thank you, Andy! That was it. I mistakenly deleted the entire <deployment> node. D'oh!

Adam Stoller

It's being called using the iwodstart CLT:

my $command = "d:\\od-home\\bin\\iwodstart $cfg -inst " . GetLUID() . " -k myarea=$area,mysite=$site,myfilelist=$filelist,myfarm=$farm -V verbose";

Uhm - I don't believe the above syntax is correct.

Besides changing iwodstart to iwodcmd start (recommended), I don't believe you can group command line parameters in one -k flag like that. I believe the command line should be something like:

...
(my $odhome = $ENV{IWOD60HOME}) =~ tr|\\|/|; # windows only
my $inst = GetLUID();
my $command = join(q{ }
                   , qq($odhome/bin/iwodcmd start $cfg)
                   , qq(-k "myarea=$area")
                   , qq(-k "mysite=$site")
                   , qq(-k "myfilelist=$filelist")
                   , qq(-k "myfarm=$farm")
                   , qq(-inst $inst)
                   , qq(-V verbose));
...

nipper

Uhm - I don't believe the above syntax is correct.

Besides changing iwodstart to iwodcmd start (recommended), I don't believe you can group command line parameters in one -k flag like that. I believe the command line should be something like:

I did not think that was supported, but according to Lex it was working elsewhere, so maybe it works with the iwodstart bat file.

Lex

I did not think that was supported, but according to Lex it was working elsewhere, so maybe it works with the iwodstart bat file.

Actually, I was faking the -k entry before I dumped it to a file to see exactly what it was outputting. It's not doing a comma-separated list, it's actually doing -k key=value -k key=value ... My bad.

I'll make the change to iwodcmd as well. Is the iwodstart going away or just deprecated and not recommended for use any more?

nipper

Actually, I was faking the -k entry before I dumped it to a file to see exactly what it was outputting. It's not doing a comma-separated list, it's actually doing -k key=value -k key=value ... My bad.

I'll make the change to iwodcmd as well. Is the iwodstart going away or just deprecated and not recommended for use any more?

That makes sense.

iwodstart has been not recommended for use for a while. Since it is a script, it should work for a while, unless IWOV really changes how OD is invoked. But there are no guarantees.