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

Issue in Previewing the files?

tech17

Hello All,

We have recently installed the TS server (7.2) on Linux.
We are facing an issue while previewing the files on server.

Earlier when we were trying to preview any file, we were getting the below mentioned error:

"Connection Failed
iwproxy was unable to open a connection to: hostname
Reason: Transport endpoint is not connected"

Then we have changed the port number in httpd.conf.
Hence, the entry in iw.cfg is customer_webserver_port=81
and httpd.conf is Listen 81

But, now when we are trying to preview any file we are getting "HTTP 404 not found error".

We have also seen access.log, but nothing much is available.

In iw.cfg, I have the entry
customer_webserver_host=TS_host_name

I had tried using localhost, IP Addess in above config but got the same error.

I am able to access http://TS_IP:81 and getting the Apache page, however when I have tried to access below links they are not accessible:

http://TS_hostname:81/
http://TS_IP:81/iw-mount/default...test.txt
http://TS_IP:81/iw-mount/

Thanks.

Find more posts tagged with

Comments

Rick Poulin

Which httpd.conf did you change? There are two!

The iwwebd process (TeamSite's Apache) should be listening on port 80.
You then need a _separate_ httpd process running on 81.

In a default install, iwwebd will be correctly configured and your previous Apache httpd.conf will have its Listen :80 directive commented out. You just need to add a Listen :81 there and start that Apache instance. There is no need to change ports in iw.cfg and iw-webd/iwwebd.conf.

tech17

Which httpd.conf did you change? There are two!

The iwwebd process (TeamSite's Apache) should be listening on port 80.
You then need a _separate_ httpd process running on 81.

In a default install, iwwebd will be correctly configured and your previous Apache httpd.conf will have its Listen :80 directive commented out. You just need to add a Listen :81 there and start that Apache instance. There is no need to change ports in iw.cfg and iw-webd/iwwebd.conf.

Thanks for your reply,

I have changed the httpd.conf file which is present under /etc/httpd/conf/httpd.conf and I have changed the Listen 80 to Listen 81.

I think the other file you are talking about is “/usr/iw-home/TeamSite/iw-webd/conf/httpd-std.conf”, I have not changed anything in this and it is still Listening to 80.

Could you please elaborate more on the changes you want me to do and where?

Rick Poulin

I have changed the httpd.conf file which is present under /etc/httpd/conf/httpd.conf and I have changed the Listen 80 to Listen 81.

This is the only change you need.

Perhaps I misunderstood your original post. If you can hit both port 80 and 81 and get a response from Apache (even if it's a 404), but you can't access specific paths on port 81, then you may have to change your Listen directives to use your server's IP address specifically. There are a number of threads around from people who have had the same problem. That should solve the problem of not being able to hit the server by hostname.

As for the /iw-mount/ path, check the httpd.conf file for a virtual host mapping with the same name. It should point it to /iwmnt. If you've changed that path, (via /etc/defaultiwmount or iw.cfg) then you need to update httpd.conf to match.

tech17

This is the only change you need.

Perhaps I misunderstood your original post. If you can hit both port 80 and 81 and get a response from Apache (even if it's a 404), but you can't access specific paths on port 81, then you may have to change your Listen directives to use your server's IP address specifically. There are a number of threads around from people who have had the same problem. That should solve the problem of not being able to hit the server by hostname.

Yes, I think you misunderstood my problem. The scenarios which I have mentioned in my original post are the steps which many users had recommended to perform in various other posts.

So I have just mentioned the o/p of each step so that one can get some pointer that what can be the issue.

My basic issue is that I am not able to preview my file not even a simple .txt or .html file present in Workarea.

As for the /iw-mount/ path, check the httpd.conf file for a virtual host mapping with the same name. It should point it to /iwmnt. If you've changed that path, (via /etc/defaultiwmount or iw.cfg) then you need to update httpd.conf to match.

Regarding this point you mean Configuring iw-mount for Apache?, if yes then I have already done the entry in http.conf. Below is the code snippet which I have appended in the http.conf which is present under /etc/httpd/conf/httpd.conf:

<Directory "/.iwmnt">
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
</Directory>
Alias /iw-mount/ /.iwmnt/

I am not sure whether I needed to do any customization in above code as the location of my iwmnt is in root(/iwmnt).

nipper

try

ping hostname

from the ts-server

tech17

try

ping hostname

from the ts-server

I have pinged the hostname and it is getting connected.
Apart from this I have also tried the telnet using port 80 and 81 both and it is getting connected.

tech17

I have managed to get rid of 404 file not found error, I simply made the changes in httpd.conf file where I had configured the /iw-mount path for Apache.
I have just removed the dot(.) like /.iwmnt and changed it to /iwmnt and it worked for me. But now I am facing another issue issues

When I am trying to preview any text file I am able to view it but for any .html and .jsp file I am getting blank page. However, when I have copied the same html file in /var/www/html/. And try to access directly like http://TS_IP:81/test.html, the file is getting rendered fine.

nvprasadbabu

Hi,

How did you configured in apache httpd.conf file for /iw-mount and /iwmnt? Please share those entries.

Rick Poulin

I have just removed the dot(.) like /.iwmnt and changed it to /iwmnt and it worked for me.

Note that /iwmnt is the optimized, cache view of the content store whereas /.iwmnt is the uncached version. Under normal circumstances, accessing /.iwmnt shouldn't be a problem unless your server can't perform fast enough or if the permissions there don't allow read access to httpd. I'd treat that as suspicious and investigate further.

When I am trying to preview any text file I am able to view it but for any .html and .jsp file I am getting blank page.

Anything of note in your Apache logs?

tech17

Anything in your Apache logs?

Could you please elaborate more, which logs are you talking about? As mentioned earlier, I am able to view the same html file from Apache directly, I am facing issue only while accessing through preview in interwoven. So do you want me to check any iw specific log file? as I didn't get much in access.log.

Thanks.

Parameters_report.rptdesign

Rick Poulin

When the output of a valid resource gives you a blank page, that means that Apache found the resource but was unable to put it through an output stream. As such, I'd expect something to show up in your error.log, which sits beside access.log.

tech17

Hi,

How did you configured in apache httpd.conf file for /iw-mount and /iwmnt? Please share those entries.

Hi Prasad,

I have already shared my entries in above post which you can configure in httpd.conf, the only change I made in those entries is that I have removed dot(.) i.e. instead of /.iwmnt i have kept /iwmnt.

Hope it helps.

tech17

When the output of a valid resource gives you a blank page, that means that Apache found the resource but was unable to put it through an output stream. As such, I'd expect something to show up in your error.log, which sits beside access.log.

Hi Rick,

I have checked the error.log and other logs as well but I am not getting any error while accessing the pages.
Also, I have noticed one thing that when I access the .txt file, the URL is changing from http://xx.****.x.****/iw-cc/command/iw.group.preview_file?vpath=//server-name/vse/main/profile/WORKAREA/work/content/test.txt to http://xx.****.x.****/iw/cci/meta/injection/iw-mount/vse/main/profile/WORKAREA/work/content/test.txt

However, the URL for html page is changing from http://xx.****.x.****/iw-cc/command/iw.group.preview_file?vpath=//server-name/vse/main/profile/WORKAREA/work/content/test.html to http://xx.****.x.****/iw-mount/vse/main/profile/WORKAREA/work/content/test.html (no /iw/cci/meta/injection)

Thanks

Rick Poulin

That's because VisualPreview (that annoying toolbar thing) is injected on the iw-mount version, but not in the iw/cci version. Since the preview bar only applies to HTML, you're redirected to iw/cci for any other mime type.

Sounds like your problem may actually be with TeamSite's injection of that toolbar. I'd suggest looking at the iw.cfg, particularly the iwproxy rules. You could also run iwproxy in debug mode (refer to the CLT guide) and look at what's happening to your HTTP requests as they come in.

tech17

That's because VisualPreview (that annoying toolbar thing) is injected on the iw-mount version, but not in the iw/cci version. Since the preview bar only applies to HTML, you're redirected to iw/cci for any other mime type.

Sounds like your problem may actually be with TeamSite's injection of that toolbar. I'd suggest looking at the iw.cfg, particularly the iwproxy rules. You could also run iwproxy in debug mode (refer to the CLT guide) and look at what's happening to your HTTP requests as they come in.

As mentioned, I ran the CLT iwproxy -d and got the attached result.
Also, for better understanding I am attaching my iw.cfg and rewrite.conf.
I read somewhere about rewrite.conf, however I didn't understand much in that.

Thanks.

Rick Poulin

Your proxy debug output shows a normal configuration, so that's fine. However, you couldn't get useful trace output because the (real) iwproxy was already running. Kill the iwproxy process and then run your own iwproxy -d again. You should be seeing requests as they're coming in -- so refresh your broken page and you should see where it's sending it.

Adam Stoller

Your proxy debug output shows a normal configuration, so that's fine. However, you couldn't get useful trace output because the (real) iwproxy was already running. Kill the iwproxy process and then run your own iwproxy -d again. You should be seeing requests as they're coming in -- so refresh your broken page and you should see where it's sending it.

To be, perhaps, a bit clearer - the process of debugging with iwproxy is:

tech17

[QUOTE=ghoti]To be, perhaps, a bit clearer - the process of debugging with iwproxy is:

What kind of tweaking in iw.cfg, as I changed few entries then reverted back but didn’t get much. Kindly elaborate if possible.Thanks

Adam Stoller

[quote=tech17][quote=ghoti]To be, perhaps, a bit clearer - the process of debugging with iwproxy is:

It depends on the issue(s) you're trying to resolve, whether you need more, fewer, or different iwproxy settings - the Administrator's Guide is generally the guide to all the various options - but ultimately it depends on your environment.

tech17

Hey Rick,

Did you get a chance to take a look at the new log file?
It would be great if you could provide some input or suggestions.

Thanks.