AppScan Issue

Hi Ghoti,

I incluede one ipl file which is having code to scan files using AppScan.

When im running that ipl saperately it's working fine.

When im running the same ipl in a workflow,
Im getting following error as
" segmentation fault "${BINDIRECTORY}/cliloader" "$@ 2> /dev/null

I serched in the forums, Then i found solution what you gave for this issue.
The following is the link for that thread:
http://devnet.interwoven.com/forums_vb/showthread.php?p=178151&mode=linear&highlight=Appscan#post178151

I set environemnt variable as you said.
Even then it is wworking for one workflow.
When im using the sam ipl for other workflow it is not working.

Please give me suggestion for this issue.

Thanks

Find more posts tagged with

Comments

Adam Stoller

Hi Ghoti,

I incluede one ipl file which is having code to scan files using AppScan.

When im running that ipl saperately it's working fine.

When im running the same ipl in a workflow,
Im getting following error as
" segmentation fault "${BINDIRECTORY}/cliloader" "$@ 2> /dev/null

I serched in the forums, Then i found solution what you gave for this issue.
The following is the link for that thread:
http://devnet.interwoven.com/forums_vb/showthread.php?p=178151&mode=linear&highlight=Appscan#post178151

I set environemnt variable as you said.
Even then it is wworking for one workflow.
When im using the sam ipl for other workflow it is not working.

Please give me suggestion for this issue.

Thanks

Wow - a thread that starts out assuming that I'll be reading it (not too far-fetched I guess, but still a bit strange)

The fact that the error message literally shows "${BINDIRECTORY}" and "$@" would to me be an indication that the variable wasn't defined or properly interpolated, which would make me wonder how it works anywhere.

Without seeing the actual code, and potentially be able to actually see it working (or not working) in situ makes it difficult to figure out what to suggest other than that you need to do a bit more debugging on your own since you have the code and the environment in which to run it.

Put more debugging statements in the code, try to narrow down the focus of where the problem is occurring, etc.

srilu

Hi Ghoti,

I gone through previous threads, There you seggested to set ENVIRONMENT variables.

I set those ENVIRONMENT variables,
Then it is working fine for one workflow.

I used same .ipl file for another workflow, Then i am getting same error as "Segmentation fault "${BINDIRECTORY}/cliloader" "$@ 2> /dev/null

I tried without setting ENVIRONMENT variables also, Then also getting same error.

I set ENVIRONMENT variables as
$ENV{variable-name}="variable-value";

Please give me suggestion to this issue.

Thanks

Adam Stoller

Hi Ghoti,

I gone through previous threads, There you seggested to set ENVIRONMENT variables.

I set those ENVIRONMENT variables,
Then it is working fine for one workflow.

I used same .ipl file for another workflow, Then i am getting same error as "Segmentation fault "${BINDIRECTORY}/cliloader" "$@ 2> /dev/null

I tried without setting ENVIRONMENT variables also, Then also getting same error.

I set ENVIRONMENT variables as
$ENV{variable-name}="variable-value";

Please give me suggestion to this issue.

Thanks

Are you running cliloader directly from your script - or are you running something else that in turn runs cliloader ?

You need to narrow down the line in your source that results in the segmentation fault being thrown and then continue to debug from there.

Since I don't have your code nor the ability to run it in your environment - that's about all I can suggest.