Failed to start schedule: Error checking scheduled events instances

ISSUE

Recently reinstalled UEB Environment using a temporary IP address. When reconfiguring the new VM to use the proper IP address, schedules stopped working.

The following error message is displayed when attempting to start them from the UI:
Failed to start schedule: Error checking scheduled events instances

RESOLUTION

1)  Update the hosts file with the correct IP address by navigating to Configure > Network > Edit Hosts File.

Alternatively, this can also be corrected from the CLI which is accessed through putty.exe.

[[email protected] ~]# cat /etc/hosts
127.0.0.1         localhost.localdomain localhost       vCenter-RRC     Lab
10.1.8.32        Lab-824S.localdomain      Lab-824S
2)  Now, determine whether storage is online by navigating to Configure > Storage and verify the Status.
User-added image
If storage is online, continue to the next step.

If storage is offline, run the following command from the CLI which can be accessed through putty.exe.
psql -c "update bp.storage set is_online='t' where storage_name='Internal'"
Alternatively, this can be accomplished using the unitrends-cli.
To get the values for your storage, run the 
/usr/bp/bin/unitrends-cli get storage
To update storage and return it to an "online" state, run the command as shown below.  Your sid (-s), device id (-i) and storage name (-R) should match the values for your storage shown in the output of the previous command.
Example:
/usr/bp/bin/unitrends-cli put storage -s 1 -i 1 -o -R '{"name":"Internal"}'
3)  Register the Unitrends system client.  (The Unitrends system must be registered as a client to issue certain necessary functions).
update_dpu_client

 

CAUSE

This condition may occur if the system's ip address is changed outside of the UI.  Follow the documented installation instructions to avoid this error.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us