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

telnet MyLocalHost 20014

MKNIGHT

Newbie to OD,
I'm trying to have the test.xml(Default file that comes with the installation) working and I'm getting an error.
Been reading the forum for the last day and got a few lead but with no success.

I know that the server is up: iwodcmd serverstatus: OpenDeploy is Alive.
I'm able to telnet to 9173 and 8081 with : telnet interwoven port.
interwoven is my server name.

I believe my problem is with the port 20014, even if it's up, I did netstat -a and 20014 is up and running, but when I'm trying:
1.telnet interwoven 20014 --> error connect failed
2.telnet MyLocalHost 20014 -->Error connect failed(got MyLocalHost from odnodes.xml)
3.telnet 10.1.200.2 20014 -->Error connect failed

But When I tried
4.telnet 127.0.0.1 20014 it works, great but I want my test.xml to work
what do I need to fix for that

Note: command issued: iwodcmd start test, I've rename and attach the file that you may need...

where should I look...

Michel
--------
Windows 2000
OD 6.0.1
Base server
All on the same machine

Find more posts tagged with

Comments

Dwayne

You said that netstat -a showed that it was listening, but on which IPs? It could be that it's only binding to the 127.0.0.1 IP address, and not the 10.1.200.2 IP. I'd run 'netstat -an' to see IPs without name resolution getting in the way.

Your odbase.xml would probably also be helpful for diagnosing the problem.

Adam Stoller

You said that netstat -a showed that it was listening, but on which IPs? It could be that it's only binding to the 127.0.0.1 IP address, and not the 10.1.200.2 IP. I'd run 'netstat -an' to see IPs without name resolution getting in the way.

Your odbase.xml would probably also be helpful for diagnosing the problem.

Specifically - the way the localNode is defined in the odbase.xml file will help determine how OD is trying to bind the deployment port (20014 by default) to an IP address.

You may need to go a step further to determine how the server itself is binding names to the IPs - but the odbase.xml would be the first place I'd look (and remember to stop/start the OD service(s) after making changes to the odbase.xml in order for those changes to take effect)

MKNIGHT

You're right I've tried netstat -an and it's not set for the IP, only for 127.0.0.1.

I will go and read about odbase.xml, i've attached it. If there anything you can pin point to, that would be appreciated.

thanks

Dwayne

I suggest you change the line

<localNode host="INTERWOVEN"/>

to be instead

<localNode host="10.1.200.2"/>

(assuming that's the IP you want to bind to). The restart OD

MKNIGHT

Great it worked,

Thanks for the fast replied, I can now move ahead...

Michel

MKNIGHT

Just out of curiousity would it be an easy process if I would want to use the
hostname instead of an IP?

Is it because it's on the same machine that I need to use the IP?

MKNIGHT

Never mind my last question I've typed the hostname in and it worked.

Note: That I re-started my server properly this time... ;-)