Premature end of script?

TS5.5.2 SP3 on Solaris.

I am trying to use the following script in a CGI task and it keeps returning a 500 error. The error_log returns: Premature end of script headers: /opt/teamsite/iw-home/httpd/iw-bin/iw_cgi_wrapper.cgi

I've seen a few threads about this, but they mainly applied to issues with templating.cfg or permissions or premature output. I can run this script fine w/o the wrapper, either from the command line or through the browser.

Can anyone see anything that should interfere with the wrapper that I'm missing?

=============================

#!/opt/teamsite/iw-home/iw-perl/bin/iwperl

# Flush the output buffer right away.
$| = 1;

use TeamSite::CGI_lite;
use TeamSite::Config;
use TeamSite::WFtask;
use TeamSite::WFworkflow;
use FedEx::Usertask;

my($cgi) = TeamSite::CGI_lite->new();
$cgi->parse_data();
my($wfid, $taskid, $area) = (@ARGV[2..4]);
my($task) = new TeamSite::WFtask($taskid);
my($job) = new TeamSite::WFworkflow($wfid);

#my($taskid) = $cgi->{'form'}{'iw_taskid'} || $cgi->{'form'}{'task_id'};
my($task) = TeamSite::WFtask->new($taskid);
my($nexttask) = $taskid + 1;
$area = $task->GetArea() if (!$area);
my($new_owner) = $cgi->{'form'}{'developer'};
my($workflow_roles) = "/opt/teamsite/iw-home/local/config/wft/fedex/roles";
my($role_list)="$workflow_roles/role.uid";
my($branch_path)="/default/main/us/about";
my @developers = FedEx::Usertask::xml_get_dev_users($role_list,$branch_path);

if ($new_owner eq ""){
print<<EOD;
Content-type:text/html

<html>
<head>
<title>Assign developer for Task</title>
</head>
<body>
<h1>Assign developer for task</h1>
<p>Pick a developer:<br/>
<form name="form" action="setdeveloper.cgi" method="post">
<select name="developer">
<option value="">================</option>
EOD
foreach $developer(@developers){
chomp($developer);
print "<option value='$developer'>$developer</option>\n";
}
print<<EOD;
</select>
<br/>
Comments:<textarea cols="50" rows="3" name="comments"></textarea>
<input type="submit" name="submit"/>
</form>
</p>
</body>
</html>
EOD
}
else{
print<<EOD;
Content-type:text/html

<html>
<head>
<title>Assign developer for Task</title>
</head>
<body>
Assigned
</body>
</html>
EOD
$retcode = `/opt/teamsite/iw-home/bin/iwsettaskownerandarea $nexttask $new_owner $area`;

$task->CallBack($retcode, "Set developer to $new_owner");
}
exit(0);

===========================

Thanks,
Mark

Find more posts tagged with

Comments

Migrateduser

It looks to me like you are only outputting the content type header if new_owner is empty, so that could be it, if it isn't. Have you checked

/iw-home/iw-webd/log/error.log

to see if it has anything interesting in it?

bagman

No... I'm printing the content header after the "else" also, although I probably should just print it out before the conditional.

I don't have that log file...assuming it's Apache. I'm running iPlanet and don't think I've ever successfully found where it's logging to. Smiley Happy

The script runs find as a stand-alone. It's something with how it interactes with the iw_cgi_wrapper program.

Thanks,
Mark

Adam Stoller

I'm a bit confused about this script - it looks like part of it was written to be a CGI script and part of it was written to be an externaltask script. If you're running it as a CGI script and you're expecting to get $wfid, $taskid, etc from @ARGV - then your script is going to blow up when you try to create the $task object - and chances are something is being sent to STDOUT somewhere around there.

If you want to debug this a little better - I suggest you make the following changes:#!/opt/teamsite/iw-home/iw-perl/bin/iwperl
use CGI::Carp qw(fatalsToBrowser);
print "Content-type: text/html\n\n";
# Flush the output buffer right away.
$| = 1;

use TeamSite::CGI_lite;
use TeamSite::Config;
use TeamSite::WFtask;
use TeamSite::WFworkflow;
...

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

Migrateduser

I'm not sure I follow you there. Are you saying that you are running iPlanet in place of iw-webd, or are you saying that you are running iPlanet as the customer web server? The latter would make sense, the former would not (unless they made some changes to the unix version between 5.0.1 and 5.5.2 to let you replace iw-webd).

If they changed the directory tree around a bit on the unix version, you could cd to /iw-home and try a find to turn up the logfiles:

find . -name error.log -print

It has to be there somewhere.

bagman

I had wondered about that possibility and tried it a couple of different ways. Still, I would think the only difference between and externaltask and a cgitask would be the interactive web component. At the end of the day, they're both just Perl scripts.

It has to be a bigger problem. I tried to do a basic "Hello World" script - not pulling in any libraries or anything - and am getting the same results.

Migrateduser

Here's a thought - to validate that it's an interaction with iw_cgi_wrapper.cgi, run it without the wrapper and see what you get.

bagman

It runs fine from the command line and bypassing the wrapper.

Adam Stoller

An externaltask script gets its parameters from the command line.
A cgitask script gets its parameters from form variables.
They are NOT the same - especially if you are trying to create TeamSite::WFtask objects within them based on the taskid ..

So ... which is this - an externaltask script of a cgitask script?

Once you make that decision we can talk more about how to debug it.

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

Migrateduser

Are you saying those are two separate instances: a)it runs fine from the command line and b)it runs fine as a custom menu item if you don't use the wrapper, or are you saying that you have only tried 'a'. Fish is right, though - you need to go ahead and sort out which way you are going to do it. Have you already made his suggested change and output the header right after you use the modules?