Hardware Sentry KM: Some OS Commands Fail and Return no Result
KB1151 - Aug 06, 2014
Type: Problem
Description: This article explains the procedure to follow when OS Commands time out and return no results.
Additional Keywords: Hardware Sentry, OS Commands
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
This issue can simply be solved by increasing the value of the defaultCommandTimeout configuration variable.
Procedure
To modify the value of the defaultCommandTimeout variable:
- Run wpconfig.exe
- Click
to get the configuration of your PATROL Agent
- Go to the Edit menu and select Add Variable
- In the Variable field, enter: /SENTRY/HARDWARE/defaultCommandTimeout
- In the Value field, specify the time in seconds after which the OS commands will time out (in our example 300 seconds)
- Click Add.
- Click
to apply your changes to the PATROL Agent’s configuration.
- Restart the PATROL Agent.