After spinning up a Strategy Azure environment, Telemetry service under Identity stops. Even after starting the service, it returns to a stopped state.
The following error appears in /opt/mstr/PlatformAnalytics/log/platform-analytics-usher-lookup-producer.log:
If you check platform-analytics-usher-lookup-producer.err file in the same location, you may also see the following error:
This issue is an identified defect in the Strategy Azure platform using the provisioning console.
This is due to the wrong UsherServerUser being placed in the PAConsumerConfig.yaml file, which is used to log in to the database where the Usher schema resides. Since the user is incorrect, it is unable to make the connection and, therefore, the service fails to start.
Navigate to your PAConsumerConfig.yaml file, located in opt/mstr/PlatformAnalytics/conf. Scroll to the very end of the file where you have the Usher configuration listed:
Notice that user is listed as mstr. Change the user name to something like mstr@env-xxxx-mysql, where env-xxxx is your environment number. You can also copy the user from the same file listed under platform analytics configuration and paste it.
