Discussion Feed

Question   Can customers use an alias other than "eum-processor" for the EUM server certificate?   Answer   The EUM processor looks for the alias "eum-processor" in the keystore to locate the server certificate for SSL handshake.   Using any other alias for the server certificate will lead to handshake failure as the processor will not be able to locate the proper certificate.    If the server certificate expires and the issuer issues a new certificate, it should be imported with the same alias name as "eum-processor" and not under a new name.   ... View more

Symptoms The installation of the Events Service does not complete and fails with the following error on the command line:    Events Service installation failed. Task: Copying JRE to the remote host failed on host x.x.x.x with message: Failed to upload file: Failed to create remote path   Diagnosis This issue occurs when the user that is specified in the command used to install the Events Service does not have write permission on the destination host.    When the Events Service tries to copy files, it fails as it is unable to create the directory structure and write the files to the destination path.  Solution Provide the write permission to the user on the destination host for the specified path. Then rerun the installation command for the Events Service using Platform Admin.    Related Links: Install Events Service on Linux Install Events Service on Windows Events Service Requirements Prepare the Events Service Host Install the Platform Admin ... View more

Symptoms  The Analytics Agent startup fails with the following error in the Analytics Agent logs:   [2017-06-02T13:09:47,657+02:00]  [ERROR]  [analytics-agent-sync-thread-0]  [c.a.a.agent.sync.ErrorMessageHelper]  Analytics agent failed to connect to the controller registration endpoint. com.appdynamics.analytics.shared.rest.exceptions.ClientException: Could not execute request to https://<controller host>/rest/analytics/agent/register ... ... Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target   Diagnosis The issue occurs when using a self-signed certificate for the Controller.   The Analytics Agent uses a truststore for the JRE to validate the certificate of the connecting server. The truststore does not have self-signed certificates added to the store by default.   Solution Import the client certificate to the JRE truststore, which is located in the Java directory used by the Analytics Agentby default.   Example: JAVA_HOME/lib/security/cacerts   ... View more

Symptoms First, follow the instructions here: How do I symbolicate mobile crash reports?   The dSYM file has been uploaded and the upload has been verified, but the corresponding crash reports do not get symbolicated.   Diagnosis If the dSYM file is incomplete or does not have the necessary debug information, the EUM Server will not be able to symbolicate the crash reports.   Use the "dwarfdump" command to verify that the dSYM file contains debugging information.    Example of output:   $ dwarfdump  86D24-73RC-2B32-ZY70-ABCXYZ.dSYM ----------------------------------------------------------------------  File: 86D24-73RC-2B32-ZY70-ABCXYZ.dSYM (arm64) ---------------------------------------------------------------------- .debug_info contents: < EMPTY >     Solution Check that the dSYM file is complete and contains the necessary debugging information prior to upload. ... View more

Symptoms In the controller UI, iOS crashes are not symbolicated by default. T o get human-readable crash stack traces that can be easily understood, use a platform-specific mapping file that can translate the raw data into human readable output.   iOS users can review the below diagnosis and solution.   For Android, see "Upload the ProGuard Mapping File" in Instrument an Android Application - Manual. Diagnosis iOS crash snapshots can be symbolicated using the  debug symbols (dSYM)  file. The crash snapshots are processed only once by the EUM Server, so if the  dSYM  file is not present  at the time of processing , the  snapshots  will not be symbolicated. Crash report example:    Binary Images: 0xd8000 - 0x12ffff+ECommerce-iOS armv7 <feaae512eb613a75a33dee253fa87bb6> /var/mobile/Containers/Bundle/Application/C64FEBB0-EF8E-4079-BDE0-E35C531F0CA2/ECommerce-iOS.app/ECommerce-iOS     In the above example, the string feaae512eb613a75a33dee253fa87bb6  is the  universally unique identifier ( UUID ) of the application. To symbolicate the crash reports, upload the dSYM file with the corresponding UUID. The dSYM file was generated when the application was built. If you rebuild the application later, it almost always will have a new and different UUID. It is possible to set up your environment to upload the file automatically each time you build. Solution For crash reports to be symbolicated, the corresponding dSYM files need to be uploaded to AppDynamics.   Users can either set up their environment to upload the file automatically each time they build or choose to upload the file manually.   Crashes that have already been processed will not be symbolicated retroactively, but all future reported crashes will be symbolicated.    Note: Crash snapshots are processed only once by the EUM Processor, therefore if the dSYM file is missing during the time of processing the snapshot, it won’t be symbolicated. Even if the user uploads the dSYM file later, the EUM Processor will not retroactively process these snapshots. ... View more