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

Help on executing External Task

Balu110

I am trying to execute a perl program using an external task but for some reason the task is hanging and not proceeding further. Unable to find any errors in the log files. Also, I don’t see any errors, if I execute the perl program independently.

Code snippet:
<externaltask name="External Script" description = "Executing External Script" owner="__TAG__('iw_user');">
<areavpath v="__TAG__('iw_workarea');"/>

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

<command v="/clocal/user/client.ipl"/>

</externaltask>

Can some one help me to identify the problem?

Thanks in advance.
Balu

Edited by Balu on 05/05/05 01:40 PM (server time).

Find more posts tagged with

Comments

jbonifaci

Can you post client.ipl as well? I assume it is calling back and transitioning the workflow task? What arguments are you passing to the script from the CLT?

Balu110

The IPL doesn't need any input parameters. So I am not passing from the external task. Attachcing the IPL for your info.

nipper

Can you post your log file as well ? Just curious how far it got (fi there is a log file)

BTW, you are not calling back if the log files are not created, so that is a likely problem.
Also, where do you think your print statements will go ?

Balu110

To answer your questions:
1- It is not all creating any log files.
2- I have added callback, if log files are not created. But same problem
3- I thought the print statements will go to job_error log or access_log but I don't see it either of those.

Thanks,

james1

This part of your Perl script:

   print "Trying to Create logdir\n";
   mkdir -p $logdir`;
   `chmod 775 $logdir`;

doesn't look like valid Perl to me.

Hope this helps.
-- James

--
James H Koh
Interwoven Engineering

nipper

Did you miss cut & paste something ? James's comment is correct, you are missing the
beginning tick (`) on the mkdir. That should never have run/passed the interpreter.

Balu110

Yes. I missed ` while pasting on the forum thread.

--------------------------------------------------
print "Trying to Create logdir\n";
`mkdir -p $logdir`;
`chmod 775 $logdir`;
--------------------------------------------------

As I mentioned earlier, I able to execute the IPL independently and it is creating the directories and output files as I expected. But the same is not happening when I am calling from a workflow external task.

Edited by Balu on 05/06/05 06:45 AM (server time).

iwovGraduate

From what you mentioned it looks like the script is not getting executed at all. Is that correct ?

Is this the correct (full) path to your ipl ? - "/clocal/user/client.ipl"

You might want to explicitly invoke iwperl -
<command v="full_path_to_iwperl/iwperl /clocal/user/client.ipl"/>

Balu110

Yes. I am trying to execute a perl program using an external task but for some reason the task is hanging and not proceeding further.
The IPL does exists in this path: /clocal/user/client.ipl. Also you can find the my external task code snippet in the initial posting of this thread.

Edited by Balu on 05/06/05 07:09 AM (server time).

cliffhanger

Balu,
Besides what Samir said, you can also try hardcoding the log path in your ipl. Then log all the variables, and see till what point you are reaching in the LOG.
Don't you also need to give the path to "iwperl" in <command>?? something like:

<command v = "IWHOME/iw-perl/bin/iwperl FULLPATH-TO-YOUR-IPL"/>

-cliff

Edited by cliffhanger on 05/06/05 07:14 AM (server time).

jbonifaci

Bala, I think you miss understoond what samir said. He suggested you add the full path to iwperl to your external command as well:

<command v="full_path_to_iwperl/iwperl /clocal/user/client.ipl"/>

~Jeff

Balu110

Jeff,
I thought the fullpath is not required for command line, since my first line of IPL has that. But I went modified as you suggested,

<command v="/InterWoven/iw-home/iw-perl/bin/iwperl /clocal/user/client.ipl"/>

Noticied the following error in the error_log:
[Fri May 6 10:25:16 2005] [error] [client 53.232.26.130] File does not exist: /InterWoven/iw-home/httpd/iw/launchpad100/com/interwoven/launchpad100/IWLaunchPad$COMClassObject.class

The above mentioned error is not coming every time when I execute my workflow. So I am not sure whether it is related to the IPL.

Thanks in advance.

Edited by Balu on 05/06/05 07:56 AM (server time).

iwovGraduate

If you don't know how to debug external tasks, heres your chance...

Run this from command line

"/InterWoven/iw-home/iw-perl/bin/iwperl /clocal/user/client.ipl job_id task_id areavpath"

Try that and post what happens.

job_id = id of thw workflow that hangs on the externaltask.
task_id = taskid of the externaltask which runs client.ipl and is hanged.
areavpath = the vpath to the workarea in which job was started.

beforeDrawLegendItem.rptdesign

Balu110

As I mentioned earlier, I able to execute the IPL independently (meaning from the command line) and it is creating the directories and output files as I expected. But the same is not happening when I am calling from a workflow external task.

iwovGraduate

As I mentioned earlier, I able to execute the IPL independently (meaning from the command line) and it is creating the directories and output files as I expected. ...

Did the hanged task transition to next task when you did the above ?

Migrateduser

If you're not creating a log file with this script, then it's not getting to the CallBack block. Your code might be immaculate, but if you don't transition, your workflow will hang. The script itself will not hang, or use CPU for an indefinite amount of time, if it executes okay. But, your workflow will not do what you want it to.

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3
By the way, I miss Unix terribly.

Balu110

No. It is not transitioning to next task.

Migrateduser

You really should have a CallBack within your else statement right after you make your one and only CallBack in the script currently. I think that's where you're getting stuck. Whether you want the task to fail or, more likely, if you want the task to transition successfully if the log file is not written, you need to transition it one way or another.

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3
By the way, I miss Unix terribly.

Balu110

I tried the following now:
In the external task I commeted the current client.ipl and put the other working email IPL and the external task worked and transitioned to next task. Then I tried to put my client.ipl and the external task didn't transition to the next task and didnot create the output log files as well. This is confirming that the external task is hanging because of the cilent.ipl.

I don't see any errors, If I execute the client.ipl from the command prompt and it is creating the output file as it suppose to. So how do I approach this problem.

Again thanks in advance,

Balu110

Dave, as you mentioned I have added callback to the else and the same problem, no output log files.

My current callback look as follows:
----------------------
if ( -f $logfile ){
#print "Successful Log Output\n";
#$task->CallBack(0);
$task->CallBack(2);
} else {
print "Logs not created correctly\n";
$task->CallBack(0);
}
----------------------
BTW, how do I find the call back code(s) description?

Migrateduser

I assume your log file is important to you, so I'd figure out why that isn't being created / modified. The fact that your log file doesn't exist is blocking your code from executing the CallBack because it's within an IF statement. Like I mentioned before, you really should have an else statement there with a CallBack -- it's better coding standards and it won't cause this to happen. That is, your IF block there isn't being executed.

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3
By the way, I miss Unix terribly.

nipper

Change your code to make a log file in /tmp (since you are on Unix),
still looks to me as a permissions issue.

Andy

Balu110

Dave, After adding the above mentioned callbacks in the "If & Else "blocks, the external task is transitioning to next task but not creating the output log files.

nipper

Then it is a permissions issue. You have the permission to create the directory & log file.
The process that the script is running as (may be iwui) does not.

Move the log to /tmp, see what group and user creates the file. Then you know what
group/user needs write access to your directory