External Task not executing when called from Workflow.

Just for fun dump the command you are executing to a file post it.

it is just a simple command `/usr/iw-home/OpenDeploy/OpenDeployNG/bin/iwodstart test_ictest_staging`. I am using this command for dubugging purpose, original one used file list. None of them are working.

I have tried using both back ticks and system(). Both methods work for independent perl script but not in workflow called script.

ADHealthCheck.rptdesign

Migrateduser

Run your externaltask script in debug mode passing the job_id, task_id and areavpath from the command line.

Silix

Did you try running the script called by the "external task" on the command prompt with the variables jobid, taskid and workarea vpath ? What do you get ?

- Silix

Did you try running the script called by the "external task" on the command prompt with the variables jobid, taskid and workarea vpath ? What do you get ?

- Silix

I did just now, it runs fine, gives this:

/usr/iw-home/iw-perl/bin/iwperl /usr/iw-home/local/bin/debug.ipl 133441 133445 /default/main/ic_test/STAGING

Locating OpenDeploy service.
OpenDeploy server host: localhost, RMI registry port: 9173
Got OpenDeploy service
>>>>>-- Start deployment test_ictest_staging.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment test_ictest_staging finished:
ID: m382 Start time: Tue Mar 07 13:09:58 EST 2006
Status: Completed

ERROR:02426: Task or Workflow not active

The workflow never fails, it completes cleanly, when started from temsite interface.

Run your externaltask script in debug mode passing the job_id, task_id and areavpath from the command line.

this is the list of environment variables when called from command line:

HOME = /export/home/sp58r
LOGNAME = sp58r
MAIL = /usr/mail/sp58r
PATH = /bin:/usr/bin:/usr/ucb:/usr/bin/X11:/usr/local/bin:/usr/local/bin
PWD = /usr/iw-home/bin
SHELL = /bin/ksh
SSH2_CLIENT = 137.20.164.106 1448 137.20.225.56 22
SSH2_SFTP_LOG_FACILITY = 0
TERM = vt100
TZ = US/Eastern
USER = sp58r
_ = /usr/iw-home/iw-perl/bin/iwperl

And this is the list when called from workflow:
EXITVAL = 0
IW_HOME = /usr/iw-home
IW_MOUNT = /iwmnt
IW_MOUNT_PRIVATE = /.iwmnt
IW_RELBINDIR = /usr/iw-home/bin
IW_STORE = /u002/iw-store
LC_COLLATE = en_US.ISO8859-1
LC_CTYPE = en_US.ISO8859-1
LC_MESSAGES = C
LC_MONETARY = en_US.ISO8859-1
LC_NUMERIC = en_US.ISO8859-1
LC_TIME = en_US.ISO8859-1
PATH = /usr/iw-home/private/bin:/usr/sbin:/sbin:/usr/bin:/usr/iw-home/private/bin:/usr/iw-home/bin:/usr/sbin:/sbin:/usr/bin:/usr/ucb:/usr/local/bin:/usr/iw-home
RESULT = 0
TRACEFILE = /var/adm/iwtrace.log
TZ = US/Eastern
UNIX95 = 1
_INIT_NET_STRATEGY = none
_INIT_PREV_LEVEL = S
_INIT_RUN_LEVEL = 3
_INIT_RUN_NPREV = 0
_INIT_UTS_ISA = sparc
_INIT_UTS_MACHINE = sun4u
_INIT_UTS_NODENAME = sun92.pseg.com
_INIT_UTS_PLATFORM = SUNW,Sun-Fire-480R
_INIT_UTS_RELEASE = 5.8
_INIT_UTS_SYSNAME = SunOS
_INIT_UTS_VERSION = Generic_108528-23

You are hard coding the path to OD in the script ?

Silix

I did just now, it runs fine.
The workflow never fails, it completes cleanly, when started from temsite interface.

The Workflow gets completed and the External task runs fine when run on command line.

So the only possiblity I think is the User access error. OpenDeploy when invoked by an external script runs as a specific logon account . That account must be added to your master.uid file.

You can get the account name by creating a test deployment and invoking it in a DNR of another deployment. When you see the deployment list in the OD admin GUI, you can get the logon account name. It would be something like domain/pubservice. Add it to your master.uid and reset TS. That should work.
- Silix

ryandev

We've seen a problem with one of our testing servers. TS 6.5 sp1. The external task will not run.

Try turning off the iwprocessd in iw.cfg.

[iwserver]

use_process_daemon=no

ryandev

We hadn't done any config changes. Just a simple restart of TS and it started to happen. To fix, we were told to upgrade to SP2 - but no bug was identified as the culprit.

You are hard coding the path to OD in the script ?

Yes.

The Workflow gets completed and the External task runs fine when run on command line.

So the only possiblity I think is the User access error. OpenDeploy when invoked by an external script runs as a specific logon account . That account must be added to your master.uid file.

You can get the account name by creating a test deployment and invoking it in a DNR of another deployment. When you see the deployment list in the OD admin GUI, you can get the logon account name. It would be something like domain/pubservice. Add it to your master.uid and reset TS. That should work.
- Silix

this still does not explain the core dump file (segment fault) and the fact that the system has been running for more than 2 years without problem. Anyways I will try this.

We've seen a problem with one of our testing servers. TS 6.5 sp1. The external task will not run.

Try turning off the iwprocessd in iw.cfg.

[iwserver]

use_process_daemon=no

and this too.

We hadn't done any config changes. Just a simple restart of TS and it started to happen. To fix, we were told to upgrade to SP2 - but no bug was identified as the culprit.

exactly so here too!!! But our system is OD5.6

nettai

exactly so here too!!! But our system is OD5.6

Kumaarsuraj ... i am also facing the same problem. i have checked all the pointer that have been mentioned in this thread still i am unable to do a deploy through external task.

please help me out

Nidhi_Agrawal

nettai,can u chk that your ipl is calling from workflow or not.
Just put some debug statements on ipl file before running the od command and some more debug stmt after that command and chk ur log.
And also check the command by printing them log.
Sometime issues can be of "/" or "\" type.

Nidhi..

Kumaarsuraj ... i am also facing the same problem. i have checked all the pointer that have been mentioned in this thread still i am unable to do a deploy through external task.

please help me out

nettai

nettai,can u chk that your ipl is calling from workflow or not.
Just put some debug statements on ipl file before running the od command and some more debug stmt after that command and chk ur log.
And also check the command by printing them log.
Sometime issues can be of "/" or "\" type.

Nidhi..

Nidhi..

All those are perfectly fine.. anyway i have found the issue and the right document for this is as follow:
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=49449

Actually their is a ipl file in the opendeployng/solution/perl folder "iwodstart.ipl" . its required to call this ipl file instead of "iwodstart.exe"

Thanks,
Karthik

hello, i am trying to run ipl script from submit workflow, but it seems that my workflow doesnt invoke the command.

when i run the cmd from windows cmd window the script runs perfect... but when i run the submit workflow, the files gets submited but this task doesnt invoke the ipl script?

any suggestions or comments?

[HTML]

[/HTML]

i even tried just the cmd bellow as a cmd for the external task but it still doesnt get run from the workflow.

[HTML]
[/HTML] which has this inside it d:\iw-home\iw-perl\bin\iwperl d:\cr\sort_log.ipl

Simple question, are are trying to deploy from a TS server to another (or the same) TeamSite server ?

Can you post the receiver logs generated ?

well actually this doesnt have anything to do with Opendeploy... sorry, i just found a thread that s similar to what i need...

this is a regular submit workflow in TS... all it does is:

(regular submit task) -> then (external task which calls a java app which runs fine) -> then (external task to run a perl script) -> then (end task).

everything runs fine, except the perl script task that i post on here, the workflow doesnt complain about anything at all, unless i make some syntax error inside the external task( to show me that it actually goes throw the task)

and this didnt do it neither Smiley Sad

use_process_daemon=no

Well you should start a new thread.

Is there any indication that the script starts ? Do you have any logging in the very beginning ?

WF tasks behave differently. The WF engine appends Job ID, Task ID and WA name to the end of the call.

Also, the WF will never restart unless you run a callback in the Perl script. I think you should RTFM on external tasks and steal some code to get yourself started.

Andy