Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Server Automation10.60

Use > Software management > Remediate and installing software > Timeout handling for installation or uninstallation and remediation jobs

Timeout handling for remediation and installation jobs

A timeout can occur during a software remediation or installation job. When this happens the job execution stops to prevent further changes to the server.

The error handling option set for the job (see Step 2 (Optional) - Specify reboot, error handling, and script options for remediation) does not apply to timeouts. A timeout, unlike a general error, describes a situation where the job had been running successfully until a specified time interval passed. This is not considered an error, and the job does not attempt to run the remaining phases irrespective of the above flag.

Execution exceeds maximum defined duration

The main reason remediation and installation jobs time out is, when processing a job phase or job item exceeds the maximum defined duration for the specific phase or item (Example: package, script or patch).

These timeout values can be adjusted in the Command Engine section of System Configuration (for more information contact your HPE Server Automation Administrator).

When encountering this type of timeout, the job attempts to stop as soon as possible. This behavior depends on phase active when the timeout occurred:

Analyze: the analyze phase gets completed, but the next phases will not be started
Download: the download stops after the current package is downloaded. Pending packages will not be downloaded and the next phases will not be started.
Action: the installation that is currently running will complete but no remaining items will be processed.

After the timeout occurs and until the job execution stops, the status of the server will be changed to Stopping. After the job execution stops the server will be marked as Timed Out.

Communication problems between the agent and the core

An SA core considers a job as timed out, if communication problems prevent it from reaching the agent during job execution.

Timeouts and server reboots

When a timeout is detected during the Action phase the job prevents the server reboots requested by the packages imported into SA.

If the timeout occurs during a reboot, then after restarting, the agent will not continue with the job. This addresses the situation when servers stay offline for a long time before managing to start again.

Send Help Center feedback