If the enterprise nodes are giving following errors under logs:
"CPS Status: The token was invalid for the given Synthetic-Node, likely because the token data wasn't in cache, no tokens assigned for the machine or the token is not assigned to the machine."
Please follow the below steps:
Clear the token values.xml file-
Stop catchpoint service
> rm /opt/3genlabs/registry/LocalMachine/software/3genlabs/hawk/syntheticnode/service/\*
> rm /opt/3genlabs/registry/LocalMachine/software/3genlabs/security/mostrecentschedulertoken/\*
Start catchpoint service.
If still the token issue not resolved-
Stop the service again; and remove the entire registry folder and restart Catchpoint services. > rm -rf /var/3genlabs/registry
OR
1 - Stop catchpoint.
2 - Delete /var/3genlabs/hawk/syntheticnode/synthetic_node_configuration.dat\*
3 - Delete /var/CatchPoint/Agent/Services/CommEng/Cache/\*
4 - Start the node
You can flush the token using below:
http://s.3gl.net/hawkscheduleserver/monitorservice.svc/web/query?name=synthetic-location¶meters=mrum=<hostname>|flush_machine=1