Open Deply failing at the base server

Hi,

I am working on Teamsite 6.5 SP2 (Syetem's OS is win2k3 SP1). I have OD version 6.0.2.

Whenever I try to deploy any file, the deployment fails. There are no logs on the reciever end. On the base server, the logs give the following error:

***ERROR - Job ID=m1Deployment=_adidasGroup_en_investor
Base: Exceeded all 3 retries to get a connection with the target OpenDeploy host. Failed creating socket.

Both the base and the reciever are on the different servers, but there is no Firewall between them.

All base and rcvr files have correct entries.

Problem is that I am note able to telnet 20014.

Can anyone please help. Its very very urgent.

Regds

Find more posts tagged with

Comments

ReggieRWalker

Is it possible that your target server has 2 nics? If not, can you post the deployment config file and the odrcvr.xml file for your target?

ISCBorisB

If it is so very urgent, what have you tried yourself? What possible causes for failure to establish base-receiver connection
you've already eliminated?

The problem is very common, simple DevNet search returned 11(eleven) threads with the exact match. Have you analysed any of them?
If not - you are wasting yours and our time. It is your environment, we can not test it. The best anybody can do is start asking you to
check "this" and check "that" - and all these questions were already asked in numerous threads.

Nitin_B

Listen, I am not at all wating anyone's time. I have already analysed each and every thread and after not finding the solution have I opened this thead.

Hi Reggie,

Ya the target server has 2 Nics. Can you please let me know what role does that have to do, I mean the impact. I already read in many of the threads about this.

We have 2 Nics but only one is registered in internal DNS against the host name.

Another thing which we noticed is that we are able to telnet the target server, using the host name(but not using the ip) locally.

Regds

ReggieRWalker

Listen, I am not at all wating anyone's time. I have already analysed each and every thread and after not finding the solution have I opened this thead.

Hi Reggie,

Ya the target server has 2 Nics. Can you please let me know what role does that have to do, I mean the impact. I already read in many of the threads about this.

When you install OD on a machine with multiple NICs, the service will bind to one of those NICs.

We have 2 Nics but only one is registered in internal DNS against the host name.

Another thing which we noticed is that we are able to telnet the target server, using the host name(but not using the ip) locally.

Regds

You should be able to telnet to the registered IP. Can you list your config files? As Boris mentioned, we can't help solve what we can't see.

Nitin_B

Thanks.

Can you please let me know which config files are required. Please name the files and I'll send over to you.

Regds

Nitin_B

Hi,

Thanks for your direction. I checked and found that it is getting binded to the wrong IP actually (I saw using the netstat -an command). Can you please let me know how can I switch this binding to the correct IP.

Regds

ReggieRWalker

Hi,

Thanks for your direction. I checked and found that it is getting binded to the wrong IP actually (I saw using the netstat -an command). Can you please let me know how can I switch this binding to the correct IP.

Regds

The fastest way to do it is to change the "host" attribute in your odnodes.xml file (on the base and target) to that binded IP instead of using the hostname. This will allow you to still use the hostname in your config files.

Adam Stoller

The fastest way to do it is to change the "host" attribute in your odnodes.xml file (on the base and target) to that binded IP instead of using the hostname. This will allow you to still use the hostname in your config files.

The odnodes.xml file is not used on the Receiver except possibly with respect to reverse deployments (I'm not sure that it's even used then).

We have 2 Nics but only one is registered in internal DNS against the host name.
[...]
I checked and found that it is getting binded to the wrong IP actually (I saw using the netstat -an command). Can you please let me know how can I switch this binding to the correct IP.

OpenDeploy tends to bind to the first network it finds when the server boots - or at least the first one that corresponds to the hostname or IP address in the localNode setting of the server's configuration file.

In this case, it sounds like the odrcvr.xml is set with a hostname for the localNode - and that despite the DNS only showing the one IP address - the local hosts file on the server is binding that name to the other one [first]. In a case like this you might be able to change the order that the host:IP address bindings are referenced in the hosts file -or- set the localNode of the odrcvr.xml to the actual IP address against which you want it to bind (probably easier without potentially messing something else up that depends on the current binding order).

Once you make the change - you need to restart things. If you changed the hosts file I'd recommend rebooting the server. If you change the localNode setting in the odrcvr.xml file, I'd suggest stopping and re-starting the OpenDeploy receiver process.

Once you do that - see if you can telnet from the base server to the receiver again - if you can, you should be fine. If not, please explain in detail what you did (every step)

Nitin_B

Hi,

Thanks a lot. I changed the hostname to ip and it did work.

Regds