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; } } }

routed Deployment

naumank

Hi,

I am having a problem to run routed deployment this time, however I ran routed deployment before and it works fine but today I had a weird issue when I am running a routed deployment from server 1 through server 2 to server 3, it is getting failed and keep getting following error message in the server1_odbase.log file

2012-08-27 17:45:30.587 GMT-0400 serverLog [RMI TCP Connection(9)-172.XX.YY.ZZ] - ENG 08002: ***ERROR - Route Computation for routeDefinition =route1 failed
2012-08-27 17:44:02.608 GMT-0400 serverLog [RMI TCP Connection(6)-172.XX.YY.ZZ] - ENG: Empty route. Unable to get route for routeDefinition = route1

or if i make the route1 definition changed in the odnodes.xml file then I got this

2012-08-27 17:38:24.737 GMT-0400 serverLog [RMI TCP Connection(8)-172.XX.YY.ZZ] - ENG: Router Adapter Class Name = com.interwoven.od.adapter.route.firstmatch.IWFirstMatchRouter
2012-08-27 17:38:24.749 GMT-0400 serverLog [RMI TCP Connection(8)-172.XX.YY.ZZ] - ENG 08012: ***ERROR - toNode (server2 )regular expression can't match to the origin node (server1 in the route Definition = route1
2012-08-27 17:38:24.749 GMT-0400 serverLog [RMI TCP Connection(8)-172.XX.YY.ZZ] - ENG: Empty route. Unable to get route for routeDefinition = route1

1) Server 1( od base server) has a direct connectivity with Server 2(od base server).
2) Server 2(Od base server) has a direct connectivity with Server 3(od reciever)
3) Server 1 and Server 3 do not have direct connectivity.

This is my routeDefinition in odnodes.xml in Server1
[html]

[/html]
OD version 7.3 in Linux,
I would really appreciate your help.

Find more posts tagged with

Comments

Adam Stoller

We'd need to see a lot more of the configuration - like where you define the nodes for "Server1", "Server2", and "Server3" (in odnodes.xml) and the actual deployment configuration file you're using to run the routed deployment (all either properly formatted for the forum, or attached as files so you don't have to muck with the formatting)

artor

Thanks and here are the configuration

odnodes.xml file in Server1 and I also have the entry for Server 3 in Server 2 odnodes.xml file.
[html]

host="172.XX.YY.ZZ"
port="20014"
/>

host="172.XX.YY.ZA"
port="20014"
targetArea="/tmp/dirA"
/>

host="172.XX.YY.ZZ"
port="20014"
/>
[/html]

and Here is the deployment file

[html]

[/html]

Adam Stoller

Thanks and here are the configuration

odnodes.xml file in Server1 and I also have the entry for Server 3 in Server 2 odnodes.xml file.[html]

targetArea="/tmp/dirA" />
[/html]

Okay - so you did define the targetArea for node "Server2" - good; I'm not sure if you need one defined for "Server3" though, I think you might:

<node name="Server3" host="172.XX.YY.ZZ" port="20014"
targetArea="{ENODETARGDIR}" />

Although I wrote the original Perl-based implementation of routed deployments (about 12 years ago), I've only played with the productized version of it once since, and I don't recall all the ins-and-outs of it - but the config you posted looks like it conforms to the instructions in the manual.

I'd suggest trying the change above and see if that fixes things, or at least seems to move things forward to a different error...

artor

I would change that but I used the same file in my other servers such as server A through Server B and Server C and it works.
the only difference in this scenario is as compared to the one which causing a problem is

Server A has a connectivity with Server B
Server B has a connectivity with Server C
Server A has a connectivity with Server C as well

But I will try to make changes as you suggest and see if it works or not

artor

Now I able to run with some error which are as

[html]

2012-08-28 16:32:49.735 GMT-0400 serverLog [ReThread-0] - ENG: Rcvr send verson string, rc=1
2012-08-28 16:32:49.735 GMT-0400 serverLog [ReThread-0] - ENG: Rcvr: sender-version=7.3.1.0.0 receiver-version=7.2.0.0.0
2012-08-28 16:32:49.751 GMT-0400 serverLog [ReThread-0] - ENG: Receiver is version slave
2012-08-28 16:32:49.751 GMT-0400 serverLog [ReThread-0] - ENG: Printing the Route Table
2012-08-28 16:32:49.751 GMT-0400 serverLog [ReThread-0] - ENG: From Node = Server1
2012-08-28 16:32:49.752 GMT-0400 serverLog [ReThread-0] - ENG: To Node = Server2
2012-08-28 16:32:49.752 GMT-0400 serverLog [ReThread-0] - ENG: From Node = acaertidcp-cms03
2012-08-28 16:32:49.752 GMT-0400 serverLog [ReThread-0] - ENG: To Node = Server3
2012-08-28 16:32:49.752 GMT-0400 serverLog [ReThread-0] - ENG: Receiver: Printing Successor Node for = acaertidcp-cms03
2012-08-28 16:32:49.752 GMT-0400 serverLog [ReThread-0] - ENG: Receiver: Successor Node = Server3 target Area is
2012-08-28 16:32:49.752 GMT-0400 serverLog [ReThread-0] - ENG: uat-app01 is in EndNode Vector
2012-08-28 16:32:49.752 GMT-0400 serverLog [ReThread-0] - ENG: Failed writing to the config file
2012-08-28 16:32:49.752 GMT-0400 serverLog [ReThread-0] - ENG 08006: Generation of config file for next Tier failed
2012-08-28 16:32:49.783 GMT-0400 serverLog [ReThread-0] - ENG: Rcvr sent nack, rc=1
2012-08-28 16:36:15.949 GMT-0400 serverLog [Thread-8] - CLT: Allowing execution from localhost.localdomain/127.0.0.1

[/html]

Adam Stoller

Now I able to run with some error which are as ...

THis looks more like a permissions issue.

Is OD running as root (unix) or System (windows) - or as some specific user ("non-root")?

naumank

It was running as a root. I checked this error in the od reference manual and it says its because of some setting in odnodes.xml file or deployment config file but there is no detail mentioned and i tried with several setting but unable to run.

Adam Stoller

It was running as a root. I checked this error in the od reference manual and it says its because of some setting in odnodes.xml file or deployment config file but there is no detail mentioned and i tried with several setting but unable to run.

Check the Support site and/or talk to Support - there was a problem in the initial release of 7.3.1 OpenDeploy where it didn't properly handle down-rev deployments - which you are apparently doing (just noticed it now)

That's probably the cause of the "nack - which if resolved, might solve the entire problem.

artor

Thanks for your help, I downgraded to 7.2.1 but no luck and now I opened the case and let see whether i can resolve or not.