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

workflow not invoking external script

Priya_N

Hi
i am running Version: 5.5.2 Build 26949 Interwoven 20031029 with OpenDeploy:
Version 5.6.0.1.0 Build 21220 Interwoven 20030618

We had some workflows configured and working / Now I find that the workflow never invokes any external scripts/

to check I wrote a very simple workflow like

Start of Example workflow

<externaltask name="Email_Author_Approve"
owner="team1000"
description="Approved"
start="t">

<areavpath v="__TAG__('iw_workarea');"/>

<successors>
<successorset description="End">
<succ v="End"/>
</successorset>
</successors>

__INSERT__("<command v='$iwhome/iw-perl/bin/iwperl $iwhome/local/config/wft/publish/teamsite.ipl '/>");

</externaltask>
<endtask name="End">
<activation>
<pred v="Email_Author_Approve"/>
</activation>
</endtask>
</workflow>

End of Workflow

Now teamsite.ipl contains just the following

#!/opt/teamsite/iw-home/iw-perl/bin/iwperl
use TeamSite::WFtask;
use TeamSite::WFworkflow;

my $taskid = $ARGV[1];
my $task = new TeamSite::WFtask($taskid);
my $iwhome = TeamSite::Config::iwgethome();

open(FILEOUT, ">>/opt/teamsite/iw-home/local/config/wft/publish/test.dat") or die "Cannot open file: !";

print FILEOUT "\n Started teamsite.ipl at localtime() . ...\n";

print FILEOUT "Finished\n";
close FILEOUT;

$task->CallBack(0);
exit(0);

Even This script is never being called iwjoberrors.log shows the following

/opt/teamsite/iw-home/local/config/wft/publish/teamsite.ipl for task 5973; retrying in 1 minute

All these in a production server where we had the application running.

ANy clues as to what went wrong ???

Edited by Priya_N on 01/22/04 05:00 AM (server time).

Find more posts tagged with

Comments

Adam Stoller

Check the script by running it from the command line with
iwperl -w -c scriptname

Check for error messages in iwtrace.log and iwserver.log - perhaps you're running out of memory and TeamSite is failing to spawn the process because of that.

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

Priya_N

Hi

Thanks for your suggestion / iwperl -w -c doesnot produce any error syntax of all the wft's are OK. Also iwtrace does not contain any values. iwtrace.log size is zero bytes. iwserver log contained core dumped messages which vanished when I deleted the core file.

Priya_N

A related post is at

http://devnet.interwoven.com/forums/cgi-bin/showflat.pl?Cat=&Board=DOWNLOADS_WORKFLOWS&Number=10269&page=&view=&sb=&o=&vc=1

unfortunately the above post dosent help

nipper

1 Post the XML output from the WFT

2 Try running the EXACT perl command from the commandline that is listed in the XML, post the output (it will likely be an error, but which error is critical).

Adam Stoller

I'd ask whether the script was in fact marked executable, but you seem to be running it through iwperl within the wft (not required for Unix, only required for Windows)

How much memory do you have on the server? What other applications (besides TeamSite and OpenDeploy) are running on the server?

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

Priya_N

All the files (ipl's and wft ) infact every other file is given 755 permission. The external script that is supposed to be called does have 777 permission.

memory is 4 GB .

This is a dedicated teamsite server / no other application run on this machine . Only Teamsite and OD are available .

nipper

I see you are trying to run iwodstart and iwsendmail as a command, can you write a perl script that wraps around those commands. That is commonly what happens.

Try a perl command like this:

#!/where/ever/perl/is/bin/iwperl
use TeamSite::WFtask;
use TeamSite::Config;
use TeamSite::WFworkflow;
open LOG (">/tmp/IT_WORKED");
print LOG "IT WORKED \n";
CLOSE (LOG);
my $wfID = $ARGV[0];
my $taskID = $ARGV[1] ;
my $workarea = $ARGV[2];
my ($task) = new TeamSite::WFtask($taskID);
$task->CallBack(0,"Mail worked");
exit;

Priya_N

I am attaching the sample perl file which was used to chk if the script is ever being called

#!/opt/teamsite/iw-home/iw-perl/bin/iwperl
use TeamSite::WFtask;
use TeamSite::WFworkflow;
my $taskid = $ARGV[1];
my $task = new TeamSite::WFtask($taskid);
my $iwhome = TeamSite::Config::iwgethome();
open(FILEOUT, ">>/tmp/wft_taskerror.log") or die "Cannot open file: !";
print FILEOUT "\n" . localtime() . ": Testing Started...\n";

print FILEOUT "Finished\n";
close FILEOUT;

$task->CallBack(0);
exit(0);

This script runs well from shell prompt nothing is printed to the log file when we invoke from workflow

Priya_N

To add a few more points

even the sample workflow prints the same error msg in iwjoberrors.log

#[Thu Jan 22 14:03:43 2004] Could not run /opt/teamsite/iw-home/iw-perl/bin/iwperl /opt/teamsite/iw-home/local/config/wft/publish/teamsite.ipl for task 5664; retrying in 1 minute

Priya_N

Hi

Interwoven support suggeted the following change in iw.cfg

use_process_daemon=no

I made the change and all seeem to work fine Smiley Happy

Any clues as to what use_process_daemon=no means / and what relation does it have with a perl file invoking a opendeploy script ?