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

listener cannot bind...

nipper

Hi

In a test environment, OD 5.6 SP1 (cannot upgrade right now)

Linux on a virtual server (there are multiple IP addresses, OD is assigned to a standalone VS)

I have changed RMI, odrcvr, deploy, etc to virtual IP address

netstat -an shows no conflicts on 20014

[root@ussdiweb92v log]# netstat -an | grep 20014
[root@ussdiweb92v log]#

RMI port is open and does get connected when OD starts.

Still cannot connect:

NG: 2005-10-04 15:01:50 PDT GMT-07:00 Component Version : 5.6.0.1.0 Build 21220 Interwoven 20030618

ENG: 2005-10-04 15:01:50 PDT GMT-07:00 *** I18N initialization done ***

ENG: 2005-10-04 15:01:50 PDT GMT-07:00 *** Event reporting is configurated to be disabled ***

ENG: 2005-10-04 15:01:50 PDT GMT-07:00 *** OpenDeploy Server is NOT a sender ***

ENG: 2005-10-04 15:01:50 PDT GMT-07:00 *** OpenDeploy Server is a receiver ***

ENG: 2005-10-04 15:01:50 PDT GMT-07:00 Listener completed sessions capacity = 50
ENG: 2005-10-04 15:01:50 PDT GMT-07:00 *** Fan-out capability enabled ***

SVR: 2005-10-04 15:01:50 PDT GMT-07:00 Starting OpenDeploy engine component.
ENG: 2005-10-04 15:01:50 PDT GMT-07:00 Getting the local Node = 43.130.138.178

ENG: 2005-10-04 15:01:50 PDT GMT-07:00 Creating session listener on port 20014...

ENG: 2005-10-04 15:01:50 PDT GMT-07:00 Receiver-side handshake timeout = 120 secs

ENG: 2005-10-04 15:01:50 PDT GMT-07:00 ***ERROR - Session Listener failed binding on [43.130.138.178:20014] exiting...

SVR: 2005-10-04 15:01:50 PDT GMT-07:00 ***ERROR - OpenDeploy engine component encountered error.

SVR: 2005-10-04 15:01:50 PDT GMT-07:00 ERROR DETAILS:
Session Listener failed binding on [43.130.138.178:20014]
SVR: 2005-10-04 15:01:50 PDT GMT-07:00 Bring up of OpenDeploy server FAILED.

Clues ?

Find more posts tagged with

Comments

nipper

does anyone know of a way to test if you can bind to a port on Unix ?

You can telnet to a port if something is there, but I want to see what error I get
trying to bind to port 20014. The OD logs do not provide any usefull info.

nipper

Well I got it working, though it is a little different from other posts I have seen.

ENvironment is Linux server running vmware and multiple virtual Linux servers.

OpenDeploy is binding to the physical IP address of the box. Not the vmware instance
assigned ip address. Also when I tried to bind to the hostname it bound to loopback
(127.0.0.1) and was not visible form outside, so I needed to hardcode the IP address.

cgoodall

We're having the same problem with OD 6.1.1 on Windows 2003 on VMware. When you say your hardcoded the IP address, what do you mean specifically?

Thanks
~Chris

nipper

This thread was a year and a half ago, so my memory is vague.

IIRC, OD was trying to bind to the IP address of the host system and not the specific VMWare instance.

cgoodall

I knew it was a shot in the dark, due to the age of the post.

Thanks for your quick reply! We're also working with Interwoven support.

Thanks again,
~Chris

CRB

We're having the same problem with OD 6.1.1 on Windows 2003 on VMware. When you say your hardcoded the IP address, what do you mean specifically?

Thanks
~Chris

in odrcvr.xml
[HTML][/HTML]

cgoodall

Thanks Chris.

We're still getting the same error, except OD now indicates that it can't bind the port on the IP and not the hostname. So it looks like it did notice the change.

The ball is in Interwoven Support's hands again. I'll post if they come up with something. We've been working the probem since Friday and have asked to have the issue escalated.

Sincerely,
~Chris

Amlan

Hi,
i too am experiencing the same problem using Solaris 10. Any updates from IW Support regarding this.

Amlan

tanguyr

Same problem here on a new install of receiver 6.2.0 on Solaris 10. The machine i am installing on is a zone.

/t

tanguyr

Same problem here on a new install of receiver 6.2.0 on Solaris 10. The machine i am installing on is a zone.

/t

Sorted - the problem was on our end, the ip address in /etc/hosts was not correct (did not match the ip address returned by ifconfig -a)

/t