Segmentation Fault when executing Workflow

Has anyone seen Segmentation faults when executing workflows?

We have an OpenDeploy ipl script that runs fine from the command line, but gives a segmentation fault when executed as a part of Workflow.

Find more posts tagged with

Comments

Migrateduser

Do you have a core file (say in the 'iw-home' directory) to examine? That would help us understand where the segmentation fault is coming from (from Perl, from OD, from TS, etc.)... Does the script itself run, but then die when it tries to run opendeploy?

--
Evers Ding
Staff Engineer, Interwoven

harrij

We have excatly the same problem with TS 552 and OD 551.

We are having problems with getting an external task to work. This task includes a perl-script which uses iwodstart CLT to initiate a deployment. The script runs smoothly from command line, but from workflow it seems to crash. Also, the iwodstart command works when run from the command line and the deployment finishes correctly. Only when the iwodstart is called from within a workflow does it crash and logs "segmentation fault" to iwtrace.log The problem seems to affect all our workflows which use external task to call Perl script which in turn calls iwodstart.

So far it seems that the iwodstart is problematic component, ie. it or something it calls segfaults when the iwodstart is invoked from the workflow.

Adam Stoller

Try using IWODHOME/solutions/perl/iwodstart.ipl rather than IWODHOME/bin/iwodstart -- some folks have found this to work more reliably (especially on Windows, where the latter is a '.bat' script).

--fish
(Interwoven Senior Technical Consultant)

harrij

Our conclusion so far is, that the ipl-script gets called from the task, but the iwodstart the ipl calls crashes at some point. The task even gets ok-return code from the ipl -script ie. the workdflow thinks everything went through ok even though the iwodstart didin't succeed.

This is what we been able to debug so far on Solaris 2.8 and TS 552SP1, OD 551SP2, WFB 5.5.2