Why can't I see EUM license details from the controller's license page?
When viewing the Controller's license page, the user is unable to see the EUM license details.
Troubleshooting when the EUM license details don't appear in the Controller's UI
Start by investigating the Controller's ability to communicate with and register the EUM portion of the license with the EUM Server.
Although the Controller is attempting direct communication with the EUM Server, the Events Service (Analytics Processor) also plays an indirect role in this communication. The EUM Server relies on the Events Service to be running in order to start up. If the Events Service is not running or the EUM Server cannot properly communicate with the Events Service then the EUM Server will eventually fail to start. If the EUM Server fails to start then any connection attempt from the Controller to the EUM Server will likely not succeed.
The bottom line is that all three hosts must be in communication for successful EUM license registration to occur and render EUM licensing information on the Controller's license page.
Pull the relevant log files
In diagnosing a problem like this it is always a good idea to pull all the relevant log files. I've listed the names of each log file is relevant here, and what host it can be found on. On all three hosts, there should be a directory called "logs" which lives inside the home directory for the associated product.
Controller - server.log
Events Service - events-service-api-store.log
EUM Server - eum-processor.log
Example
In this particular case, I was able to find a log entry from the eum-processor.log file which stated there was an error starting the EUM Processor Server. I've highlighted the key elements in the log snippet below which tell us where to begin our investigation:
06 Dec 2016 17:57:34.681 -0800 main AD.ALL ERROR
| Error Starting EUM Processor Server
| java.lang.RuntimeException: java.lang.RuntimeException: bulk update event type=MobileSessionRecord failed!!! url=http://localhost:9080/v2/events/MobileSessionRecord/_bulk, key=MGE1OT...
| {"statusCode":401,"code":"Auth.Unauthorized","message":"The supplied auth information is incorrect or not authorized.","developerMessage":""}
Since the EUM Server failed to start, the EUM host could not listen on TCP port 7001, therefore preventing successful connections from the Controller host.
The other important details in this log entry tell us that, when attempting authorization with the Events Service at the url http://localhost:9080, the supplied auth information is incorrect or not authorized.
Now that we have a starting point, we must configure the correct authorization key for the EUM Server.
Solution
Update the authorization key used by the EUM Server so that it can communicate with the Events Service. Assuming no other issues exist, the EUM Server should be able to start up.
Once we can confirm the EUM Server is started we can then confirm the Controller can properly communicate with and register the EUM license details with the EUM Server.
How do I find the correct authorization key needed for EUM Server/Event Service communication?
The events-service-api-store.properties file in the conf directory of your Events Service installation is where this authorization key is set. In the majority of cases, the authorization key is a randomly generated UUID. The snippet below shows the property where the EUM Server's authorization (access) key is set.
ad.accountmanager.key.eum=c9053630-84e4-4b61-9e49-b092b95c9c95
The example value set for the EUM Server is c9053630-84e4-4b61-9e49-b092b95c9c95. Now that we know the correct key value, we can go to the EUM Server to update the incorrectly set value.
How do I set/update the EUM Server's authorization key?
In the eum.properties file which resides in the bin directory of your EUM Server's installation, there is a section dedicated to setting up the communication between the EUM Server and the Events Service. The property analytics.accountAccessKey is the one we are interested in.
In the sample below, it appears the access key is 1a59d1ac-4c35-4df1-9c5d-5fc191003441, which doesn't match the authorization key c9053630-84e4-4b61-9e49-b092b95c9c95 in the conf directory of the Events Service installation example above.
# Analytics server properties
analytics.accountAccessKey=1a59d1ac-4c35-4df1-9c5d-5fc191003441
Assuming this is the only issue, you can resolve it by updating the analytics.accountAccessKey property in the eum.properties file so that it uses the ad.accountmanager.key.eum property value from the events-service-api-store.properties file. There are a few steps which must take place.
- Update the analytics.accountAccessKey value in the eum.properties file to
c9053630-84e4-4b61-9e49-b092b95c9c95. The results of the above steps should show the eum.properties file with the following values:
# Analytics server properties
analytics.accountAccessKey=c9053630-84e4-4b61-9e49-b092b95c9c95
- Please save the eum.properties file.
- Please attempt to start the EUM Server from the eum-processor directory like so:
bin/eum.sh start &
- We recommend reviewing the latest eum-processor.log file to ensure the EUM Server starts up properly.
- Assuming the EUM Server starts properly we should be able to the correct EUM license details from the Controller's license page
Related Links:
https://docs.appdynamics.com/display/PRO42/Troubleshoot+EUM+Server+Installation
https://docs.appdynamics.com/display/PRO42/Install+a+Split+Host+%28Production%29+EUM+Server
https://docs.appdynamics.com/display/PRO42/Configure+the+EUM+Server
https://docs.appdynamics.com/display/PRO42/Connect+to+the+Events+Service
