Asset management module execution status stuck in "Waiting".
search cancel

Asset management module execution status stuck in "Waiting".

book

Article ID: 63763

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation

Issue/Introduction

The AM task is always shown in the "Waiting" state and does not run.

Environment

Client Automation - All Versions

Cause

The HW and SW module scheduled to run according to a specified time, for e.g. once a week, displays the status of the Inventory module as "Waiting" with "day of week condition not fulfilled".

This creates an illusion that the module is not running at all and thus the inventory is not collected.

Resolution

Status Update for UNIX:

The above situation is not an error on UNIX and Linux agents. Following are the facts about module execution and status updates on Linux/UNIX machines:

  • Consider that the Inventory module is configured to run once a week.

  • The agent will execute the module for the first time, and then it will not run the concerned module until the conditions are met again.

  • The module is launched only when the scheduling conditions are met (which can be confirmed from the AM agent logs).

  • The status is updated each time the AM agent executes. If scheduling conditions are not met, the status is updated as "Waiting" which indicates that it is waiting until the next execution.

  • The time stamp for module execution remains the same, which specifies the last time the module was executed.

Status Update for Windows:

The windows agents update the status in a different way and preserve the last status. Following are the facts about module execution and status updates on windows agents:

  • Consider that the Inventory module is configured to run once a week.

  • The AM agent will execute, as well as update the status of module execution only when the module is executed as specified in the schedule. If the status is "OK" for the last execution of the module, it will remain "OK" until the module runs the next time.

Owing to the differences in the way UNIX and Windows agents update the execution status, the status of Hardware or Software modules shows as "Waiting" on most of the Unix/Linux machines.

Additional Information

***Note: This situation is applicable to all the Scheduling conditions in general and is not limited to "Once a week condition".