AppD Archive

Can not enable EUM on trial mode

CommunityUser
Splunk Employee
Splunk Employee

Hi

according to attached screenshots the EUM cant be enabled on on-premise installation model.

any adwise would be highly appreciated

[#|2015-11-01T10:41:07.501+0330|WARNING|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.web.security|_ThreadID=57;_ThreadName=Thread-5;|WEB9102: Web Login Failed: com.sun.enterprise.security.auth.login.common.LoginException: Login failed: Cannot authenticate user : singularity-agent@customer1|#]

[#|2015-11-01T10:41:14.367+0330|WARNING|glassfish3.1.2|com.singularity.ee.controller.auth.AuthRealm|_ThreadID=57;_ThreadName=Thread-5;|Failed authenticating user : 5|#]

[#|2015-11-01T10:41:14.368+0330|WARNING|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.web.security|_ThreadID=57;_ThreadName=Thread-5;|WEB9102: Web Login Failed: com.sun.enterprise.security.auth.login.common.LoginException: Login failed: Cannot authenticate user : singularity-agent@customer1|#]

[#|2015-11-01T10:41:15.025+0330|INFO|glassfish3.1.2|com.singularity.ee.controller.beans.agent.db.MetricMemoryDataStore|_ThreadID=149;_ThreadName=Thread-5;|Verification started for Sun Nov 01 10:34:00 IRST 2015|#]

[#|2015-11-01T10:41:15.045+0330|INFO|glassfish3.1.2|com.singularity.ee.controller.beans.agent.db.MetricMemoryDataStore|_ThreadID=149;_ThreadName=Thread-5;|Verification finished. VerifyResult{verifiedCount=908, rowsCount=4100, errorCount=0}|#]

[#|2015-11-01T10:41:18.337+0330|INFO|glassfish3.1.2|com.singularity.ee.controller.beans.model.ApplicationManagerBean|_ThreadID=59;_ThreadName=Thread-5;|For App[Modiseh] EUM Enabled Status updated from [true] to [false]|#]

[#|2015-11-01T10:41:18.889+0330|INFO|glassfish3.1.2|com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean|_ThreadID=59;_ThreadName=Thread-5;|EUM Cloud Registration state invalidated for application 5. This will trigger a cloud registration request|#]

[#|2015-11-01T10:41:20.090+0330|INFO|glassfish3.1.2|com.singularity.ee.controller.beans.model.ApplicationManagerBean|_ThreadID=63;_ThreadName=Thread-5;|For App[Modiseh] EUM Enabled Status updated from [false] to [true]|#]

[#|2015-11-01T10:42:07.927+0330|INFO|glassfish3.1.2|com.singularity.ee.controller.beans.eumcloud.EUMCloudRegistrationManager|_ThreadID=139;_ThreadName=Thread-5;|Aborting EUM registration for application 5, [ Modiseh], account 201650-ss-gbg-2xyu5dqeeowt, not enabled for EUM|#]

[#|2015-11-01T10:42:07.927+0330|INFO|glassfish3.1.2|com.singularity.ee.controller.beans.eumcloud.EUMCloudRegistrationManager|_ThreadID=139;_ThreadName=Thread-5;|EUM Cloud registration performed for application 5, current state : null|#]

[#|2015-11-01T10:42:14.393+0330|WARNING|glassfish3.1.2|com.singularity.ee.controller.auth.AuthRealm|_ThreadID=60;_ThreadName=Thread-5;|Failed authenticating user : 5|#]

[#|2015-11

 on

0 Karma

Arun_Dasetty
Super Champion

Hi ,

Can you validate the EUM related jvm args in domain.xml once as referred in doc section:

https://docs.appdynamics.com/display/PRO39/Install+the+On-Premise+End+User+Experience+Management+Pro...

Also send the recent 2-3 server.log once? we understood that you are trying to use EUM AWS Cloud instead onPremise eum processor from your comments and logs, let us know if any disconnect here

CommunityUser
Splunk Employee
Splunk Employee

Thanks Kumar , it resolved the problem 95%  :slightly_smiling_face:

now i faced to another error regarding to analysis service location

the appdynamics.controller.eum.analytics.service.hostName  was pointing to internet but after changing it to internal server  , again i faced to error :

Invalid analytics configuration, or analytics processor not running: Could not execute request to https://appdynamics.gbgnetwork.net:443/v2/events/BrowserRecord/search

thanks for your advices

]|#]

[#|2015-11-03T12:03:54.902+0330|INFO|glassfish3.1.2|com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean|_ThreadID=155;_ThreadName=Thread-5;|Posted EUM Internal Error Event [Agent Event Type[EUM_INTERNAL_ERROR]
Occurred at Time[1446539634901]
Summary[EUM Internal Errors]
Severity[ERROR]
Event Details[{com.singularity.ee.controller.beans.eumcloud.RESTCommunicationException|FailedToSyncEumCloudLicenseForAccount=RESTCommunicationException: org.apache.http.conn.HttpHostConnectException: Connect to Appdynamics.gbgnetwork.net:7001 [Appdynamics.gbgnetwork.net/172.20.21.23, Appdynamics.gbgnetwork.net/0:0:0:0:0:0:0:1] failed: Connection refused: connect while calling 'http://Appdynamics.gbgnetwork.net:7001/eumaggregator/provision-license'::Failed to sync EUM Cloud License with cloud for account [customer1], eum_account_name [201650-ss-gbg-2xyu5dqeeowt]
, com.singularity.ee.controller.beans.eumcloud.RESTCommunicationException|RegistrationError=RESTCommunicationException: org.apache.http.conn.HttpHostConnectException: Connect to Appdynamics.gbgnetwork.net:7001 [Appdynamics.gbgnetwork.net/172.20.21.23, Appdynamics.gbgnetwork.net/0:0:0:0:0:0:0:1] failed: Connection refused: connect while calling 'http://Appdynamics.gbgnetwork.net:7001/eumaggregator/register-app'::Failed to complete registration, response=null, request=com.appdynamics.eumcloud.registration.dto.EUMCloudRequestApplicationRegistration@3dcc1864
}]
Error IDs[[]]
Correlation Map[{}]
EventProperties[null]
]|#]

[#|2015-11-03T12:03:54.981+0330|INFO|glassfish3.1.2|com.appdynamics.RULES.PROCESSING|_ThreadID=160;_ThreadName=Thread-5;|Running HR processor, checking HR cache|#]

[#|2015-11-03T12:03:54.982+0330|INFO|glassfish3.1.2|com.appdynamics.RULES.PROCESSING|_ThreadID=160;_ThreadName=Thread-5;|Running HR processor, cache loaded|#]

[#|2015-11-03T12:04:15.015+0330|INFO|glassfish3.1.2|com.singularity.ee.controller.beans.agent.db.MetricMemoryDataStore|_ThreadID=155;_ThreadName=Thread-5;|Verification started for Tue Nov 03 11:57:00 IRST 2015|#]

[#|2015-11-03T12:04:15.042+0330|INFO|glassfish3.1.2|com.singularity.ee.controller.beans.agent.db.MetricMemoryDataStore|_ThreadID=155;_ThreadName=Thread-5;|Verification finished. VerifyResult{verifiedCount=492, rowsCount=1432, errorCount=0}|#]

[#|2015-11-03T12:04:22.614+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|Event Data Query Optimization Value : true|#]

[#|2015-11-03T12:04:22.616+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|Number of Rows requested in query = [600]|#]

[#|2015-11-03T12:04:22.617+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|Time Bucketing for EventData Affected Query : [false]|#]

[#|2015-11-03T12:04:22.617+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|Processing Bucket for EventData Affected Query: StartTime = [1446538762615] EndTime = [1446539662615]|#]

[#|2015-11-03T12:04:22.631+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|Query_Loop counter = [0] Number of rows retrieved in current loop : [0]|#]

[#|2015-11-03T12:04:22.632+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|EventData Affected Query Total Number of Rows retrieved = [0]|#]

[#|2015-11-03T12:04:22.652+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|Event Data Query Optimization Value : true|#]

[#|2015-11-03T12:04:22.653+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|Number of Rows requested in query = [600]|#]

[#|2015-11-03T12:04:22.654+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|Time Bucketing for EventData Affected Query : [false]|#]

[#|2015-11-03T12:04:22.654+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|Processing Bucket for EventData Affected Query: StartTime = [1446538762615] EndTime = [1446539662615]|#]

[#|2015-11-03T12:04:22.661+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|Query_Loop counter = [0] Number of rows retrieved in current loop : [0]|#]

[#|2015-11-03T12:04:22.662+0330|INFO|glassfish3.1.2|com.appdynamics.EVENTS.READ|_ThreadID=58;_ThreadName=Thread-5;|EventData Affected Query Total Number of Rows retrieved = [0]|#]

[#|2015-11-03T12:04:23.238+0330|SEVERE|glassfish3.1.2|com.singularity.ee.controller.ui.services.eum.web.WebAnalyzeUiService|_ThreadID=53;_ThreadName=Thread-5;|ClientException caused by IOException caught while executing analytics query; invalid/unset analytics configuration / or analytics processor not running|#]

[#|2015-11-03T12:04:24.099+0330|SEVERE|glassfish3.1.2|com.singularity.ee.controller.ui.services.eum.web.WebAnalyzeUiService|_ThreadID=56;_ThreadName=Thread-5;|ClientException caused by IOException caught while executing analytics query; invalid/unset analytics configuration / or analytics processor not running|#]

0 Karma

Arun_Dasetty
Super Champion

Hi,

Can you check behavior post trying below changes:

- add port 443 in your case for below similar jvm args:

<jvm-options>-Dappdynamics.controller.eum.analytics.service.hostName=localhost:9080</jvm-options>

above change requires controller ui jvm process restart

- is the events service jvm is running? if not issue below and check error again in UI after re-login Controller

shell> cd <Controller_install_dir>/bin

shell> controller.sh/bat stop-events-service

shell> controller.sh/bat start-events-service

Also from logs, it looks eum processor jvm is not running on port 7001, check once again that eum process jvm is running on port 7001:

Connection refused: connect while calling 'http://Appdynamics.gbgnetwork.net:7001/eumaggregator/register-app'

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Kumar

 i addedd 443 for  Dappdynamics.controller.eum.analytics.service.hostName

also server log and some screenshots attached ,still there is a problem i think

Thanks

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...