Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
workflow and opendeploy
mogoo
Help! We have a workflow with an external task that calls on an ipl. The ipl calls on iwodstart to deploy the attached files. This workflow was working fine for a couple of months until a couple of days ago, when it suddenly stopped working.
The 3 files associated with this wf (2 mentioned above, plus the deployment config xml file) haven't been touched, and our sysadmin says nothing has been changed on the server. Furthermore, we have a custom menu item that calls on the very same deployment config file, and it works fine.
In the wf log, when it was working, it would write this:
2003.07.28 (15:23)
Locating OpenDeploy service.
OpenDeploy server host: localhost, RMI registry port: 9173
Got OpenDeploy service.
>>>>>-- Start deployment GO_emergency_deploy.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment GO_emergency_deploy finished:
ID: m221 Start time: Mon Jul 28 15:23:29 PDT 2003
Status: Complete
----------------------------------------------------------------------
now that it's not working, it just writes this:
2003.07.30 (09:54)
----------------------------------------------------------------------
I've run out of places to look. Seems to me like it might be a permissions thing, as the deployment script works fine from the custom menu. Can anyone give me any clues as to where to look?
Thanks for any insight!
maureen
Find more posts tagged with
Comments
nipper
Have you tried just echoing the command line from the Perl script & then running it from the command line as that user ?
That is the first thing I start testing with.
In fact, in all of my ipls, I use something like this:
$cmd = "iwodstart.... > /tmp/OD_log_$$.txt 2>&1"
print LOG "$cmd\n";
$out = `$cmd`;
print "result $out\n";
see if the command runs from the command line first, go from there
Andy
Johnny
Has anything else changed?...
If the workflow itself hasnt, go back and look at what has, including perms etc.
One thing to look at is the number of file handle issue that has been around while trying to run iwodstart within a wf external task.
What version of OpenDeploy are you using?...
instead of the script iwodstart in OD/bin/ try rehashing the iwodstart.ipl in the solutions directory.
I dont think it should apply to OD 5.6, though im not sure, someone else might like to answer that one.
John Cuiuli