Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
External Task not starting .ipl
Jeremy
Solaris, TS552
Hi,
We are having problems with External Tasks running in the Workflow. We kick off the WF, the first task is an External Task (start="t"). But this task does not start. However if I try running this task from the command line it executes perfectly. I don't think this is an environment variables problem as the external .ipl does not even start. Tried a very simple task that wrote to a log file and then did a callback, but from Teamsite it does not execute...ie. nothing in the log file. However from the command line it executes fine and transitions the WF to the next task.
The owner of the task is iwadmin.
There are no errors in the iwjoberrors.log file.
I am calling the external task as I normally do, but it does not seem to work. When I run the WF in debug mode and copy and paste the exact command onto the command line it, followed by the jobid, taskid, workarea and files, it works perfectly.
Anyone have any ideas?
Jeremy
Find more posts tagged with
Comments
Adam Stoller
(1) Is the externaltask script executable (chmod +x)?
(2) Is the #! line (the first line) of the perl script pointing to the correct location of iwperl?
(3) Are you parsing the command line arguments correctly?
(4) Are there any errors in iwtrace.log, iwjoberrors.log, or in the iw-webd/logs/error.log ?
If you post the script (as an attachment) and perhaps the wft that calls it, we might be able to provide a better diagnosis.
--fish
(Interwoven Senior Technical Consultant)
Edited by ghoti on 02/24/03 05:56 AM (server time).
Jeremy
Hi,
Thanks for the reply. This problem had actually been persisting for about a week on all the developers machines. However, all of a sudden after I had made my post here ealier today it all seemed to work. Strange I know!!
I am checking with the Infrastructure team to see if they had made any changes to the server.
All a little odd I know!
But to answer your questions all the same:
(1) Is the externaltask script executable (chmod +x)?
Yes
(2) Is the #! line (the first line) of the perl script pointing to the correct location of iwperl?
Yes
(3) Are you parsing the command line arguments correctly?
Yes - as I said it works fine from the command line.
(4) Are there any errors in iwtrace.log, iwjoberrors.log, or in the iw-webd/logs/error.log ?
The following errors were (are now no longer) occuring in the iwjoberrors.log file.
[Fri Feb 21 12:39:58 2003] Could not run /apps/iw-home/iw-perl/bin/iwperl /apps/local/iwov/workflow/scripts/common/validateDCR.ipl for task 40190; retrying in 1 minute
[Fri Feb 21 12:40:00 2003] Could not run /apps/local/iwov/workflow/scripts/common/startWorkflow.ipl for task 40137; retrying in 1 minute
[Fri Feb 21 12:40:35 2003] Could not run /apps/local/iwov/workflow/scripts/common/sendMailUnlock.ipl for task 40132; retrying in 1 minute
[Fri Feb 21 12:40:59 2003] Could not run /apps/iw-home/iw-perl/bin/iwperl /apps/local/iwov/workflow/scripts/common/validateDCR.ipl for task 40190; retrying in 1 minute
[Fri Feb 21 12:41:00 2003] Could not run /apps/local/iwov/workflow/scripts/common/startWorkflow.ipl for task 40137; retrying in 1 minute
I am sure I'll be back on here if the problem returns.
Thanks for your help though
Jeremy
Adam Stoller
Does your TeamSite server meet the memory requirements documented in the TeamSite Administrator's Guide?
Do you have other applications running on the TeamSite server that might be using a lot of memory?
I'm not sure it's either of the above, beacause I believe those usually indicate a failure to "spawn" the external process rather than to "run" them, but it doesn't hurt to check.
--fish
(Interwoven Senior Technical Consultant)
rwinterpacht
I'm currently experiencing this same problem in an upgraded installation of TeamSite 5.5.2, sp3, on Solaris 8. I'm using absolute paths for the perl scripts, all work ok from command line, but WF doesn't call them right...they work in the 5.0.1 env that we upgraded from, too. I even checked to make sure the right users are in master.uid: root, websrv, nobody, iwui. Any help is appreciated.
Adam Stoller
I don't have a Solaris system handy to try things out on - but if you can post (as an attachment) the wft, the scripts, and an 'ls -l' of the directory where the scripts live - then we might be able to take some shots at figuring out what's happening (or not as the case may be)...
--fish
(Interwoven Senior Technical Consultant)
mgal
Are you seeing externaltasks stuck in todo list, is there any information in the trace log?