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

iwproxy Connection Failed.

RichieRich

A common response to the following question would be "Has anything changed." The answer is no. Smiley Surprised

) With that said, last Friday everything was fine and working great. Today a user was trying to preview a page and received:

Connection Failed
iwproxy was unable to open a connection to: server.domain.com:81
Reason: Connection refused.

(Note: I changed server.domain.com from the real server/domain just for this post.)

I looked into the iw.cfg file and see customer_webserver_port=81. Apache is running, and this file hasn't changed. I did a netstat -an | grep 81 and I don't see anything listening on port 81. I tried stopping and starting teamsite in hopes the problem was maybe a processed died, no such luck.

The iwserver.log shows:

Interwoven Web Daemon starting ...
Interwoven Proxy Server starting ...
Interwoven Servlet Engine starting ...

What can be the issue for this? When teamsite starts up, it excepts a web server to be listening on port 81 correct?

If this is true, I don't know what might be the problem or what would be a valid path for debugging to track down the issue.

Any help would be greatly appreciated.

-[ Richie Rich ]-

Find more posts tagged with

Comments

Migrateduser

There are a few other logs to check, proxy has one and so does servletd. I know I posted the log file locations in a previous post, but I don't have time to look now. Those would be the first place I'd look. Could you provide more info on your environment, TS Version, Op Sys, etc?
regards,

lissa

RichieRich

TeamSite: 5.5.2 Build 15650 Interwoven 20030110
OS: Solaris SunOS (5.8)

I also checked out Tomcat's Log ($iw-home/servletd/logs/servlet.log)

Does teamsite's startup scripts invoke an instance of Apache to act has it's default Content Web server?

I don't see any location for proxy logs.

-[ Richie Rich ]-

Allora

I encountered this error, as well, but when running TS 6 on Windows 2000 Server. The setting in iw.cfg also showed as port 81. I looked in IIS at the settings for the Default Web Site and found the TCP port to be 82. I changed the setting in iw.cfg to port 82, reset TeamSite and the problem went away. Perhaps you can apply this information to your implementation.

RichieRich

After digging into this problem, I see apache isn't listening on port 81.

Teamsite has a built in web server (iwwebd) which clients connect to on port 80 by default. The Apache server that is setup to listen on port 81 isn't running. During startup it stops with the following exception:

Syntax error on line 43 of /etc/apache/jserv.conf:
ApJServLogFile: file '/var/apache/logs/mod_jserv.log' can't be opened
/usr/apache/bin/apachectl start: httpd could not be started

I checked out /etc/apache/jserv.conf on line 43 and all tht is on there is

ApJServLogFile /var/apache/logs/mod_jserv.log

The file does exists and the permissions for this file are configured to give nobody so that nobody is the owner with rw and the group is bin with r.

I ran lsof | grep mod_jserv.log to check and see if the file is held open by another process, but no such luck.

-[ Richie Rich ]-

Migrateduser

Glad to hear you've tracked down the problem to your apache installation. Are you actually using jserv? If not, the simplest thing is probably to just comment out the mod_jserv bits of httpd.conf, probably including an "Include" directive pulling in the mod_jserv config file.