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 Bug??

yanSi

Our base is v5.6.0.1.0 build 21220
Our receiver is v6.0.1.0.0 build 41860

I think I found a bug in the way OD processes the deployment config files. In the OD admin guide, it says that localNode is the IP address of your OD base. Most of the time it will be 127.0.0.1 since the deployment configs will reside on your OD base. When you try create a new deployment config using the admin UI, the localNode value defaults to the IP address of your OD base (it won't be 127.0.0.1 but it will be equivalent).

I find that if I go with the default value, the deployment will fail. But if I enter the IP of my OD receiver, the deployment completes.

Does anyone else think that this is a bug or am I misinterpreting the manual or maybe it has something to do with the different base/receiver versions?

Find more posts tagged with

Comments

John742

Please post your deployment xml config file and if possible odnodes and odbase configs. Solaris or Windows?

J Dagenhardt

Edited by John742 on 03/10/05 06:17 PM (server time).

yanSi

Consider these 3 statements:
1. According to page 315 of the OD admin guide, the localNode value should be the IP address of the base.
2. When you compose a deployment configuration, the default value is the IP address of the base.
3. Deployment configuration files reside on the base so you would think that an element called localNode would be the IP address of the base.

If you use the IP address of the base, the deployment will fail. If you use the IP address of the receiver, the deployment completes successfully.

DeloyToYan.xml is attached

Edited by yanSi on 03/11/05 07:44 AM (server time).

yanSi

odnodes is attached, odbase is listed below. Oh yeah... and OD is running on Windows
-------------------------------------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<deployServerConfiguration>







<localNode host="10.20.200.27"/>

<listenerProperties name="InterwovenOpenDeploy"
bindPort="20014"/>

<transportProperties name="od"
bufferSize="8000"
/>

<schedulerProperties jdbcDriverClass="org.hsql.jdbcDriver"
dbUrl="jdbc:HypersonicSQL Smiley Very Happy

:\iw-home\OpenDeploy\OpenDeployNG\db\schedDB"
dbUser="sa"
dbPassword=""
/>

<dnrProperties allowDnrExecution="yes"
infoStreamFormat="manifest" />

<allowedHosts>
<node host="10.20.200.27">
<allowedDirectories>
<path name="Y:\default\main\Bases\Trenton\STAGING"/>
</allowedDirectories>
</node>

<node host="10.22.50.100">
<allowedDirectories>
<path name="C:\trenton"/>
</allowedDirectories>
</node>

</allowedHosts>

<logRules maxBytes="32Mb"
directory="D:\iw-home\OpenDeploy\OpenDeployNG\log"
level ="verbose"
/>

<eventReporting enabled="yes" cfgPath="D:\iw-home\OpenDeploy\OpenDeployNG\etc\eventReportingConfig.xml" />

</deployServerConfiguration>

Edited by yanSi on 03/11/05 07:50 AM (server time).

Migrateduser

Check that the allowed host value in the receivers odrcvr.xml file matches the localnode value in the deployment config.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

yanSi

Yes the localNode in the deployment config does match the IP address of the receiver (see attachment).

What I was trying to get at was that the admin guide led me to believe that the localNode value should be the IP address of the base. Also the default value for a new deployment config and the element name (LOCALNode) also led me to believe that the value should be the IP of the base.

Migrateduser

> What I was trying to get at was that the admin guide led me to believe that the localNode
> value should be the IP address of the base.

That is correct. But in order for the sender to be allowed to connect to the receiver, that value must be listed as an allowed host in the receiver's config file.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

yanSi

The odrcvr file does list the base as an allowed host (see 6th post)

RECEIVER:
node host="10.22.50.100"

BASE:
node host="10.20.200.27"

--------------------------------------------------------------------------------------------

But in the deployment configuration (which resides on the base), the local Node value uses

localNode host="10.22.50.100"

which is the IP of the receiver (see 3rd post).

-------------------------------------------------------------------------------------------

The deployment completes without error if the localNode is set to the receiver IP, but will
fail if localNode is set to the IP of the base.

Therefore, because setting the localNode value to the IP of the base fails, I think it's a bug
either in OD or in the OD documentation or I'm going crazy.

Migrateduser

The localNode value in the deployment config is used by the Receiver to string-match against the list of allowed hosts. The actual value doesn't matter, so long as it matches a value in the Receiver's allowed hosts list.

In your case, I think you've set the value to be 10.22.50.100, but this could have been any string value.

Fyi, note that if the Receiver can't match the localNode value from the deployment config, it then attempts to match the IP info from the connection request.

If you want to use only the latter method of allowed host checking, then you would configure the "strict partner checking" attribute.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com