Error with URL displayed on CGI Task

Hi,

I have an CGI task that displays a link to ipl file within httpd/iw-bin/
In our dev environment this works fine, i click on it and the file displays.
In our test environment when i click on this link i get a 500 Internal Server Error with the follwoing entry in the $iwhome\iw-webd\logs\error.log of
[Tue Jan 14 11:02:54 2003] [error] [client 127.0.0.1] couldn't spawn child process: d:/iw-home/httpd/iw-bin/where_used.ipl

The versions of the file are the same.

Has anyone come across this before or can give me a hint as to where i can go looking to trace where the problem lies?

Cheers,

Hazzie
TS 5.5.2 on NT.

Edited by Hazzie on 01/14/03 03:59 AM (server time).

Find more posts tagged with

Comments

Adam Stoller

How much memory do you have on your test machine?
How many other applications are running on that server?

The cannot spawn error message sounds very much like what I've run into before when dealing with a server that was (a) undersized and (b) overloaded with other applications.

--fish
(Interwoven Senior Technical Consultant)

Hazzie

The basics of the box is as follows
Quad Pentium III Xeon 700 MHz processor,
1MB cache,
4Gig mem
When i looked it was running between 80%-90% idle.
It is dedicated to our test environment for TS and nothing else runs on it (apart from other TS thigns like OpenDeploy).

Hazzie
TS 5.5.2 on NT.

Hazzie

Found the problem "i believe"

In our script where_used.ipl the first line has the path to perl. This was correct for our dev environment however in our test environment perl is in a different location. It was still marked for the path for Dev. However, i am sure that what i have read is that paths to perl in the 1st line of a script do not matter when your working with NT. Maybe thats a fundemental misconception i have been living with.

Another strange thing i noticed about this problem was the following
The script can be run from 2 places. From a clickable link on a cgi task or as a custom menu item from the file menu. Before i altered the path to perl, it worked from the file menu and not from the clickable link (i have just found out). After i modified the path to perl they both worked.
Also,
If i added iw_cgi_wrapper.cgi (not quite sure what this does) to the statement in the clickable link then the script worked.
so
http://stattltsbdc1004.test.lloydstsb.co.uk/iw-bin//where_used.ipl?path_0=y:/default/main/ecommerce/CMF/Sites/Retail/WORKAREA/test_IPR87/assets/link/external/link_shareview.xml&edit=no
became
http://stattltsbdc1004.test.lloydstsb.co.uk/iw-bin/iw_cgi_wrapper.cgi/where_used.ipl?path_0=y:/default/main/ecommerce/CMF/Sites/Retail/WORKAREA/test_IPR87/assets/link/external/link_shareview.xml&edit=no

any comments?

Hazzie
TS 5.5.2 on NT.

Adam Stoller

I didn't think the path to iwperl in the #! line was interpreted on Windows, but the flags (like -w) are.

iw_cgi_wrapper is, I believe, used to do "impersonation" so that the script essentially runs as the user who is logged into TeamSite.

--fish
(Interwoven Senior Technical Consultant)

Hazzie

Thats what i thought about windows and perl scripts. Very peculiar.
Has any one else noticed this sort of behaviour?

Hazzie
TS 5.5.2 on NT.