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

Html preview not working in TS 7.3.1 | linux

retesh

Hi,

We have a fresh installation of TS 7.3.1 on Red Hat Linux 5.3.

We have generated html pages from DCT + xslt (PT). But html output page doesn't open in IE. It gives connection fail error (err msg below).

iwproxy was unable to open a connection to: server_name:81
Reason: Transport endpoint is not connected.

I've checked iw.cfg, customer_webserver_port=81.

Please help guys.

Thanks,
Retesh

Find more posts tagged with

Comments

ISCBorisB

Hi,

We have a fresh installation of TS 7.3.1 on Red Hat Linux 5.3.

We have generated html pages from DCT + xslt (PT). But html output page doesn't open in IE. It gives connection fail error (err msg below).

iwproxy was unable to open a connection to: server_name:81
Reason: Transport endpoint is not connected.

I've checked iw.cfg, customer_webserver_port=81.

Please help guys.

Thanks,
Retesh

[post=176641]Virtualization Web Server[/post]

nipper

Check that your webserver is set to autostart. Apache typically does not start on boot on Linux

retesh

Thanks for responge Guys Smiley Happy

Issuing netstat -a | grep 81 on the server returns below lines:
----------------------
tcp 1 0 geamstlxts02d.geam.co:57818 geamstlxts02d.geam.cor:6689 CLOS
E_WAIT
unix 3 [ ] STREAM CONNECTED 18168 /var/run/dbus/system_bu
s_socket
unix 3 [ ] STREAM CONNECTED 18167
unix 2 [ ] DGRAM 11481
-------------------------
Does this means port 81 is not listening? Should my next step be checking if apache is running or not? And, set it to autostart.

Once content webserver (eg. Apache) is up and running, then does it always listen on port 81?

Many Thanks,
Retesh

nipper

Yea, apache is not listing. You can use apachectl to start it. Check google for instructions to have it start on boot.

During the install process of TeamSite, it should have modified httpd.conf to move apache to port 80, assuming the proper information was provided to the installer.

Adam Stoller

Yea, apache is not listing. You can use apachectl to start it. Check google for instructions to have it start on boot.

During the install process of TeamSite, it should have modified httpd.conf to move apache to port 80, assuming the proper information was provided to the installer.

I believe you meant to move apache to port 81 - since iwwebd (which is also apache, but a "private" version for TeamSite use only) should be running on port 80.

nipper

I believe you meant to move apache to port 81 - since iwwebd (which is also apache, but a "private" version for TeamSite use only) should be running on port 80.

Yes it should be port 81. Thanks

retesh

Thanks Guys. The preview problem got resolved by starting apache for linux. The conf file already had entry to listen on port 81. I think this gets written during installation.

But, I am facing another issue at the moment. We did iwreset after making some config changes post preview issue fix. Now, iwwebd is not starting through iwreset. When i try to start it using clt from IWWEBD_HOME then it returns with an error cannot start web daemon due to a library file not found.
When I preview html, it returns with a screen "IW Web Daemon was unable to coonect to IW Proxy.... Contact Interwoven Admin..."

Would I need to reboot the linux box to fix this. I somehow dont feel if any conf file entries are required. Please suggest

Adam Stoller

Thanks Guys. The preview problem got resolved by starting apache for linux. The conf file already had entry to listen on port 81. I think this gets written during installation.

But, I am facing another issue at the moment. We did iwreset after making some config changes post preview issue fix. Now, iwwebd is not starting through iwreset. When i try to start it using clt from IWWEBD_HOME then it returns with an error cannot start web daemon due to a library file not found.
When I preview html, it returns with a screen "IW Web Daemon was unable to coonect to IW Proxy.... Contact Interwoven Admin..."

Would I need to reboot the linux box to fix this. I somehow dont feel if any conf file entries are required. Please suggest

Is it iwwebd that failed to start, or iwproxy?
If there's a library missing, I'd think that this problem would have pre-existed your issue with the "customer web server" apache - but it didn't sound like you had this problem before. Are you attempting to start iwwebd as root?
A reboot should not be necessary, but on the other hand, if the processes do not start correctly when you do reboot the server - then you definitely have a problem that needs to be addressed.

retesh

Is it iwwebd that failed to start, or iwproxy?
If there's a library missing, I'd think that this problem would have pre-existed your issue with the "customer web server" apache - but it didn't sound like you had this problem before. Are you attempting to start iwwebd as root?
A reboot should not be necessary, but on the other hand, if the processes do not start correctly when you do reboot the server - then you definitely have a problem that needs to be addressed.

Hi Ghoti,

When we do iwreset then IWWEBD fails to start. When i try to start IWWEBD service seperately then too it doesn't.

No, I didn't had this problem before.

Thanks,
Retesh

retesh

I am writing down the results of two commands lines, which is confusing me. Result of one suggest iwwebd is down and the result of other suggest its up and running. Clicking on html pages still comes up error screen "IW Web Daemon was unable to coonect to IW Proxy.... Contact Interwoven Admin..."

1. netstat -A inet -lnp | grep iwwebd

tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 10210/iwwebd
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 10210/iwwebd
------------------------------------

2. ./iw.webd start

/teamsite/Interwoven/TeamSite/iw-webd/bin/iwwebd: error while loading shared libraries: libaprutil-0.so.0: cannot open shared object file: No such file or directory
./iw.webd start: iwwebd could not be started
------------------------------------

Any suggestions..

Adam Stoller

Try explicitly stopping iwwebd first - then check with your netstat to make sure it's not there - and then try starting it again.

It's possible that it somehow got into a strange state in which it's not completely down nor completely up.

For the library thing - try running ldd on

IWHOME/iw-webd/bin/iwwebd

and post the results.

nipper

Also run this command:

locate server.log

You shoud get a result like this (among many others):

/apps/Interwoven/ApplicationContainer/server/default/log/server.log

check the last few hundred lines of that file and you will probably see some errors, which may be helpful

retesh

Try explicitly stopping iwwebd first - then check with your netstat to make sure it's not there - and then try starting it again.

It's possible that it somehow got into a strange state in which it's not completely down nor completely up.

For the library thing - try running ldd on
IWHOME/iw-webd/bin/iwwebd
and post the results.

Stopping iwwebd doesn't work as the server is already stopped. How should i run Idd. iwwebd is a file, not a directory.

Thanks.

nipper

Stopping iwwebd doesn't work as the server is already stopped. How should i run Idd. iwwebd is a file, not a directory.

Thanks.

ldd needs a file as a parameter:

ldd
ldd: missing file arguments
Try `ldd --help' for more information.

ldd /apps/Interwoven/TeamSite/iw-perl/bin/iwperl
linux-gate.so.1 => (0xffffe000)
libnsl.so.1 => /lib/libnsl.so.1 (0x00a5f000)
libdl.so.2 => /lib/libdl.so.2 (0x002ad000)
libm.so.6 => /lib/libm.so.6 (0x002b4000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x002f3000)
libutil.so.1 => /lib/libutil.so.1 (0xf7f68000)
libc.so.6 => /lib/libc.so.6 (0x00138000)
/lib/ld-linux.so.2 (0x00119000)

retesh

Thanks all for your valuable inputs on this thread. The problem is resolved.
The root cause of the issue was my team member (while trying to configure LSCS components) updated rewrite_conf file. There was a minor syntactical error in this file due to which WEB Daemon wasn't starting. Fixing the error made web daemon work.

I am closing this thread.