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

Must a Reverse Source be an OpenDeploy receiver?

lynnmaureen

I'm having difficulty getting a reverse deployment to work.
Must a Reverse Source in a reverse deployment have only the Receiver version of OpenDeploy installed? Eg. The documentation mentions that reverse deployments are useful for deploying content from a Receiver server, but I'm wondering if this type of deployment will still work if both servers have Base installations.
I'm using version 5.6.0 on all servers.

Edited by lynnmaureen on 05/31/04 08:50 AM (server time).

Find more posts tagged with

Comments

bboyle

we have reverse deployments working between two base servers (OD5.6) so that's not the problem.

I do remember it being a bit tricky to get it working, bit confusing with all the reversing. Things like the server starting the deployment - source in a regular deploy - is the reverseTarget, and treated like a target must have the appropriate allowedHosts/allowedDirectories to accept the deployment. We were also using keyfiles specified and had to put them on both servers (even though we didn't want to use them in the reverse deployments - long story).

Post up your config, and maybe the log, someone will work it out Smiley Happy

lynnmaureen

Okay, so that rules out my first question.
The deployment fails instantly, and I get the following error in every log for each of the deployment legs:

ENG: 2004-06-01 10:42:22 EDT GMT-04:00 Thread-845 Sender is version master
ENG: 2004-06-01 10:42:22 EDT GMT-04:00 Thread-845 Sender compatible with receiver: version same
ENG: 2004-06-01 10:42:22 EDT GMT-04:00 Thread-845 ***ERROR - Receiver has rejected sender -- nack:5.6.0.0.0
ENG: 2004-06-01 10:42:22 EDT GMT-04:00 Thread-845 fRevRes=-1
ENG: 2004-0006-01 10:42:22 EDT GMT-04:00 Thread-845 exiting setup

For testing, I've stripped the config down to 1 replication farm and 1 deployment definition, but I'm still getting this error.

I've made sure that the host value in the Reverse Target's odbase.xml and odnodes.xml configs match... I was sure that would solve the problem, but it hasn't.

Any ideas?

Adam Stoller

Just checking to make sure we're on the same page here:
- Base Server (reverseTarget) is 10.54.0.101
- Receiver (rerverseSource) is NCMSDA02
-- The Receiver is also a TeamSite server
-- Both servers are Windows based and running OD 5.6.0
-- (note: permissionRules settings only show Unix 'directory' and 'file' settings not Windows settings)

- The Base Server's odbase.xml lists NCMSDA02 as an allowedHost and E:\sites\hrdc-drhc\docroot\docs\en\cs (or some root-part of that path) within the allowedDirectories section for that host.
-- Is E:\ a local disk partition or a mapped drive?

- The Receiver's odrcvr.xml (or odbase.xml if they are both BaseServers) lists 10.54.0.101 as an allowedHost (at this point it shouldn't matter what's listed for allowedDirectories as long as something is listed there).

- There is no firewall doing NAT between the two servers

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

lynnmaureen

- Base Server (reverseTarget) is 10.54.0.101
yes
- Receiver (rerverseSource) is NCMSDA02
yes

-- The Receiver is also a TeamSite server
Both servers have a Base installation, and yes, the reverseSource is a TeamSite server.

-- Both servers are Windows based and running OD 5.6.0
yes

-- (note: permissionRules settings only show Unix 'directory' and 'file' settings not Windows settings)
hmm.. well, I can remove/change that for testing purposes for this particular deployment, but all of our deployments use those same permissionRules, and all of our OpenDeploy servers are running Windows...

- The Base Server's odbase.xml lists NCMSDA02 as an allowedHost and E:\sites\hrdc-drhc\docroot\docs\en\cs (or some root-part of that path) within the allowedDirectories section for that host.
yes, as follows:
10.54.0.101's odbase.xml:


<node host="10.54.0.102">
    <allowedDirectories>
        <path name="E:\Inetpub" /> 
        <path name="E:\sites\hrdc-drhc\docroot" /> 
        <path name="E:\sites\hrdc-drhc\cgi-bin" /> 
    </allowedDirectories>
</node>
<node host="NCMSDA02">
    <allowedDirectories>
        <path name="E:\Inetpub" /> 
        <path name="E:\sites\hrdc-drhc\docroot" /> 
        <path name="E:\sites\hrdc-drhc\cgi-bin" /> 
    </allowedDirectories>
</node>

The two nodes shown are actually the same server. I listed it by name and IP just to be sure...
10.54.0.101's odnodes.xml:

<node name="NCMSDA01" host="10.54.0.101" port="20014" />

-- Is E:\ a local disk partition or a mapped drive?
local

- The Receiver's odrcvr.xml (or odbase.xml if they are both BaseServers) lists 10.54.0.101 as an allowedHost (at this point it shouldn't matter what's listed for allowedDirectories as long as something is listed there).
Yes

- There is no firewall doing NAT between the two servers
No, there is not.

Adam Stoller

One question I realize I accidently left off the last set ... did you remember to stop/start the servers (both sides) after making changes to the config files?

From what you've responded with so far - it looks like you should be able to connect (assuming those IP addresses and/or non-qualified domain names work as-is)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

lynnmaureen

No, I forgot! Hopefully that will solve the problem then.