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

opendeploy and workflow

fuzzy

I have tst 5.5.2 and od 5.5.1 on unix installed and have a workflow that has an external task that calls the iwodstart to start the deployment.
within the external task (perl script) I execute some other perl scripts and the iwodstart command several times.
all the scripts get executed except the iwodstart commands.
If I run the external task from the command line I have no problem and the iwodstart works fine however when it is through the external task in the workflow the iwodstart does not execute (the system call) ???
all other system calls work fine.
This is not due to environment setting (both run as the same user id)
I have noticed that in the iw-home/OpenDeployNG/solutions/perl directory there is a version of iwodstart.ipl
should this one be used when in the external task??
any instight as to what I might be doing wrong would be great help.
I have sp2 patch installed as well (and am in the process of installing latest available patches)

Farzam
ffarzanehfar@yahoo.co.uk"> ffarzanehfar@yahoo.co.uk

Find more posts tagged with

Comments

Adam Stoller

Can you post (as an attachment) the script you are using for your externaltask so that we can see how you are running the command?

Are you running OpenDeploy 5.5.1, 5.5.1 SP1, or 5.5.1 SP2?

The IWODHOME/solutions/perl/iwodstart.ipl is an alternative - it was developed expressly for people using OpenDeploy via workflows on Windows, (because getting error codes through batch scripts didn't seem to work very well) though I believe it has been ported to work on Unix as well.

--fish
(Interwoven Senior Technical Consultant)

fuzzy

Hi Fish,
I have OD sp1 and sp2 installed on both server and base opendeploy
I have attached a very cut down version of the external task.
now the external task works if called from the command prompt but does not work if called from the workflow.
One thing to point out is that I do have a DNR in the deployment, no datadeploy, the other thing is that I have some other command that work fine when called it seems that it is just the iwodstart, I also tried it with the iwodstart.ipl but got the same problem

Farzam
ffarzanehfar@yahoo.co.uk"> ffarzanehfar@yahoo.co.uk

Migrateduser

For whatever it's worth, when I run iwodstart from inside an externaltask, I wrap double quotes around all the input parameters lie this:

my $cmdlinearg = "$ODHOME/bin/iwodstart \"$OdName\" -k filelst=\"$filelist_name\" -V verbose";

my $deployresult = `$cmdlinearg`;

Don't know if that will make a difference or not. I've never had a problem with iwodstart working from inside an externaltask.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

fuzzy

I just tried it (the quotes - and changed it to the a similar format as yours, but it just does not want to start from the external task.
does the external task need to be on a particular location (directory) mine works and creates the logs but just does not want to execute the iwodstart.
any other ideas
what build of teamsite and od server do you have?
Interwoven OpenDeploy(5.5.1 Build 13804 Interwoven 20021119)
iwserver: 5.5.2 Build 14136 Interwoven 20021127

Farzam
ffarzanehfar@yahoo.co.uk"> ffarzanehfar@yahoo.co.uk

Migrateduser

We are running on Solaris (OD 5.5.1 and TS 5.5.2) and if all the other commands are running from your externaltask, there's no reason why iwodstart shouldn't run as well. Does it get hung at the iwodstart or does it appear to skip over it? That just doesn't make sense if it seems to just skip it. As a longshot, maybe check the permissions on iwodstart and make sure the user running the externaltask can execute it. I'm grasping at straws at this point.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Adam Stoller

Could you also post the output that you were capturing in /tmp/t.log - from both a run from the command line, and a run from within a workflow?

--fish
(Interwoven Senior Technical Consultant)

SP4_ulimit.png

SP5_ulimit.png

Migrateduser

fuzzy,

We have received anecdotal reports from a few customers that the iwodstart shell script did not work for them in external tasks but that the Perl scripts do. I have not been able to reproduce this problem, but you may want to try using the iwodstart.ipl in the solutions directory.

Brinko Kobrin
Interwoven Staff Engineer

fuzzy

Hi Brinko,
well this is another situation that causes pain after installed an untested SP pack.
After porting thescript iwodstart.ipl to UNIX,it is working however I still do get the following error:
/app/iw-home/OpenDeployNG/jre/bin/java[17]: /dev/null: cannot create
Segmentation Fault

Farzam
ffarzanehfar@yahoo.co.uk"> ffarzanehfar@yahoo.co.uk

Adam Stoller

If memory serves correct - line 17 of 'java' is a bizarre piece of code that causes erroneous messages such as this to be displayed. As best as we could tell the error message is harmless and can be ignored - we just didn't change the code because it wasn't ours (it was Sun's).

The line involved looks something like this:

PRG=`whence $0` >/dev/null 2>&1

Notice that the redirection takes place *outside* the backtics and there are no quotes surrounding the whole thing.

Line 30 looks very similar and has the same problem.

--fish
(Interwoven Senior Technical Consultant)

nipper

I know this is an old thread but I went through the same thing. Basically ksh would seg fault when spawning from a WFT to iwodstart.

I tried to get the iwodstart.ipl to work, but saw the errors noted above. FInally I was told to try the -inst flag on iwodstart which avoided the problem. How I do not know.

Andy

Test_SSD_File.zip

Test.pdf

Test.zip

fuzzy

Hi Andy,
yes I do not get the segmentation violation and I checked my scripts and I am using the -inst option as well . this could be an explanation..
the other thing was that I converted the iwodstart.ipl to the unix version since it was just NT version and it has been working fine for a while.

Farzam
ffarzanehfar@yahoo.co.uk"> ffarzanehfar@yahoo.co.uk

MikaV

Hi fuzzy

Is it possbile to get that iwodstart.ipl script which you ported to UNIX? I think we have same problem, SPs installed and iwodstart not working anymore from workflow.

fuzzy

Hi Mark send me you email address and I will try and send it to you

Farzam
ffarzanehfar@yahoo.co.uk"> ffarzanehfar@yahoo.co.uk

Migrateduser

I had the similiar problem and had to rewrite the iwodstart into perl version. And it worked out perfectly after I done that. We are running under Solaris 2.8 with TS5.5.2 and OD5.5.1

wmh

We are now seeing this problem as well. Using the -inst switch is not working.

Can someone send me the Unix version of iwodstart.ipl for me to try?

mogoo

ditto, our OD via external tasks is working sporadically. Tried all of the above suggestions. Could someone post a unix version of iwodstart.ipl?
thanks,
maureen

Migrateduser

Here's how I run it on Solaris - works every time...

my $cmdlinearg = "$ODHOME/bin/iwodstart \"$OdName\" -k filelst=\"$filelist_name\" -V verbose";
my $deployresult = `$cmdlinearg`;

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

structure.JPG

mogoo

I'm trying to run it the exact same way, Dave. It worked for 3 weeks solid, then stopped working. Now, every once in a while, it decides to work, but for the most part does not.
A difference in setup, perhaps? TS5.5.2.1, OD 5.5.1, Solaris

Migrateduser

I think we're set up pretty much the same as you. When you say it stopped working, what exactly do you mean? Do you get nothing back from the CLT call? Do you see anything at all in the OD log?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

mogoo

I have the external ipl writing to a log file. When the OD part is working, I get 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)
-----------------------------------

The wft, ipl and deploy config xml were not touched. In fact, that very same xml works fine when it's called from a custom menu item. Our sysadmin says nothing was done to the box in terms of permissions, upgrades, etc.

Dunno what's going on here. Martians must've been playing with our machines.
maureen

nipper

Maureen

Any core files floating around ? run this as root & look for any cores of ksh:

find / -name core -exec file {} \;

If you see this, then java cores ksh out with too many file descriptors open.

Since I upgrades to SP3 and OD5.6 I have not seen this.

HTH

Andy

Migrateduser

Nipper, this is a known issue. Sun has a bug (bug# 4821957) that documents a fd leak with jre1.3..1. We (Interwoven) has a KB article (KB#49799) that documents a workaround. It basically replaces the topline in JRE's java_wrapper script to use usr/dt/bin/dtksh. It seems to have worked for many other customers. If you can't figure out exactly what to change, please open a support case and mention the KB article above, Support can share detail procedure with you.