Troubleshoot Actors

Articles

Actor did not respond - Windows and Protected Theater Actors
If you are working with your Window Actor and receive an Actor did not respond error, it could be because the services do not start in time. For example, it's possible to see this error if you are trying to run Actions or update the CTTA informati...
Allow Ping for Network Actors
By default, Network Actors are configured not to respond to ICMP packets, such as ping (ICMP echo) requests.  In certain scenarios, you may need to enable ping responses on your Network Actor. This functionality is useful for troubleshooting or for ...
Director IP address changed and now some of the Actor are not working
If your Director's IP address changes, Actors that use Pull Communication mode will have issues working correctly until they know what the new IP address is. You must complete the following steps for each Actor. Network Actors Access the Actor f...
Failure to install a Linux Actor on Red Hat Enterprise Linux 7.x
Issue Installing a Linux Actor fails on some Red Hat Enterprise Linux (RHEL) 7.x systems. Cause The Actor installer attempts to confirm that the epel-release and nginx RPMs are already installed. If these RPMs aren't already in...
Invalid Token Error When Updating the Actor
When trying to update an Actor or refresh its network connection, you may receive an Invalid Token error. There is a 4-step process to resolve this: remove the Actor configuration from the Director, run vreset to revert the Actor to its default st...
Issues Adding Interfaces
The Validation Platform Windows Actor can have separate interfaces for management and testing. These interfaces can only be setup using vregister; you cannot use the Director to edit this information for the Actor. When you run vregister, two thing...
Issues with Action User Profiles
Action User Profile cannot be Selected If there are issues with the Actor's user credential capabilities, you see the error "Actor does not support non-system users" instead of being able to select an Action User Profile. If you check the Actor ...
Operational Status: Actor Tests
This table outlines all Operational Status tests that are available for Actors.  Before any Actor tests begin, a Communications Test is run to verify the Actor and Director can communicate. If the Communications Test fails, no other Actor tests wi...
Restarting and Rebooting Actors
You can restart the Actor service, reboot the Actor, or refresh the Actor information if you made changes to it from the command line. Select Environment > Actors . Locate the Actor you want and then click  Edit . Click one of ...
Reverting Actors to Default State
In certain situations, such as moving an Actor between Directors, Actors may need to be reverted to their default state. This section includes instructions for reverting the Actor. To Revert Actor to Default State Using vreset For Actors, the v...
Resolve Problems during Actor Registration
If you are having issues registering an Actor, there are several tools available to help identify and resolve the issue. These include: Monitor Registration Communication Address Communication Issues during Registration R...
Some Actions will Not Run if Backend Service Doesn't Have Full Disk Access: Operation Not Permitted Error
When using a Mac Actor, some Job Actions will not run if the backend_service doesn't have full disk access. The following example shows the output when a user attempts to make a custom modification to the crontab and it fails with the following per...