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

Edit DCR hangs/FormAPI fails

Adam Stoller · 2005-07-26T12:38:10+00:00

EnvironmentTeamSite 6.5 SP1Solaris 9 Problem(I've got a case open with Support, but while I'm waiting I figured I'd see if anyone else has some ideas...)Sometime between the middle of last week and yesterday our DEV system stopped being able to render DCRs/DCTs correctly; it takes about 10-15 minutes for it to finally…

Adam Stoller

Environment

Problem

Given that, anyone have any ideas?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Johnny

Try sticking a http sniffer to see which URL's are halting.

If you are using FireFox, you can download Live HTTPHeaders, it works great in these situations. MS have a proxy called Fiddler which you could use for IE.

It's probably a good starting point to zoom into the problem.

John Cuiuli

Adam Stoller

I tried the Live HTTPHeader thing - and it looks like it *is* related to FormAPI somehow ......
----------------------------------------------------------
tsserver>http://tsserver/iw-cc/formspub/dcrfileinfo.jsp?vpath=//tsserver/vpath-to-dcr

GET /iw-cc/formspub/dcrfileinfo.jsp?vpath=//tsserver/vpath-to-dcr HTTP/1.1
Host: tsserver
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://tsserver/iw-cc/command/iw.formspub.userscript?vpath=//tsserver/vpath-to-dct
Cookie: JSESSIONID=jsessionid; IWAUTH=iwauth; iw_user=astoller; iw_role=master; iw_which_ui=ccpro

HTTP/1.x 200 OK
Date: Tue, 26 Jul 2005 15:12:34 GMT
Server: Apache-Coyote/1.1
Vary: Cookie
Set-Cookie: IWAUTH=iwauth; Expires=Tue, 19-Jan-2038 03:09:07 GMT; Path=/
Content-Type: text/html;charset=UTF-8
Content-Length: 760
X-Cache: MISS from tsserver
Keep-Alive: timeout=15, max=75
Connection: Keep-Alive
----------------------------------------------------------
(this is where it seems to start hanging .... when it tries to get one of our javascript sources)
----------------------------------------------------------
http://tsserver/iw-mount/default/main/ED/en/STAGING/formapi/globalfunctions.js

GET /iw-mount/default/main/ED/en/STAGING/formapi/globalfunctions.js HTTP/1.1
Host: tsserver
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://tsserver/iw-cc/command/iw.formspub.userscript?vpath=//tsserver/vpath-to-dct
Cookie: IWAUTH=iwauth; iw_user=astoller; iw_role=master; iw_which_ui=ccpro

HTTP/1.x 504 Gateway Timeout
MIME-Version: 1.0
Server: Simple, Secure Web Server 1.1
Date: Tue, 26 Jul 2005 15:14:33 GMT
Content-Type: text/html
----------------------------------------------------------
http://wdchqdtmsd01.dev.ed.gov/iw-mount/default/main/ED/en/STAGING/formapi/article.js

GET /iw-mount/default/main/ED/en/STAGING/formapi/article.js HTTP/1.1
Host: wdchqdtmsd01.dev.ed.gov
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://wdchqdtmsd01.dev.ed.gov/iw-cc/command/iw.formspub.userscript?vpath=//wdchqdtmsd01/vpath-to-dct
Cookie: IWAUTH=iwauth; iw_user=astoller; iw_role=master; iw_which_ui=ccpro

HTTP/1.x 504 Gateway Timeout
MIME-Version: 1.0
Server: Simple, Secure Web Server 1.1
Date: Tue, 26 Jul 2005 15:16:33 GMT
Content-Type: text/html
----------------------------------------------------------
(Then ... )
----------------------------------------------------------
http://wdchqdtmsd01.dev.ed.gov/iw-cc/base/styles/iw.css

GET /iw-cc/base/styles/iw.css HTTP/1.1
Host: wdchqdtmsd01.dev.ed.gov
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
...
HTTP/1.x 304 Not Modified
Date: Tue, 26 Jul 2005 15:16:34 GMT
Server: Apache/1.3.31 (Unix) mod_fastcgi/2.4.2 mod_ssl/2.8.19 OpenSSL/0.9.7d
Connection: Keep-Alive
Keep-Alive: timeout=15, max=100
Etag: "a040-66fd-41f8f58a"
Vary: Cookie
....
(it renders the form without having run the FormAPI code)
=============================
[DEVTS] bin > ls -l /default/main/ED/en/STAGING/formapi/globalfunctions.js
-r-xr-xr-x 1 astoller iwglobal 11485 Apr 28 16:21 /default/main/ED/en/STAGING/formapi/globalfunctions.js*
[DEVTS] bin > head -2 /default/main/ED/en/STAGING/formapi/globalfunctions.js
// Global Functions
//
=============================
The file is there - it's readable by everyone.
We're trying to check with the OPS group to find out if any changes were made recently to the firewall in our DEV/TEST environment.
If you have any other thoughts, please pass them along ...
(Thanks much for the Live HTTPHeader pointer)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Johnny

Looks like it might be the virtualization server as it's trying to access the formapi in your iw-mount location




http://wdchqdtmsd01.dev.ed.gov/iw-mount/default/main/ED/en/STAGING/formapi/article.js

What happens when you put that on a blank (no cookies etc) web browser itself.
Then try it directly to your webserver port

EG

http://wdchqdtmsd01.dev.ed.gov:81/iw-mount/default/main/ED/en/STAGING/formapi/article.js

If the webserver responds directly, then maybe something fishy (sorry) has happened to the proxy server (rewrite rules changed??)

Can you virtualize any other content in that location or any other location?

Also try to see if you can hit those URL's directly from the local server.
There are scripts called GET, HEAD in the iwperl/bin directory that will let you make http requests. That might show if it is an external firewall/proxy issue. You could also use telnet, but GET, HEAD are probably easier.

John Cuiuli

Adam Stoller

Going to port 81 (customer web server) works fine - I see the JS code in the browser window (since it's not being interpreted through HTML code)
Going to port 80 (iw-webd) it hangs with an eventual 'HTTP/1.x 504 Gateway Timeout'

There's only one iwproxy rule in iw.cfg:
_regex=/(images/govben\.gif)=/iwmnt/default/main/ED/en/STAGING/$1

[there's another one to turn off smart context editing for images, doc, etc.]

iwproxy appears to be running fine... though I just ran it in debug mode and tried to "view" and HTML page and saw the following:[Request from client:]
GET /iw-mount/default/main/ED/en/STAGING/formapi/globalfunctions.js HTTP/1.1
Accept: */*
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Accept-Encoding: gzip,deflate
Accept-Language: en-us,en;q=0.5
Connection: close
Cookie: IWAUTH=iwauth; iw_user=astoller; iw_role=master; iw_which_ui=ccpro
Host: localhost:1080
Referer: tsserver>http://tsserver/iw-cc/command/iw.formspub.userscript?vpath=//tsserver/vpath-to-dct
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
X-Forwarded-For: ip-address-of-client-machine
X-Forwarded-Host: ts-server
X-Forwarded-Scheme: http
X-Forwarded-Server: another-ip-address

[Using Referer pathtrack: '/iw-cc/command/iw.formspub.userscript']

[opening proxy connection to: another-ip-address:81]
....long wait...
[::ERROR:: iwproxy server connect failed]ping another-ip-address
no answer from another-ip-addressI'm looing to track down what this IP address is ...

I double checked with the Live HTTPHeaders on our PROD system (since I can't just take down iwproxy there) and it works just fine there - using the /iw-mount path to the HTML file.

so it seems pretty likely that there's something "network" related involved here ... I'm going to have to talk to our OPS folks some more ...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Johnny

Can you preview any content - very strange if you can?

Have there been any changes to iw-webd/conf/rewrite.conf.template ? That's where all the redirection is happening.

Also did you try connecting directly to the proxy? http://server:1080/iw-mount..../

Doing these steps on the local server might give you a clue too.

But if this is the only file that you can't preview, it does not make any sense at all.

John Cuiuli

Adam Stoller

User (customer) Error.

Unbeknownst to me, the IP address of the TeamSite server was changed recently when our OPS folks were attempting to move the DEV machine from the TEST network to the DEV network (but then ended up moving it back to the TEST network anyway).

They changed the IP address - but we never changed the IP addresses in the iw.cfg file for the 'host' and 'customer_webserver_host' settings.

I finally managed to track this down when I found out that viewing simple HTML files didn't work - and then ran iwproxy in debug mode and saw an IP address, that I didn't reconize nor was able to ping, referenced near an error message.

[*sigh*]

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Johnny

At least you found out about Live HTTP Headers Smiley Happy

John Cuiuli