Controls stuck in -1 status stay in -1 status after a restart

Sometimes, Infogix will suggest a customer to perform a restart of Assure to resolve an issue where a control is stuck in the "-1" status and it needs to be stopped. After the restart, the expectation is that the control will update its status to be "16" (which means that it failed). However, due to the way the control was stopped (Assure restarting), the control will remain in the "-1" status. This does not mean the control is still running. After a restart, all controls are forcibly stopped, so it will no longer be running despite the status showing "-1".

If you wish to remove these "-1" statuses, you can use the "closeCatalogs" server-utility script to move these executions to RC=16. This script is available in Assure 8.5 and newer.

Here's an example of how to use it:

./closeCatalogs -catalogs 1003

The number you'd enter after -catalogs is the "Catalog ID" found in Results by Control Point.