Hardware Sentry KM: Some OS Commands Fail and Return no Result

  • kb1151
  • Aug. 6, 2014
  • 1 min read

What to do when OS Commands time out and return no results.

Problem Hardware Sentry OS Commands

Related Topics

Description

Because the default timeout for OS Commands is set to 30 seconds, any command that require more time to return a result will produce the following error:

Description: OSCOMMAND TEST on localhost: FAILED
--------------------------
The following command-line failed to match the criteria:
- CommandLine = /usr/bin/iostat -En
- ExpectedResult = Soft [Ee]rrors.*Hard [Ee]rrors.*Transport [Ee]rrors

Actual result (see below):

This issue can simply be solved by increasing the value of the defaultCommandTimeout configuration variable.

Procedure

To modify the value of the defaultCommandTimeout variable:

  1. Run wpconfig.exe
  2. Click inline to get the configuration of your PATROL Agent
  3. Go to the Edit menu and select Add Variable

    4. inline

  4. In the Variable field, enter: /SENTRY/HARDWARE/defaultCommandTimeout
  5. In the Value field, specify the time in seconds after which the OS commands will time out (in our example 300 seconds)
  6. Click Add.
  7. Click inline to apply your changes to the PATROL Agent’s configuration.
  8. Restart the PATROL Agent.
Problem Hardware Sentry OS Commands