Minor scheduler enhancements (2.7 b213+)

steve · January 24, 2012 9:18AM

The scheduler task allows you to specify a time-out in seconds, but this only takes effect if the "fork" global config option is enabled. This has now been clarified in the interface.

In addition, "Chain" actions now have two new options:

Time-out (seconds): If non-zero, allows you to put a limit on the entire sequence of actions. If the limit is reached, Omniscope will attempt to terminate the action as a failure. This works regardless of the "fork" setting.
Propagate failure: If unticked, failures (including timeouts) are isolated to the chain action. Any enclosing chain actions will continue unaffected. The log will show the failure details.

Using these options and a hierarchy of nested chain actions, you can create any effect you want in terms of time-outs and failure handling.

Please report any issues with this as errors in Omniscope or by commenting below.

benjamin · January 24, 2012 3:50PM

Is this on the wesbite i can only see 2.87 b212 not b213

mustafa · January 24, 2012 6:03PM

The build 213 should be available from the website from Wednesday morning.

benjamin · January 25, 2012 4:38AM

If the chain action timeouts the action does not seem to send an failure email action.

In the scheduler log it appears to indicate it has sent email failure action but it does not.

Also the sechduler task timeout setting this is only for task executed and not a global timeout for any file/chain action which are running on the scheduler , is that correct ?

steve · January 25, 2012 2:24PM

The failure action appears to be working. Here's what I configured; does this work for you (also attached)?

This executes two Chain actions, one inside the other. It uses "Execute command" to echo messages to the console to follow the progress. The nested chain action times out after 2 seconds, so we never see the "nested after" output. Instead we see the "Fail" from the failure action.


<?xml version="1.0" encoding="UTF-8"?>
<schedulerChainAction title="Outer" logTimings="false" 
    timeOut="0" propagateFailure="true">
  <actions>
    <schedulerExecAction 
        command="cmd /c echo &quot;outer before&quot;" 
        waitUntilTerminated="true" ignoreError="false" />
    <schedulerChainAction 
        title="Nested" logTimings="false" timeOut="2" 
        propagateFailure="false">
      <actions>
        <schedulerExecAction 
            command="cmd /c echo &quot;nested before&quot;"
            waitUntilTerminated="true" ignoreError="false" />
        <schedulerExecAction 
            command="cmd /c sleep 3" 
            waitUntilTerminated="true" ignoreError="false" />
        <schedulerExecAction 
            command="cmd /c echo &quot;nested after&quot;" 
            waitUntilTerminated="true" ignoreError="false" />
      </actions>
      <failureAction>
        <schedulerExecAction 
            command="cmd /c echo &quot;Fail&quot;" 
            waitUntilTerminated="true" ignoreError="false" />
      </failureAction>
    </schedulerChainAction>
    <schedulerExecAction 
        command="cmd /c echo &quot;outer after&quot;" 
        waitUntilTerminated="true" ignoreError="false" />
  </actions>
</schedulerChainAction>

Log on test action (fits with what I was expecting):


ERRORS/WARNINGS: 
Chain action "Nested" failure due to timeout   

MESSAGES: 
"outer before" 
Executed process: cmd /c echo "outer before" 
"nested before" 
Executed process: cmd /c echo "nested before" 
Executing chain action "Nested" failure action 
"Fail" 
Executed process: cmd /c echo "Fail" 
"outer after" 
Executed process: cmd /c echo "outer after" 
Executed chain: "Outer"

steve · January 25, 2012 2:25PM

(tested using Settings > Server > Edit action descriptor, then choosing to test on press OK)

Welcome!

Categories

Ideas Parade