Discussion Feed

Issue This issue is happening when the host's /tmp directory is noexec and the Events Service is not starting, throwing the following error: [2018-07-13T14:18:55,672+02:00]  [ERROR]  [main]  [c.a.common.framework.AbstractApp]  Severe error occurred while starting application [events-service-api-store]. Shutdown procedure will commence soon java.lang.UnsatisfiedLinkError: /tmp/jna-3506402/jna1770418019150735408.tmp: /tmp/jna-3506402/jna1770418019150735408.tmp: failed to map segment from shared object: Operation not permitted   Solution The solution is to add one of the options below to the events-service.vmoptions prior to initiating startup:   -Djna.tmpdir=/new/tmp/location OR -Djava.io.tmpdir=/new/tmp/location   Try running the Events Service manually after this change using the command line to resolve this issue: <events-service-home>/bin> events-service.sh  start -p <path_to_events-service-api-store.properties file> ... View more

The Mobile app uses the same settings as the Controller. The timeouts mentioned below are the defaults:  http.session.inactive.timeout: The amount of time without a client request to the Controller after which the user session times out and the user will need to log in again to continue. The default is 3600 seconds (60 minutes). ui.inactivity.timeout: The amount of time without user activity in the Controller UI after which the user session times out and the user will need to log in again to continue. The default is -1 (disabled).   These values can be modified after logging in to the Administration Console. ... View more

We complete the actual data purge by deleting entire indices once all records have expired. For example,  an index will rollover either when the average shard size breaches a threshold or when the age of the index exceeds the data retention period for the account/event type. We will wait until all documents in the index have expired, then delete the entire index.   Sometimes, the index doesn't rollover itself. In those cases, you can follow the instructions below to roll it over.   1. Use the rollover index API call:   http://<host:9080>/v1/admin/cluster/{cluster}/index/{index}/rollover   2. Complete the request with headers:   curl -XPOST  http://<host:9080>/v1/admin/cluster/{cluster}/index/{index}/rollover -H"Authorization: Basic <Base64 encoded ad.accountmanager.key.controller from events-service-api-store.properties>" -H"Content-Type: application/json" -H"Accept: application/json"   3. Once the command is successfully executed, verify  it using the output of the following:   curl http://localhost:9200/_cat/indices?v   4. Later, once the retention period setting comes into effect and all documents in the old index become expired, the entire index will be deleted. ... View more

Issue While starting the Events Service, it fails to start up due to following error stack trace:   [ERROR]  [ProcessQueue0]  [c.a.a.p.e.e.ElasticSearchExecutor]  This message was throttled [1] times: java.security.AccessControlException: access denied ( "java.lang.RuntimePermission" "getClassLoader") [ERROR]  [ProcessQueue0]  [c.a.a.p.e.e.ElasticSearchExecutor]  java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "getClassLoader") [ERROR]  [ProcessQueue0]  [c.a.a.p.e.e.ElasticSearchExecutor]      at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472) [ERROR]  [ProcessQueue0]  [c.a.a.p.e.e.ElasticSearchExecutor]   Solution To resolve this issue, the classloader whitelist can be customised by tweaking the local Java Security Policy. This can be done: system wide:   $JAVA_HOME/lib/security/java.policy , for just the   elasticsearch   user:   /home/elasticsearch/.java.policy , or from a file specified in the   JAVA_OPTS   environment variable with   -Djava.security.policy=someURL : export JAVA_OPTS = " $ { JAVA_OPTS } - Djava . security . policy = file : ///path/to/my.policy` ./ bin / elasticsearch     Once this is complete, this error should be resolved.   Reference: https://www.elastic.co/guide/en/elasticsearch/reference/2.2/modules-scripting-security.html ... View more

Question How often does the data purge activity occur for EUM resource snapshots when the retention policy configuration is set? Answer For the on-premise EUM Processor, the expiration check happens once every hour.   The data purge that occurs as part of the retention policy also happens with every check. This is due to the fact that if we were to only check once every day, our retention policy of 15 days may become 16 days, which is undesirable. ... View more

Question Is it possible to set up multiple Synthetic Private Agents on the same server?   Answer As per the current model, if you install multiple Synthetic Private Agents tagged under same ID on same machine, it won't work properly since we need to take screenshots of sessions from browsers on the machine. If two agents are running on same machine, it won't give expected results. The solution to this would be set multiple Private Agent machines and tag them all under same name and ID for the Private Agent. They will form a cluster on their own in this way and you can then execute multiple jobs without any issues. ... View more

Issue While creating an EUM app in an on-premise Controller, it fails with the error   "internal server error. See server.log"   The Controller UI gives the same error when tried with  "Create an Application manually" or "Create an Application using the Getting Started Wizard."  This error is even seen when both EUM and Events Service are up.   Diagnosis When checking the Controller's server.log for the same timeframe, it seems like EUM Processor is not reachable from the browser where the Controller UI is accessed to create this EUM app:   Communication failure with service (http://<EUM-HOST>:7001/v2/application/EUM-AAB-AUB/resource-timing): Unexpected HTTP error 500: {"code":500,"message":"There was an error processing your request. It has been logged (ID ecac6f5d92fddeb5)."}|#]   To further validate this, gather the output (o/p) of the following URL from the same browser where this error is seen inside the Controller UI:   http://<EUM-HOST>7001/eumcollector/get-version This would fail as from the same browser the EUM is not reachable.   Solution While creating an EUM app from the Controller UI, the browser validates the communication to the EUM Processor. To resolve this issue, grant  access to the EUM Processor (TCP/7001) from the web browser.   Once this is done, you should be able to create an EUM app successfully.   Note: 7001 is default HTTP port for eum processor. ... View more