Attachment 1339962 Details for Bug 1500464 – hawkular-metrics pod log

hawkular-metrics pod log

hawkular-metrics.txt (text/plain), 72.11 KB, created by Junqi Zhao on 2017-10-18 02:48:14 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Junqi Zhao

Created: 2017-10-18 02:48:14 UTC

Size: 72.11 KB

patch

obsolete

>2017-10-18 01:10:59 Starting Hawkular Metrics
>The service account has read permissions for its project. Proceeding
> 
>================================================================================
>                                WARNING                                         
>================================================================================
>  The service account for Hawkular Metrics does not have permission to watch
>  namespaces. Without this permission Hawkular Metrics may not function
>  properly.
>  
>  Installing metrics with a newer version of openshift-ansible should automatically
>  create the required roles and add this role to the 'hawkular' user.
> 
>  Alternatively, you can also manually do this by running the following commands: 
> 
>  oc create clusterrole hawkular-metrics --verb=get,list,watch --resource=namespaces
> 
>  oc adm policy add-cluster-role-to-user hawkular-metrics system:serviceaccount:openshift-infra:hawkular -n openshift-infra
> 
>================================================================================
> 
>/opt/hawkular/auth ~
>Splitting up the Kubernetes CA into individual certificates
>Adding the Kubernetes CAs into the trust store
>Picked up JAVA_TOOL_OPTIONS: -Duser.home=/home/jboss -Duser.name=jboss
>Certificate was added to keystore
>~
>=========================================================================
>  JBoss Bootstrap Environment
>  JBOSS_HOME: /opt/eap
>  JAVA: /usr/lib/jvm/java-1.8.0/bin/java
>  JAVA_OPTS:  -server -verbose:gc -Xloggc:"/opt/eap/standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1192m -Xmx1192m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.logmanager,jdk.nashorn.api -Djava.awt.headless=true -Xbootclasspath/p:/opt/eap/jboss-modules.jar:/opt/eap/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.3.Final-redhat-1.jar:/opt/eap/modules/system/layers/base/org/jboss/logmanager/ext/main/jboss-logmanager-ext-1.0.0.Alpha2-redhat-1.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager -javaagent:/opt/eap/jolokia.jar=port=8778,protocol=https,caCert=/var/run/secrets/kubernetes.io/serviceaccount/ca.crt,clientPrincipal=cn=system:master-proxy,useSslClientAuthentication=true,extraClientCheck=true,host=0.0.0.0,discoveryEnabled=false -Djava.security.egd=file:/dev/./urandom -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/heapdump
>=========================================================================
>Picked up JAVA_TOOL_OPTIONS: -Duser.home=/home/jboss -Duser.name=jboss
>Could not start Jolokia agent: java.lang.IllegalStateException: Cannot use keystore for https communication: java.security.cert.CertificateException: Could not parse certificate: java.io.IOException: Illegal header: -----BEGIN CERTIFICATE-----  
>[0m2017-10-18 01:11:01,331 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.3.Final-redhat-1
>[0m[0m2017-10-18 01:11:01,687 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1-redhat-1
>[0m[0m2017-10-18 01:11:01,777 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.0.6.GA (WildFly Core 2.1.15.Final-redhat-1) starting
>[0m[32m2017-10-18 01:11:01,779 DEBUG [org.jboss.as.config] (MSC service thread 1-7) Configured system properties:
>	DISABLE_NAMESPACE_FILTER = true
>	KUBERNETES_MASTER_URL = https://kubernetes.default.svc
>	USER_WRITE_ACCESS = False
>	[Standalone] = 
>	awt.toolkit = sun.awt.X11.XToolkit
>	com.datastax.driver.FORCE_NIO = true
>	file.encoding = ANSI_X3.4-1968
>	file.encoding.pkg = sun.io
>	file.separator = /
>	hawkular-alerts.cassandra-nodes = hawkular-cassandra
>	hawkular-alerts.cassandra-use-ssl = true
>	hawkular.alerts.allowed-cors-access-control-allow-headers = authorization
>	hawkular.alerts.openshift.auth-methods = openshift-oauth,htpasswd
>	hawkular.alerts.openshift.htpasswd-file = /secrets/hawkular-metrics.htpasswd.file
>	hawkular.metrics.admin-tenant = _hawkular_admin
>	hawkular.metrics.allowed-cors-access-control-allow-headers = authorization
>	hawkular.metrics.cassandra.nodes = hawkular-cassandra
>	hawkular.metrics.cassandra.use-ssl = true
>	hawkular.metrics.default-ttl = 7
>	hawkular.metrics.openshift.auth-methods = openshift-oauth,htpasswd
>	hawkular.metrics.openshift.htpasswd-file = /secrets/hawkular-metrics.htpasswd.file
>	java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
>	java.awt.headless = true
>	java.awt.printerjob = sun.print.PSPrinterJob
>	java.class.path = /opt/eap/jboss-modules.jar:/opt/eap/jolokia.jar
>	java.class.version = 52.0
>	java.endorsed.dirs = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/endorsed
>	java.ext.dirs = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
>	java.home = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre
>	java.io.tmpdir = /tmp
>	java.library.path = /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
>	java.net.preferIPv4Stack = true
>	java.runtime.name = OpenJDK Runtime Environment
>	java.runtime.version = 1.8.0_144-b01
>	java.security.egd = file:/dev/./urandom
>	java.specification.name = Java Platform API Specification
>	java.specification.vendor = Oracle Corporation
>	java.specification.version = 1.8
>	java.util.logging.manager = org.jboss.logmanager.LogManager
>	java.vendor = Oracle Corporation
>	java.vendor.url = http://java.oracle.com/
>	java.vendor.url.bug = http://bugreport.sun.com/bugreport/
>	java.version = 1.8.0_144
>	java.vm.info = mixed mode
>	java.vm.name = OpenJDK 64-Bit Server VM
>	java.vm.specification.name = Java Virtual Machine Specification
>	java.vm.specification.vendor = Oracle Corporation
>	java.vm.specification.version = 1.8
>	java.vm.vendor = Oracle Corporation
>	java.vm.version = 25.144-b01
>	javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
>	javax.net.ssl.keyStore = /opt/hawkular/auth/hawkular-metrics.keystore
>	javax.net.ssl.keyStorePassword = <redacted>
>	javax.net.ssl.trustStore = /opt/hawkular/auth/hawkular-metrics.truststore
>	javax.net.ssl.trustStorePassword = <redacted>
>	javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
>	javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
>	javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
>	javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
>	javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
>	javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
>	javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
>	javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
>	javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
>	jboss.bind.address = 0.0.0.0
>	jboss.bind.address.private = 10.128.0.51
>	jboss.home.dir = /opt/eap
>	jboss.host.name = hawkular-metrics-vdllm
>	jboss.modules.dir = /opt/eap/modules
>	jboss.modules.system.pkgs = org.jboss.logmanager,jdk.nashorn.api
>	jboss.node.name = hawkular-metrics-vdllm
>	jboss.qualified.host.name = hawkular-metrics-vdllm
>	jboss.server.base.dir = /opt/eap/standalone
>	jboss.server.config.dir = /opt/eap/standalone/configuration
>	jboss.server.data.dir = /opt/eap/standalone/data
>	jboss.server.deploy.dir = /opt/eap/standalone/data/content
>	jboss.server.log.dir = /opt/eap/standalone/log
>	jboss.server.name = hawkular-metrics-vdllm
>	jboss.server.persist.config = true
>	jboss.server.temp.dir = /opt/eap/standalone/tmp
>	line.separator = 
>	logging.configuration = file:/opt/eap/standalone/configuration/logging.properties
>	module.path = /opt/eap/modules
>	org.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH = true
>	org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH = true
>	org.jboss.boot.log.file = /opt/eap/standalone/log/server.log
>	org.jboss.resolver.warning = true
>	org.xml.sax.driver = __redirected.__XMLReaderFactory
>	os.arch = amd64
>	os.name = Linux
>	os.version = 3.10.0-693.el7.x86_64
>	path.separator = :
>	sun.arch.data.model = 64
>	sun.boot.class.path = /opt/eap/jboss-modules.jar:/opt/eap/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.3.Final-redhat-1.jar:/opt/eap/modules/system/layers/base/org/jboss/logmanager/ext/main/jboss-logmanager-ext-1.0.0.Alpha2-redhat-1.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/classes
>	sun.boot.library.path = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/amd64
>	sun.cpu.endian = little
>	sun.cpu.isalist = 
>	sun.io.unicode.encoding = UnicodeLittle
>	sun.java.command = /opt/eap/jboss-modules.jar -mp /opt/eap/modules org.jboss.as.standalone -Djboss.home.dir=/opt/eap -Djboss.server.base.dir=/opt/eap/standalone -Djavax.net.ssl.keyStore=/opt/hawkular/auth/hawkular-metrics.keystore -Djavax.net.ssl.trustStore=/opt/hawkular/auth/hawkular-metrics.truststore -Djboss.node.name=hawkular-metrics-vdllm -b 10.128.0.51 -bprivate 10.128.0.51 -P /opt/hawkular/server.properties -DDISABLE_NAMESPACE_FILTER=true -b 0.0.0.0 -Dhawkular.metrics.cassandra.nodes=hawkular-cassandra -Dhawkular.metrics.cassandra.use-ssl -Dhawkular.metrics.openshift.auth-methods=openshift-oauth,htpasswd -Dhawkular.metrics.openshift.htpasswd-file=/secrets/hawkular-metrics.htpasswd.file -Dhawkular.metrics.allowed-cors-access-control-allow-headers=authorization -Dhawkular.metrics.default-ttl=7 -Dhawkular.metrics.admin-tenant=_hawkular_admin -Dhawkular-alerts.cassandra-nodes=hawkular-cassandra -Dhawkular-alerts.cassandra-use-ssl -Dhawkular.alerts.openshift.auth-methods=openshift-oauth,htpasswd -Dhawkular.alerts.openshift.htpasswd-file=/secrets/hawkular-metrics.htpasswd.file -Dhawkular.alerts.allowed-cors-access-control-allow-headers=authorization -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true -Dorg.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH=true -Dcom.datastax.driver.FORCE_NIO=true -DKUBERNETES_MASTER_URL=https://kubernetes.default.svc -DUSER_WRITE_ACCESS=False
>	sun.java.launcher = SUN_STANDARD
>	sun.jnu.encoding = ANSI_X3.4-1968
>	sun.management.compiler = HotSpot 64-Bit Tiered Compilers
>	sun.os.patch.level = unknown
>	user.country = US
>	user.dir = /home/jboss
>	user.home = /home/jboss
>	user.language = en
>	user.name = jboss
>	user.timezone = UTC
>[0m[32m2017-10-18 01:11:01,779 DEBUG [org.jboss.as.config] (MSC service thread 1-7) VM Arguments: -Duser.home=/home/jboss -Duser.name=jboss -D[Standalone] -verbose:gc -Xloggc:/opt/eap/standalone/log/gc.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1192m -Xmx1192m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.logmanager,jdk.nashorn.api -Djava.awt.headless=true -Xbootclasspath/p:/opt/eap/jboss-modules.jar:/opt/eap/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.3.Final-redhat-1.jar:/opt/eap/modules/system/layers/base/org/jboss/logmanager/ext/main/jboss-logmanager-ext-1.0.0.Alpha2-redhat-1.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager -javaagent:/opt/eap/jolokia.jar=port=8778,protocol=https,caCert=/var/run/secrets/kubernetes.io/serviceaccount/ca.crt,clientPrincipal=cn=system:master-proxy,useSslClientAuthentication=true,extraClientCheck=true,host=0.0.0.0,discoveryEnabled=false -Djava.security.egd=file:/dev/./urandom -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/heapdump -Dorg.jboss.boot.log.file=/opt/eap/standalone/log/server.log -Dlogging.configuration=file:/opt/eap/standalone/configuration/logging.properties 
>[0m[0m2017-10-18 01:11:03,787 INFO  [org.jboss.as.repository] (ServerService Thread Pool -- 25) WFLYDR0001: Content added at location /opt/eap/standalone/data/content/93/bd76dce5eb352c86229fcd0c44da1db68fa456/content
>[0m[0m2017-10-18 01:11:04,107 INFO  [org.jboss.as.repository] (ServerService Thread Pool -- 25) WFLYDR0001: Content added at location /opt/eap/standalone/data/content/fe/98b1634537c415c73c31652ab85537580f6cdf/content
>[0m[0m2017-10-18 01:11:04,124 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
>[0m[0m2017-10-18 01:11:04,145 INFO  [org.xnio] (MSC service thread 1-8) XNIO version 3.4.4.Final-redhat-1
>[0m[0m2017-10-18 01:11:04,152 INFO  [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.4.4.Final-redhat-1
>[0m[0m2017-10-18 01:11:04,259 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
>[0m[0m2017-10-18 01:11:04,309 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
>[0m[0m2017-10-18 01:11:04,337 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 45) WFLYCLJG0001: Activating JGroups subsystem.
>[0m[0m2017-10-18 01:11:04,360 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
>[0m[0m2017-10-18 01:11:04,369 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem
>[0m[0m2017-10-18 01:11:04,384 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem
>[0m[0m2017-10-18 01:11:04,386 INFO  [org.jboss.as.connector] (MSC service thread 1-8) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.6.Final-redhat-2)
>[0m[0m2017-10-18 01:11:04,389 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
>[0m[0m2017-10-18 01:11:04,418 INFO  [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=4.9.8.Final-redhat-1
>[0m[0m2017-10-18 01:11:04,444 INFO  [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 4.0.22.Final-redhat-1
>[0m[0m2017-10-18 01:11:04,457 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
>[0m[0m2017-10-18 01:11:04,469 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 1.3.28.Final-redhat-4 starting
>[0m[0m2017-10-18 01:11:04,471 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.3.28.Final-redhat-4 starting
>[0m[0m2017-10-18 01:11:04,474 INFO  [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
>[0m[0m2017-10-18 01:11:04,474 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
>[0m[0m2017-10-18 01:11:04,485 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
>[0m[0m2017-10-18 01:11:04,763 INFO  [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
>[0m[0m2017-10-18 01:11:04,763 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
>[0m[0m2017-10-18 01:11:04,793 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path '/opt/eap/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
>[0m[0m2017-10-18 01:11:04,810 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0012: Started server default-server.
>[0m[0m2017-10-18 01:11:04,813 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
>[0m[0m2017-10-18 01:11:04,876 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080
>[0m[0m2017-10-18 01:11:04,888 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow AJP listener ajp listening on 0.0.0.0:8009
>[0m[0m2017-10-18 01:11:04,898 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 64) MODCLUSTER000001: Initializing mod_cluster version 1.3.3.Final-redhat-1
>[0m[0m2017-10-18 01:11:04,928 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 64) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
>[0m[0m2017-10-18 01:11:05,114 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
>[0m[0m2017-10-18 01:11:05,432 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/eap/standalone/deployments
>[0m[0m2017-10-18 01:11:05,439 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "hawkular-metrics.ear" (runtime-name: "hawkular-metrics.ear")
>[0m[0m2017-10-18 01:11:05,441 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "activemq-rar.rar" (runtime-name: "activemq-rar.rar")
>[0m[33m2017-10-18 01:11:05,455 WARN  [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-1) WFLYDMHTTP0003: Unable to load console module for slot eap, disabling console
>[0m[0m2017-10-18 01:11:05,603 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
>[0m[0m2017-10-18 01:11:05,731 INFO  [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.8.Final-redhat-1 (Apache CXF 3.1.10.redhat-1) 
>[0m[0m2017-10-18 01:11:06,523 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "hawkular-metrics-alerter.war")
>[0m[0m2017-10-18 01:11:06,523 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "hawkular-metrics.war")
>[0m[0m2017-10-18 01:11:06,524 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "hawkular-alerts-action-email.war")
>[0m[0m2017-10-18 01:11:06,524 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "hawkular-alerts.war")
>[0m[0m2017-10-18 01:11:06,524 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "hawkular-alerts-action-webhook.war")
>[0m[0m2017-10-18 01:11:07,258 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-2) IJ020001: Required license terms for file:/opt/eap/standalone/tmp/vfs/temp/temp68ae6f914590aa15/content-666847c190cb4cf6/contents/
>[0m[33m2017-10-18 01:11:07,507 WARN  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-2) IJ020017: Invalid archive: file:/opt/eap/standalone/tmp/vfs/temp/temp68ae6f914590aa15/content-666847c190cb4cf6/contents/
>[0m[33m2017-10-18 01:11:08,150 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0001: /content/hawkular-metrics.ear/hawkular-metrics.war/WEB-INF/jboss-deployment-structure.xml in subdeployment ignored. jboss-deployment-structure.xml is only parsed for top level deployments.
>[0m[33m2017-10-18 01:11:09,323 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.hawkular-metrics.ear" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
>[0m[33m2017-10-18 01:11:09,458 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.hawkular-metrics.ear.hawkular-alerts.war" is using a private module ("com.google.guava:main") which may be changed or removed in future versions without notice.
>[0m[0m2017-10-18 01:11:09,493 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment hawkular-metrics.ear
>[0m[0m2017-10-18 01:11:09,570 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 5.2.5.Final-redhat-1
>[0m[0m2017-10-18 01:11:09,698 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment hawkular-metrics.war
>[0m[0m2017-10-18 01:11:09,781 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment hawkular-alerts-action-email.war
>[0m[0m2017-10-18 01:11:09,782 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment hawkular-metrics-alerter.war
>[0m[0m2017-10-18 01:11:09,784 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment hawkular-alerts-action-webhook.war
>[0m[0m2017-10-18 01:11:09,791 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'ExpressionManager' in deployment unit 'subdeployment "hawkular-metrics-alerter.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-metrics-alerter/ExpressionManager!org.hawkular.metrics.alerter.ExpressionManager
>	java:app/hawkular-metrics-alerter/ExpressionManager!org.hawkular.metrics.alerter.ExpressionManager
>	java:module/ExpressionManager!org.hawkular.metrics.alerter.ExpressionManager
>	java:global/hawkular-metrics/hawkular-metrics-alerter/ExpressionManager
>	java:app/hawkular-metrics-alerter/ExpressionManager
>	java:module/ExpressionManager
>[0m[0m2017-10-18 01:11:09,792 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'StandaloneActionPluginRegister' in deployment unit 'subdeployment "hawkular-alerts-action-email.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts-action-email/StandaloneActionPluginRegister!org.hawkular.alerts.actions.standalone.StandaloneActionPluginRegister
>	java:app/hawkular-alerts-action-email/StandaloneActionPluginRegister!org.hawkular.alerts.actions.standalone.StandaloneActionPluginRegister
>	java:module/StandaloneActionPluginRegister!org.hawkular.alerts.actions.standalone.StandaloneActionPluginRegister
>	java:global/hawkular-metrics/hawkular-alerts-action-email/StandaloneActionPluginRegister
>	java:app/hawkular-alerts-action-email/StandaloneActionPluginRegister
>	java:module/StandaloneActionPluginRegister
>[0m[0m2017-10-18 01:11:09,838 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) WFLYEJB0473: JNDI bindings for session bean named 'StandaloneActionPluginRegister' in deployment unit 'subdeployment "hawkular-alerts-action-webhook.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts-action-webhook/StandaloneActionPluginRegister!org.hawkular.alerts.actions.standalone.StandaloneActionPluginRegister
>	java:app/hawkular-alerts-action-webhook/StandaloneActionPluginRegister!org.hawkular.alerts.actions.standalone.StandaloneActionPluginRegister
>	java:module/StandaloneActionPluginRegister!org.hawkular.alerts.actions.standalone.StandaloneActionPluginRegister
>	java:global/hawkular-metrics/hawkular-alerts-action-webhook/StandaloneActionPluginRegister
>	java:app/hawkular-alerts-action-webhook/StandaloneActionPluginRegister
>	java:module/StandaloneActionPluginRegister
>[0m[0m2017-10-18 01:11:09,876 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment hawkular-alerts.war
>[0m[0m2017-10-18 01:11:10,029 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'DroolsRulesEngineImpl' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/DroolsRulesEngineImpl!org.hawkular.alerts.engine.service.RulesEngine
>	java:app/hawkular-alerts/DroolsRulesEngineImpl!org.hawkular.alerts.engine.service.RulesEngine
>	java:module/DroolsRulesEngineImpl!org.hawkular.alerts.engine.service.RulesEngine
>	java:global/hawkular-metrics/hawkular-alerts/DroolsRulesEngineImpl
>	java:app/hawkular-alerts/DroolsRulesEngineImpl
>	java:module/DroolsRulesEngineImpl
>[0m[0m2017-10-18 01:11:10,029 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'PropertiesServiceImpl' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/PropertiesServiceImpl!org.hawkular.alerts.api.services.PropertiesService
>	java:app/hawkular-alerts/PropertiesServiceImpl!org.hawkular.alerts.api.services.PropertiesService
>	java:module/PropertiesServiceImpl!org.hawkular.alerts.api.services.PropertiesService
>	java:global/hawkular-metrics/hawkular-alerts/PropertiesServiceImpl
>	java:app/hawkular-alerts/PropertiesServiceImpl
>	java:module/PropertiesServiceImpl
>[0m[0m2017-10-18 01:11:10,029 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'IncomingDataManagerImpl' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/IncomingDataManagerImpl!org.hawkular.alerts.engine.service.IncomingDataManager
>	java:app/hawkular-alerts/IncomingDataManagerImpl!org.hawkular.alerts.engine.service.IncomingDataManager
>	java:module/IncomingDataManagerImpl!org.hawkular.alerts.engine.service.IncomingDataManager
>	java:global/hawkular-metrics/hawkular-alerts/IncomingDataManagerImpl
>	java:app/hawkular-alerts/IncomingDataManagerImpl
>	java:module/IncomingDataManagerImpl
>[0m[0m2017-10-18 01:11:10,029 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'AlertsContext' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/AlertsContext!org.hawkular.alerts.engine.impl.AlertsContext
>	java:app/hawkular-alerts/AlertsContext!org.hawkular.alerts.engine.impl.AlertsContext
>	java:module/AlertsContext!org.hawkular.alerts.engine.impl.AlertsContext
>	java:global/hawkular-metrics/hawkular-alerts/AlertsContext
>	java:app/hawkular-alerts/AlertsContext
>	java:module/AlertsContext
>[0m[0m2017-10-18 01:11:10,030 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'AlertsEngineImpl' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/AlertsEngineImpl!org.hawkular.alerts.engine.service.AlertsEngine
>	java:app/hawkular-alerts/AlertsEngineImpl!org.hawkular.alerts.engine.service.AlertsEngine
>	java:module/AlertsEngineImpl!org.hawkular.alerts.engine.service.AlertsEngine
>	java:global/hawkular-metrics/hawkular-alerts/AlertsEngineImpl
>	java:app/hawkular-alerts/AlertsEngineImpl
>	java:module/AlertsEngineImpl
>[0m[0m2017-10-18 01:11:10,030 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'CassActionsServiceImpl' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/CassActionsServiceImpl!org.hawkular.alerts.api.services.ActionsService
>	java:app/hawkular-alerts/CassActionsServiceImpl!org.hawkular.alerts.api.services.ActionsService
>	java:module/CassActionsServiceImpl!org.hawkular.alerts.api.services.ActionsService
>	java:global/hawkular-metrics/hawkular-alerts/CassActionsServiceImpl
>	java:app/hawkular-alerts/CassActionsServiceImpl
>	java:module/CassActionsServiceImpl
>[0m[0m2017-10-18 01:11:10,030 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'PartitionManagerImpl' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/PartitionManagerImpl!org.hawkular.alerts.engine.service.PartitionManager
>	java:app/hawkular-alerts/PartitionManagerImpl!org.hawkular.alerts.engine.service.PartitionManager
>	java:module/PartitionManagerImpl!org.hawkular.alerts.engine.service.PartitionManager
>	java:global/hawkular-metrics/hawkular-alerts/PartitionManagerImpl
>	java:app/hawkular-alerts/PartitionManagerImpl
>	java:module/PartitionManagerImpl
>[0m[0m2017-10-18 01:11:10,030 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'CassAlertsServiceImpl' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/CassAlertsServiceImpl!org.hawkular.alerts.api.services.AlertsService
>	java:app/hawkular-alerts/CassAlertsServiceImpl!org.hawkular.alerts.api.services.AlertsService
>	java:module/CassAlertsServiceImpl!org.hawkular.alerts.api.services.AlertsService
>	java:global/hawkular-metrics/hawkular-alerts/CassAlertsServiceImpl
>	java:app/hawkular-alerts/CassAlertsServiceImpl
>	java:module/CassAlertsServiceImpl
>[0m[0m2017-10-18 01:11:10,030 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'StatusServiceImpl' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/StatusServiceImpl!org.hawkular.alerts.api.services.StatusService
>	java:app/hawkular-alerts/StatusServiceImpl!org.hawkular.alerts.api.services.StatusService
>	java:module/StatusServiceImpl!org.hawkular.alerts.api.services.StatusService
>	java:global/hawkular-metrics/hawkular-alerts/StatusServiceImpl
>	java:app/hawkular-alerts/StatusServiceImpl
>	java:module/StatusServiceImpl
>[0m[0m2017-10-18 01:11:10,030 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'PublishCacheManager' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/PublishCacheManager!org.hawkular.alerts.engine.cache.PublishCacheManager
>	java:app/hawkular-alerts/PublishCacheManager!org.hawkular.alerts.engine.cache.PublishCacheManager
>	java:module/PublishCacheManager!org.hawkular.alerts.engine.cache.PublishCacheManager
>	java:global/hawkular-metrics/hawkular-alerts/PublishCacheManager
>	java:app/hawkular-alerts/PublishCacheManager
>	java:module/PublishCacheManager
>[0m[0m2017-10-18 01:11:10,030 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'DataDrivenGroupCacheManager' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/DataDrivenGroupCacheManager!org.hawkular.alerts.engine.impl.DataDrivenGroupCacheManager
>	java:app/hawkular-alerts/DataDrivenGroupCacheManager!org.hawkular.alerts.engine.impl.DataDrivenGroupCacheManager
>	java:module/DataDrivenGroupCacheManager!org.hawkular.alerts.engine.impl.DataDrivenGroupCacheManager
>	java:global/hawkular-metrics/hawkular-alerts/DataDrivenGroupCacheManager
>	java:app/hawkular-alerts/DataDrivenGroupCacheManager
>	java:module/DataDrivenGroupCacheManager
>[0m[0m2017-10-18 01:11:10,030 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'CassCluster' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/CassCluster!org.hawkular.alerts.engine.impl.CassCluster
>	java:app/hawkular-alerts/CassCluster!org.hawkular.alerts.engine.impl.CassCluster
>	java:module/CassCluster!org.hawkular.alerts.engine.impl.CassCluster
>	java:global/hawkular-metrics/hawkular-alerts/CassCluster
>	java:app/hawkular-alerts/CassCluster
>	java:module/CassCluster
>[0m[0m2017-10-18 01:11:10,030 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'CassDefinitionsServiceImpl' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/CassDefinitionsServiceImpl!org.hawkular.alerts.api.services.DefinitionsService
>	java:app/hawkular-alerts/CassDefinitionsServiceImpl!org.hawkular.alerts.api.services.DefinitionsService
>	java:module/CassDefinitionsServiceImpl!org.hawkular.alerts.api.services.DefinitionsService
>	java:global/hawkular-metrics/hawkular-alerts/CassDefinitionsServiceImpl
>	java:app/hawkular-alerts/CassDefinitionsServiceImpl
>	java:module/CassDefinitionsServiceImpl
>[0m[0m2017-10-18 01:11:10,031 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'ActionsCacheManager' in deployment unit 'subdeployment "hawkular-alerts.war" of deployment "hawkular-metrics.ear"' are as follows:
>	java:global/hawkular-metrics/hawkular-alerts/ActionsCacheManager!org.hawkular.alerts.engine.cache.ActionsCacheManager
>	java:app/hawkular-alerts/ActionsCacheManager!org.hawkular.alerts.engine.cache.ActionsCacheManager
>	java:module/ActionsCacheManager!org.hawkular.alerts.engine.cache.ActionsCacheManager
>	java:global/hawkular-metrics/hawkular-alerts/ActionsCacheManager
>	java:app/hawkular-alerts/ActionsCacheManager
>	java:module/ActionsCacheManager
>[0m[0m2017-10-18 01:11:10,070 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: hawkular-metrics.ear
>[0m[0m2017-10-18 01:11:10,119 INFO  [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.3.3 (redhat)
>[0m[0m2017-10-18 01:11:10,129 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Starting weld service for deployment hawkular-metrics.ear
>[0m[0m2017-10-18 01:11:10,626 INFO  [org.jgroups.protocols.openshift.KUBE_PING] (MSC service thread 1-3) namespace [openshift-infra] set; clustering enabled
>[0m[0m2017-10-18 01:11:10,800 INFO  [org.jgroups.protocols.openshift.KUBE_PING] (MSC service thread 1-3) Starting UndertowServer on port 8888 for channel address: hawkular-metrics-vdllm
>[0m[0m2017-10-18 01:11:10,824 INFO  [org.jgroups.protocols.openshift.KUBE_PING] (MSC service thread 1-3) UndertowServer started.
>[0m[0m2017-10-18 01:11:14,594 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000078: Starting JGroups channel hibernate
>[0m[0m2017-10-18 01:11:14,595 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000078: Starting JGroups channel server
>[0m[0m2017-10-18 01:11:14,595 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000078: Starting JGroups channel hawkular-alerts
>[0m[0m2017-10-18 01:11:14,595 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) ISPN000078: Starting JGroups channel web
>[0m[0m2017-10-18 01:11:14,595 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000078: Starting JGroups channel hawkular-metrics
>[0m[0m2017-10-18 01:11:14,596 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000078: Starting JGroups channel ejb
>[0m[0m2017-10-18 01:11:14,607 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000094: Received new cluster view for channel hawkular-alerts: [hawkular-metrics-vdllm|0] (1) [hawkular-metrics-vdllm]
>[0m[0m2017-10-18 01:11:14,607 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000094: Received new cluster view for channel hawkular-metrics: [hawkular-metrics-vdllm|0] (1) [hawkular-metrics-vdllm]
>[0m[0m2017-10-18 01:11:14,608 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000094: Received new cluster view for channel hibernate: [hawkular-metrics-vdllm|0] (1) [hawkular-metrics-vdllm]
>[0m[0m2017-10-18 01:11:14,608 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000094: Received new cluster view for channel server: [hawkular-metrics-vdllm|0] (1) [hawkular-metrics-vdllm]
>[0m[0m2017-10-18 01:11:14,612 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000079: Channel hibernate local address is hawkular-metrics-vdllm, physical addresses are [10.128.0.51:7600]
>[0m[0m2017-10-18 01:11:14,607 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000094: Received new cluster view for channel ejb: [hawkular-metrics-vdllm|0] (1) [hawkular-metrics-vdllm]
>[0m[0m2017-10-18 01:11:14,612 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000079: Channel ejb local address is hawkular-metrics-vdllm, physical addresses are [10.128.0.51:7600]
>[0m[0m2017-10-18 01:11:14,608 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) ISPN000094: Received new cluster view for channel web: [hawkular-metrics-vdllm|0] (1) [hawkular-metrics-vdllm]
>[0m[0m2017-10-18 01:11:14,612 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) ISPN000079: Channel web local address is hawkular-metrics-vdllm, physical addresses are [10.128.0.51:7600]
>[0m[0m2017-10-18 01:11:14,613 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000079: Channel server local address is hawkular-metrics-vdllm, physical addresses are [10.128.0.51:7600]
>[0m[0m2017-10-18 01:11:14,615 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000079: Channel hawkular-alerts local address is hawkular-metrics-vdllm, physical addresses are [10.128.0.51:7600]
>[0m[0m2017-10-18 01:11:14,616 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000079: Channel hawkular-metrics local address is hawkular-metrics-vdllm, physical addresses are [10.128.0.51:7600]
>[0m[0m2017-10-18 01:11:14,626 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.8.Final-redhat-1
>[0m[0m2017-10-18 01:11:14,854 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started publish cache from hawkular-alerts container
>[0m[0m2017-10-18 01:11:14,861 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 70) WFLYCLINF0002: Started dataIds cache from hawkular-alerts container
>[0m[0m2017-10-18 01:11:14,870 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 69) WFLYCLINF0002: Started triggers cache from hawkular-alerts container
>[0m[0m2017-10-18 01:11:14,872 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 71) WFLYCLINF0002: Started globalActions cache from hawkular-alerts container
>[0m[0m2017-10-18 01:11:14,873 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 68) WFLYCLINF0002: Started partition cache from hawkular-alerts container
>[0m[0m2017-10-18 01:11:14,874 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 67) WFLYCLINF0002: Started schema cache from hawkular-alerts container
>[0m[0m2017-10-18 01:11:14,875 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 72) WFLYCLINF0002: Started data cache from hawkular-alerts container
>[0m[0m2017-10-18 01:11:14,878 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 64) WFLYCLINF0002: Started client-mappings cache from ejb container
>[0m[0m2017-10-18 01:11:14,966 INFO  [org.hawkular.alerts.engine.log] (ServerService Thread Pool -- 68) HAWKALERT220023: Init Actions Cache
>[0m[33m2017-10-18 01:11:14,986 WARN  [org.hawkular.alerts.engine.log] (ServerService Thread Pool -- 70) HAWKALERT220021: Clear Publish Cache
>[0m[0m2017-10-18 01:11:14,987 INFO  [org.hawkular.alerts.engine.log] (ServerService Thread Pool -- 70) HAWKALERT220020: Init Publish Cache
>[0m[0m2017-10-18 01:11:15,056 INFO  [com.datastax.driver.core.SystemProperties] (ServerService Thread Pool -- 74) com.datastax.driver.FORCE_NIO is defined, using value true
>[0m[0m2017-10-18 01:11:15,057 INFO  [com.datastax.driver.core.NettyUtil] (ServerService Thread Pool -- 74) Did not find Netty's native epoll transport in the classpath, defaulting to NIO.
>[0m[33m2017-10-18 01:11:18,679 WARN  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Could not connect to Cassandra cluster - assuming is not up yet. Cause: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: hawkular-cassandra/172.30.42.134:9042 (com.datastax.driver.core.exceptions.TransportException: [hawkular-cassandra/172.30.42.134:9042] Cannot connect))
>[0m[33m2017-10-18 01:11:18,684 WARN  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) [15] Retrying connecting to Cassandra cluster in [3000]ms...
>[0m[33m2017-10-18 01:11:24,713 WARN  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Could not connect to Cassandra cluster - assuming is not up yet. Cause: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: hawkular-cassandra/172.30.42.134:9042 (com.datastax.driver.core.exceptions.TransportException: [hawkular-cassandra/172.30.42.134:9042] Cannot connect))
>[0m[33m2017-10-18 01:11:24,713 WARN  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) [14] Retrying connecting to Cassandra cluster in [3000]ms...
>[0m[33m2017-10-18 01:11:27,723 WARN  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Could not connect to Cassandra cluster - assuming is not up yet. Cause: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: hawkular-cassandra/172.30.42.134:9042 (com.datastax.driver.core.exceptions.TransportException: [hawkular-cassandra/172.30.42.134:9042] Cannot connect))
>[0m[33m2017-10-18 01:11:27,724 WARN  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) [13] Retrying connecting to Cassandra cluster in [3000]ms...
>[0m[0m2017-10-18 01:11:31,198 INFO  [com.datastax.driver.core.policies.DCAwareRoundRobinPolicy] (ServerService Thread Pool -- 74) Using data-center name 'datacenter1' for DCAwareRoundRobinPolicy (if this is incorrect, please provide the correct datacenter name with DCAwareRoundRobinPolicy constructor)
>[0m[0m2017-10-18 01:11:31,199 INFO  [com.datastax.driver.core.Cluster] (ServerService Thread Pool -- 74) New Cassandra host hawkular-cassandra/172.30.42.134:9042 added
>[0m[0m2017-10-18 01:11:31,268 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Checking Schema existence for keyspace: hawkular_alerts
>[0m[0m2017-10-18 01:11:31,621 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Executing [script:vfs:/content/hawkular-metrics.ear/hawkular-alerts.war/WEB-INF/lib/hawkular-alerts-engine-1.5.4.Final-redhat-1.jar/org/hawkular/alerts/schema/cassalog.groovy, tags:[], vars:[keyspace:hawkular_alerts, reset:false, session:com.datastax.driver.core.SessionManager@6dde2742, logger:org.jboss.logging.JBossLogManagerLogger@405b7bdb]]
>[0m[0m2017-10-18 01:11:32,076 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table triggers
>[0m[0m2017-10-18 01:11:32,203 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table triggers_actions
>[0m[0m2017-10-18 01:11:32,282 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table conditions
>[0m[0m2017-10-18 01:11:32,504 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table dampenings
>[0m[0m2017-10-18 01:11:32,752 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table action_plugins
>[0m[0m2017-10-18 01:11:32,833 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table actions_definitions
>[0m[0m2017-10-18 01:11:32,949 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table actions_history
>[0m[0m2017-10-18 01:11:33,058 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table actions_history_actions
>[0m[0m2017-10-18 01:11:33,161 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table actions_history_alerts
>[0m[0m2017-10-18 01:11:33,255 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table actions_history_ctimes
>[0m[0m2017-10-18 01:11:33,346 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table actions_history_results
>[0m[0m2017-10-18 01:11:33,440 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table tags
>[0m[0m2017-10-18 01:11:33,517 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table alerts
>[0m[0m2017-10-18 01:11:33,600 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table alerts_triggers
>[0m[0m2017-10-18 01:11:33,686 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table alerts_ctimes
>[0m[0m2017-10-18 01:11:33,775 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table alerts_statuses
>[0m[0m2017-10-18 01:11:33,857 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table alerts_severities
>[0m[0m2017-10-18 01:11:33,940 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table alerts_lifecycle
>[0m[0m2017-10-18 01:11:34,005 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table events
>[0m[0m2017-10-18 01:11:34,071 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table events_triggers
>[0m[0m2017-10-18 01:11:34,144 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table events_ctimes
>[0m[0m2017-10-18 01:11:34,199 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Creating table events_categories
>[0m[0m2017-10-18 01:11:34,358 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Creating change log table hawkular_alerts.cassalog
>[0m[33m2017-10-18 01:11:34,514 WARN  [com.datastax.driver.core.Cluster] (cluster4-worker-3) Re-preparing already prepared query is generally an anti-pattern and will likely affect performance. Consider preparing the statement only once. Query='UPDATE hawkular_alerts.cassalog SET applied_at = ? WHERE bucket = ? AND revision = ?'
>[0m[0m2017-10-18 01:11:34,522 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: set-keyspace
>USE hawkular_alerts
>--
>[0m[0m2017-10-18 01:11:34,558 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: set-keyspace
>USE hawkular_alerts
>--
>[0m[0m2017-10-18 01:11:34,571 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: 1.0
>CREATE TABLE sys_config (
>        config_id text,
>        name text,
>        value text,
>        PRIMARY KEY (config_id, name)
>)
>--
>[0m[0m2017-10-18 01:11:34,691 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: set-keyspace
>USE hawkular_alerts
>--
>[0m[0m2017-10-18 01:11:34,706 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: 2.0
>ALTER TABLE conditions ADD interval bigint
>--
>[0m[0m2017-10-18 01:11:34,796 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: set-keyspace
>USE hawkular_alerts
>--
>[0m[0m2017-10-18 01:11:34,804 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: 3.0
>DROP TABLE alerts_statuses
>--
>[0m[0m2017-10-18 01:11:34,927 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: 3.1
>DROP TABLE alerts_severities
>--
>[0m[0m2017-10-18 01:11:35,017 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: set-keyspace
>USE hawkular_alerts
>--
>[0m[0m2017-10-18 01:11:35,024 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: 4.0
>ALTER TABLE conditions ADD activeRules set<text>
>--
>[0m[0m2017-10-18 01:11:35,117 INFO  [org.cassalog.core.CassalogImpl] (ServerService Thread Pool -- 74) Applying ChangeSet
>-- version: 4.1
>ALTER TABLE conditions ADD sampleSize int
>--
>[0m[0m2017-10-18 01:11:35,343 INFO  [org.hawkular.alerts.engine.impl.CassCluster] (ServerService Thread Pool -- 74) Done creating Schema for keyspace: hawkular_alerts
>[0m[0m2017-10-18 01:11:35,393 INFO  [org.hawkular.alerts.engine.log] (ServerService Thread Pool -- 66) HAWKALERT220015: Hawkular Alerts deployed in distributed mode
>[0m[0m2017-10-18 01:11:35,401 INFO  [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (EE-ManagedExecutorService-default-Thread-1) Found kmodule: vfs:/content/hawkular-metrics.ear/hawkular-alerts.war/WEB-INF/lib/hawkular-alerts-engine-1.5.4.Final-redhat-1.jar/META-INF/kmodule.xml
>[0m[0m2017-10-18 01:11:35,404 INFO  [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (EE-ManagedExecutorService-default-Thread-1) Virtual file physical path = /opt/eap/standalone/tmp/vfs/deployment/deployment3aadc977dd02f38c/hawkular-alerts-engine-1.5.4.Final-redhat-1.jar-186fcb5d17928f91/hawkular-alerts-engine-1.5.4.Final-redhat-1.jar
>[0m[0m2017-10-18 01:11:35,506 INFO  [org.hawkular.openshift.auth.OpenshiftAuthServletExtension] (ServerService Thread Pool -- 64) The OpenShift Namespace Filter has been disabled via the 'DISABLE_NAMESPACE_FILTER' system property.
>[0m[0m2017-10-18 01:11:35,556 INFO  [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (EE-ManagedExecutorService-default-Thread-1) KieModule was added: ZipKieModule[releaseId=org.hawkular.alerts:hawkular-alerts-engine:1.5.4.Final-redhat-1,file=/opt/eap/standalone/tmp/vfs/deployment/deployment3aadc977dd02f38c/hawkular-alerts-engine-1.5.4.Final-redhat-1.jar-186fcb5d17928f91/hawkular-alerts-engine-1.5.4.Final-redhat-1.jar]
>[0m[0m2017-10-18 01:11:35,615 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 64) Initializing Mojarra 2.2.12-jbossorg-2  for context '/hawkular/alerts'
>[0m[0m2017-10-18 01:11:37,566 INFO  [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 64) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.hawkular.alerts.rest.HawkularAlertsApp$Proxy$_$$_WeldClientProxy
>[0m[0m2017-10-18 01:11:38,022 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0021: Registered web context: /hawkular/alerts
>[0m[0m2017-10-18 01:11:38,315 INFO  [org.hawkular.alerts.engine.log] (ServerService Thread Pool -- 66) HAWKALERT220006: ActionListener [org.hawkular.alerts.actions.standalone.StandaloneActionPluginListener@6f2bff8b] registered
>[0m[0m2017-10-18 01:11:38,315 INFO  [org.hawkular.alerts.actions.standalone] (ServerService Thread Pool -- 66) HAWKALERT270001: Action plugin [email] registered
>[0m[0m2017-10-18 01:11:38,335 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: /hawkular/actions/email
>[0m[0m2017-10-18 01:11:38,378 INFO  [org.hawkular.alerts.engine.log] (ServerService Thread Pool -- 66) HAWKALERT220006: ActionListener [org.hawkular.alerts.actions.standalone.StandaloneActionPluginListener@579c6ce3] registered
>[0m[0m2017-10-18 01:11:38,378 INFO  [org.hawkular.alerts.actions.standalone] (ServerService Thread Pool -- 66) HAWKALERT270001: Action plugin [webhook] registered
>[0m[0m2017-10-18 01:11:38,400 INFO  [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 66) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.hawkular.alerts.actions.webhook.WebHookApp
>[0m[0m2017-10-18 01:11:38,405 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: /hawkular/actions/webhook
>[0m[0m2017-10-18 01:11:38,447 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started locks cache from hawkular-metrics container
>[0m[0m2017-10-18 01:11:38,485 INFO  [org.hawkular.openshift.auth.OpenshiftAuthServletExtension] (ServerService Thread Pool -- 66) The OpenShift Namespace Filter has been disabled via the 'DISABLE_NAMESPACE_FILTER' system property.
>[0m[0m2017-10-18 01:11:38,510 INFO  [org.hawkular.metrics.api.jaxrs.MetricsServiceLifecycle] (ServerService Thread Pool -- 66) Hawkular Metrics version: 0.23.12.Final-redhat-2
>[0m[0m2017-10-18 01:11:38,538 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 66) Initializing Mojarra 2.2.12-jbossorg-2  for context '/hawkular/metrics'
>[0m[0m2017-10-18 01:11:38,540 INFO  [org.hawkular.metrics.api.jaxrs.MetricsServiceLifecycle] (metricsservice-lifecycle-thread) HAWKMETRICS200002: Initializing metrics service
>[0m[0m2017-10-18 01:11:38,777 INFO  [com.datastax.driver.core.policies.DCAwareRoundRobinPolicy] (metricsservice-lifecycle-thread) Using data-center name 'datacenter1' for DCAwareRoundRobinPolicy (if this is incorrect, please provide the correct datacenter name with DCAwareRoundRobinPolicy constructor)
>[0m[0m2017-10-18 01:11:38,778 INFO  [com.datastax.driver.core.Cluster] (metricsservice-lifecycle-thread) New Cassandra host hawkular-cassandra/172.30.42.134:9042 added
>[0m[0m2017-10-18 01:11:39,129 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Executing [script:vfs:/content/hawkular-metrics.ear/hawkular-metrics.war/WEB-INF/lib/hawkular-metrics-schema-0.23.12.Final-redhat-2.jar/org/hawkular/schema/cassalog.groovy, tags:[0.15.x, 0.18.x, 0.19.x, 0.20.x, 0.21.x, 0.23.x], vars:[keyspace:hawkular_metrics, reset:false, session:com.datastax.driver.core.SessionManager@4e858796, replicationFactor:1, logger:org.jboss.logging.JBossLogManagerLogger@24234e0]]
>[0m[0m2017-10-18 01:11:39,281 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating table tenants
>[0m[0m2017-10-18 01:11:39,325 INFO  [org.hawkular.metrics.api.jaxrs.HawkularMetricsRestApp] (ServerService Thread Pool -- 66) HAWKMETRICS200001: Hawkular Metrics starting
>[0m[0m2017-10-18 01:11:39,326 INFO  [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 66) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.hawkular.metrics.api.jaxrs.HawkularMetricsRestApp
>[0m[0m2017-10-18 01:11:39,386 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating type aggregation_template
>[0m[0m2017-10-18 01:11:39,469 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating table tenants_by_time
>[0m[0m2017-10-18 01:11:39,581 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating type aggregate_data
>[0m[0m2017-10-18 01:11:39,585 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: /hawkular/metrics
>[0m[0m2017-10-18 01:11:39,663 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating table data
>[0m[0m2017-10-18 01:11:39,686 INFO  [org.hawkular.metrics.alerter.ExpressionManager] (ServerService Thread Pool -- 74) Starting Hawkular Metrics External Alerter, distributed=true
>[0m[0m2017-10-18 01:11:39,723 INFO  [org.hawkular.metrics.alerter.ExpressionManager] (ServerService Thread Pool -- 74) Registering Trigger UPDATE/REMOVE listener
>[0m[0m2017-10-18 01:11:39,746 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 74) Initializing Mojarra 2.2.12-jbossorg-2  for context '/hawkular/__alerter-metrics'
>[0m[0m2017-10-18 01:11:39,766 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating table metrics_tags_idx
>[0m[0m2017-10-18 01:11:39,856 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating table metrics_idx
>[0m[0m2017-10-18 01:11:39,901 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0021: Registered web context: /hawkular/__alerter-metrics
>[0m[0m2017-10-18 01:11:39,938 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "hawkular-metrics.ear" (runtime-name : "hawkular-metrics.ear")
>[0m[0m2017-10-18 01:11:39,938 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "activemq-rar.rar" (runtime-name : "activemq-rar.rar")
>[0m[0m2017-10-18 01:11:40,035 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating table retentions_idx
>[0m[0m2017-10-18 01:11:40,055 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
>[0m[0m2017-10-18 01:11:40,056 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
>[0m[0m2017-10-18 01:11:40,056 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.6.GA (WildFly Core 2.1.15.Final-redhat-1) started in 39039ms - Started 1305 of 1826 services (832 services are lazy, passive or on-demand)
>[0m[0m2017-10-18 01:11:40,110 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating type trigger_def
>[0m[0m2017-10-18 01:11:40,151 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating table tasks
>[0m[0m2017-10-18 01:11:40,201 INFO  [org.hawkular.metrics.schema.SchemaService] (metricsservice-lifecycle-thread) Creating table leases
>[0m[0m2017-10-18 01:11:40,445 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Creating change log table hawkular_metrics.cassalog
>[0m[33m2017-10-18 01:11:40,521 WARN  [com.datastax.driver.core.Cluster] (cluster5-worker-2) Re-preparing already prepared query is generally an anti-pattern and will likely affect performance. Consider preparing the statement only once. Query='UPDATE hawkular_metrics.cassalog SET applied_at = ? WHERE bucket = ? AND revision = ?'
>[0m[0m2017-10-18 01:11:40,534 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: set-keyspace
>USE hawkular_metrics
>--
>[0m[0m2017-10-18 01:11:40,545 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 1.0
>CREATE TABLE sys_config (
>    config_id text,
>    name text,
>    value text,
>    PRIMARY KEY (config_id, name)
>) WITH compaction = { 'class': 'LeveledCompactionStrategy' }
>--
>[0m[0m2017-10-18 01:11:40,606 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 1.1
>ALTER TABLE data WITH gc_grace_seconds = 86400
>--
>[0m[0m2017-10-18 01:11:40,655 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 1.2
>ALTER TABLE data ADD tags map<text,text>
>--
>[0m[0m2017-10-18 01:11:40,731 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 1.3
>ALTER TABLE data ADD s_value text
>--
>[0m[0m2017-10-18 01:11:40,787 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 1.4
>INSERT INTO sys_config (config_id, name, value) VALUES ('org.hawkular.metrics', 'string-size', '2048')
>--
>[0m[0m2017-10-18 01:11:40,792 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: set-keyspace
>USE hawkular_metrics
>--
>[0m[0m2017-10-18 01:11:40,797 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 2.0
>CREATE TABLE locks (
>    name text PRIMARY KEY,
>    value text,
>) WITH compaction = { 'class': 'LeveledCompactionStrategy' }
>--
>[0m[0m2017-10-18 01:11:40,841 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 2.1
>CREATE TABLE jobs (
>    id uuid PRIMARY KEY,
>    type text,
>    name text,
>    params map<text, text>,
>    trigger frozen <trigger_def>
>) WITH compaction = { 'class': 'LeveledCompactionStrategy' }
>--
>[0m[0m2017-10-18 01:11:40,909 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 2.2
>CREATE TABLE scheduled_jobs_idx (
>    time_slice timestamp,
>    job_id uuid,
>    PRIMARY KEY (time_slice, job_id)
>) WITH compaction = { 'class': 'LeveledCompactionStrategy' }
>--
>[0m[0m2017-10-18 01:11:40,983 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 2.3
>CREATE TABLE finished_jobs_idx (
>    time_slice timestamp,
>    job_id uuid,
>    PRIMARY KEY (time_slice, job_id)
>) WITH compaction = { 'class': 'LeveledCompactionStrategy' }
>--
>[0m[0m2017-10-18 01:11:41,043 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 2.4
>CREATE TABLE active_time_slices (
>    time_slice timestamp PRIMARY KEY
>) WITH compaction = { 'class' : 'LeveledCompactionStrategy' }
>--
>[0m[0m2017-10-18 01:11:41,106 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 3.0
>ALTER TABLE hawkular_metrics.data WITH COMPRESSION = {'sstable_compression': 'DeflateCompressor'};
>--
>[0m[0m2017-10-18 01:11:41,168 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 3.1
>ALTER TABLE data WITH compaction = {'class': 'DateTieredCompactionStrategy'} AND default_time_to_live = 604800
>--
>[0m[0m2017-10-18 01:11:41,220 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 3.2
>ALTER TABLE data DROP aggregates
>--
>[0m[0m2017-10-18 01:11:41,277 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 3.3
>DROP TYPE aggregate_data
>--
>[0m[0m2017-10-18 01:11:41,320 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 3.4
>ALTER TABLE data DROP data_retention
>--
>[0m[0m2017-10-18 01:11:41,374 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 3.5
>DROP TYPE aggregation_template
>--
>[0m[0m2017-10-18 01:11:41,412 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 3.6
>DROP TABLE tenants_by_time
>--
>[0m[0m2017-10-18 01:11:41,539 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: set-keyspace
>USE hawkular_metrics
>--
>[0m[0m2017-10-18 01:11:41,543 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 4.0
>CREATE TABLE data_compressed (
>    tenant_id text,
>    type tinyint,
>    metric text,
>    dpart bigint,
>    time timestamp,
>    c_value blob,
>    ts_value blob,
>    tags blob,
>    PRIMARY KEY ((tenant_id, type, metric, dpart), time)
>) WITH CLUSTERING ORDER BY (time DESC)
>--
>[0m[0m2017-10-18 01:11:41,594 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 4.1
>ALTER TABLE data WITH COMPRESSION = {'sstable_compression': 'LZ4Compressor'};
>--
>[0m[0m2017-10-18 01:11:41,645 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 5.0
>ALTER TABLE scheduled_jobs_idx ADD job_name text
>--
>[0m[0m2017-10-18 01:11:41,719 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 5.1
>ALTER TABLE scheduled_jobs_idx ADD job_params frozen<map<text, text>>
>--
>[0m[0m2017-10-18 01:11:41,807 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 5.2
>ALTER TABLE scheduled_jobs_idx ADD trigger frozen<trigger_def>
>--
>[0m[0m2017-10-18 01:11:41,855 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 5.3
>ALTER TABLE scheduled_jobs_idx ADD job_type text
>--
>[0m[0m2017-10-18 01:11:41,903 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 5.4
>ALTER TABLE scheduled_jobs_idx ADD status tinyint
>--
>[0m[0m2017-10-18 01:11:41,968 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 5.5
>INSERT INTO sys_config (config_id, name, value) VALUES ('org.hawkular.metrics', 'gc_grace_seconds', '604800')
>--
>[0m[0m2017-10-18 01:11:41,974 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 5.6
>BEGIN UNLOGGED BATCH
>    INSERT INTO sys_config (config_id, name, value)
>        VALUES ('org.hawkular.metrics', 'ingestion.retry.max-retries', '5');
>    INSERT INTO sys_config (config_id, name, value)
>        VALUES ('org.hawkular.metrics', 'ingestion.retry.max-delay', '30000');
>APPLY BATCH;
>--
>[0m[0m2017-10-18 01:11:41,986 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 6.0
>ALTER TABLE data_compressed WITH compaction = {
>  'class': 'TimeWindowCompactionStrategy',
>  'compaction_window_unit': 'DAYS',
>  'compaction_window_size': '1'
>}
>--
>[0m[0m2017-10-18 01:11:42,029 INFO  [org.cassalog.core.CassalogImpl] (metricsservice-lifecycle-thread) Applying ChangeSet
>-- version: 6.1
>ALTER TABLE data WITH compaction = {'class': 'SizeTieredCompactionStrategy'}
>--
>[0m[0m2017-10-18 01:11:42,158 INFO  [org.hawkular.metrics.api.jaxrs.MetricsServiceLifecycle] (metricsservice-lifecycle-thread) The keyspace hawkular_metrics is using a replication_factor of 1
>[0m[0m2017-10-18 01:11:42,377 INFO  [org.hawkular.metrics.core.service.MetricsServiceImpl] (metricsservice-lifecycle-thread) HAWKMETRICS100001: Using a key space of 'hawkular_metrics'
>[0m[0m2017-10-18 01:11:42,429 INFO  [org.hawkular.metrics.core.service.MetricsServiceImpl] (metricsservice-lifecycle-thread) HAWKMETRICS100008: Using max size of 2048 for string metrics
>[0m[0m2017-10-18 01:11:42,429 INFO  [org.hawkular.metrics.core.service.MetricsServiceImpl] (metricsservice-lifecycle-thread) HAWKMETRICS100009: Using max number of retries 5 and max retry delay of 30000 ms for inserting data points
>[0m[0m2017-10-18 01:11:42,431 INFO  [org.hawkular.metrics.core.service.MetricsServiceImpl] (metricsservice-lifecycle-thread) HAWKMETRICS100007: Using default data retention of 604800 seconds
>[0m[0m2017-10-18 01:11:42,436 INFO  [org.hawkular.metrics.core.dropwizard.MetricsInitializer] (metricsservice-lifecycle-thread) Creating metrics
>[0m[0m2017-10-18 01:11:42,625 INFO  [org.hawkular.metrics.core.dropwizard.MetricsInitializer] (RxComputationScheduler-1) Finished creating metrics in 188 ms
>[0m[33m2017-10-18 01:11:42,670 WARN  [com.datastax.driver.core.Cluster] (cluster5-worker-1) Re-preparing already prepared query is generally an anti-pattern and will likely affect performance. Consider preparing the statement only once. Query='SELECT DISTINCT tenant_id, tname FROM metrics_tags_idx'
>[0m[0m2017-10-18 01:11:42,695 INFO  [org.hawkular.metrics.core.jobs.JobsServiceImpl] (metricsservice-lifecycle-thread) Preparing to create and schedule COMPRESS_DATA job
>[0m[0m2017-10-18 01:11:42,853 INFO  [org.hawkular.metrics.core.jobs.JobsServiceImpl] (metricsservice-lifecycle-thread) Created and scheduled JobDetails{jobId=5ec0b1fc-1bf1-413f-8287-b90f28948f43, jobType=COMPRESS_DATA, jobName=COMPRESS_DATA, parameters={}, trigger=RepeatingTrigger{triggerTime=1508295600000, interval=7200000, delay=60000}, status=NONE}
>[0m[0m2017-10-18 01:11:42,866 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (metricsservice-lifecycle-thread) Checking tables in hawkular_metrics to see if gc_grace_seconds needs to be updated
>[0m[0m2017-10-18 01:11:42,877 INFO  [org.hawkular.metrics.api.jaxrs.MetricsServiceLifecycle] (metricsservice-lifecycle-thread) HAWKMETRICS200005: Metrics service started
>[0m[0m2017-10-18 01:11:42,878 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-2) gc_grace_seconds for active_time_slices is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:42,879 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-2) gc_grace_seconds for cassalog is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:42,953 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-4) gc_grace_seconds for data is set to 86400. Resetting to 0
>[0m[0m2017-10-18 01:11:42,977 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-3) gc_grace_seconds for data_compressed is set to 864000. Resetting back to zero.
>[0m[0m2017-10-18 01:11:43,010 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-1) gc_grace_seconds for finished_jobs_idx is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:43,041 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-2) gc_grace_seconds for jobs is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:43,078 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-4) gc_grace_seconds for leases is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:43,124 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-3) gc_grace_seconds for locks is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:43,153 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-1) gc_grace_seconds for metrics_idx is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:43,200 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-2) gc_grace_seconds for metrics_tags_idx is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:43,254 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-4) gc_grace_seconds for retentions_idx is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:43,299 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-3) gc_grace_seconds for scheduled_jobs_idx is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:43,325 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-1) gc_grace_seconds for sys_config is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:43,358 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-2) gc_grace_seconds for tasks is set to 864000. Resetting to 0
>[0m[0m2017-10-18 01:11:43,390 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-4) gc_grace_seconds for tenants is set to 864000. Resetting to 0
>[0m[33m2017-10-18 01:24:30,102 WARN  [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-49) RESTEASY002142: Multiple resource methods match request "GET /". Selecting one. Matching methods: [public javax.ws.rs.core.Response org.hawkular.metrics.api.jaxrs.handler.BaseHandler.baseJSON(), public void org.hawkular.metrics.api.jaxrs.handler.BaseHandler.baseHTML(javax.servlet.ServletContext) throws java.lang.Exception]
>[0m[33m2017-10-18 01:24:46,261 WARN  [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-5) RESTEASY002142: Multiple resource methods match request "GET /". Selecting one. Matching methods: [public javax.ws.rs.core.Response org.hawkular.metrics.api.jaxrs.handler.BaseHandler.baseJSON(), public void org.hawkular.metrics.api.jaxrs.handler.BaseHandler.baseHTML(javax.servlet.ServletContext) throws java.lang.Exception]

Actions: View

Attachments on bug 1500464: 1339227 | 1339962