Super Contributor.. JamesLindsay Super Contributor..
Super Contributor..
136 views

RAS Execution Log HPEOO 10.7

I'm noticing in my RAS execution log where a flow is calling a local ping operation. The log and the flow  history in Central show the operation completed though, the target host failed the ping. Still the Log is filling up with this error. Why? Is there something I need to fix? Base Content pack 1.10.0

2017-07-27 09:08:07,672 [1_WorkerExecutionThread-30_884003537] (PluginAdapterImpl.java:331) ERROR - java.lang.Exception: E:\Program Files\Hewlett Packard Enterprise\HPE Operations Orchestration\ras\bin>ping  -l 256  -n 2  thishost.net 

Pinging thishost.net [not.thereal.161.51] with 256 bytes of data:
Request timed out.
Request timed out.

Ping statistics for [not.thereal.161.51]:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
 at com.iconclude.content.actions.cmd.BaseCmd.setErrorResults(BaseCmd.java:220)
 at com.iconclude.content.actions.cmd.ping.LocalPing.execute(LocalPing.java:75)
 at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at com.hp.oo.sdk.plugins.abstracts.BaseActionPlugin.execute(BaseActionPlugin.java:53)
 at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at com.hp.oo.maven.PluginAdapterImpl.executePlugin(PluginAdapterImpl.java:328)
 at com.hp.oo.maven.PluginAdapterImpl.execute(PluginAdapterImpl.java:248)
 at com.hp.oo.execution.control.actions.contentexecution.ContentExecutionActions.executeContentAction(ContentExecutionActions.java:97)
 at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at io.cloudslang.worker.execution.reflection.ReflectionAdapterImpl.executeControlAction(ReflectionAdapterImpl.java:62)
 at io.cloudslang.worker.execution.services.ExecutionServiceImpl.executeStep(ExecutionServiceImpl.java:326)
 at io.cloudslang.worker.execution.services.ExecutionServiceImpl.execute(ExecutionServiceImpl.java:80)
 at io.cloudslang.worker.management.services.SimpleExecutionRunnable.executeRegularStep(SimpleExecutionRunnable.java:167)
 at io.cloudslang.worker.management.services.SimpleExecutionRunnable.run(SimpleExecutionRunnable.java:120)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at io.cloudslang.worker.management.services.WorkerThreadFactory$1.run(WorkerThreadFactory.java:33)
 at java.lang.Thread.run(Thread.java:745)

0 Likes
3 Replies
AndreiTruta Outstanding Contributor.
Outstanding Contributor.

Re: RAS Execution Log HPEOO 10.7

Hi,

Do you get this when executing the very same step on another RAS or on the Central Worker?

Andrei Vasile Truta
0 Likes
Super Contributor.. JamesLindsay Super Contributor..
Super Contributor..

Re: RAS Execution Log HPEOO 10.7

I get this in the execution log of every RAS server where it is the worker of a flow execution when the operation is called.

0 Likes
AndreiTruta Outstanding Contributor.
Outstanding Contributor.

Re: RAS Execution Log HPEOO 10.7

please open a ticket around this aspect.

Andrei Vasile Truta
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.