Under OOM,

 

Holmes – Both Rule and engine module were not deployed correctly. The hostname exposed within container is incorrect and doesn’t match to what is registered in Consul.

 

Also holmes requires explicit service registration into Consul.

 

root@s8f9d9316a5ff42c8b7157bcad3728488-dcae-analytics-holmes-rule-ma:/home/holmes# env | grep -i hostname

HOSTNAME=holmes-rule-mgmt

 

2018-05-11 21:12:18 253 INFO  [org.onap.holmes.common.config.MicroServiceConfig][pool-1-thread-1] - Query the config-binding-service address using the URL: http://consul-server.onap:8500/v1/catalog/service/config-binding-service

2018-05-11 21:12:18 266 INFO  [org.onap.holmes.common.config.MicroServiceConfig][pool-1-thread-1] - The config-binding-service address is http://config-binding-service:10000

2018-05-11 21:12:18 291 INFO  [org.onap.holmes.common.config.MicroServiceConfig][pool-1-thread-1] - The query url is: http://config-binding-service:10000/service_component/holmes-rule-mgmt. The corresponding configurations are

2018-05-11 21:12:18 291 ERROR [org.onap.holmes.rulemgt.dcae.DcaeConfigurationPolling][pool-1-thread-1] - Failed to fetch DCAE configurations. Can not resolve configurations from DCAE. The configuration string is empty.

org.onap.holmes.common.exception.CorrelationException: Can not resolve configurations from DCAE. The configuration string is empty.

        at org.onap.holmes.common.dcae.utils.DcaeConfigurationParser.parse(DcaeConfigurationParser.java:39) ~[holmes-rulemgt.jar:1.0.0-SNAPSHOT]

        at org.onap.holmes.common.dcae.DcaeConfigurationQuery.getDcaeConfigurations(DcaeConfigurationQuery.java:32) ~[holmes-rulemgt.jar:1.0.0-SNAPSHOT]

        at org.onap.holmes.rulemgt.dcae.DcaeConfigurationPolling.run(DcaeConfigurationPolling.java:57) ~[holmes-rulemgt.jar:1.0.0-SNAPSHOT]

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_151]

        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_151]

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_151]

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]

 

Similar issue for holmes engine.

2018-05-12 07:34:09 734 INFO  [org.onap.holmes.common.config.MicroServiceConfig][pool-3-thread-1] - The query url is: http://config-binding-service:10000/service_component/holmes-engine-mgmt. The corresponding configurations are

2018-05-12 07:34:09 734 ERROR [org.onap.holmes.engine.dcae.DcaeConfigurationPolling][pool-3-thread-1] - Failed to poll the DCAE configurations. Can not resolve configurations from DCAE. The configuration string is empty.

org.onap.holmes.common.exception.CorrelationException: Can not resolve configurations from DCAE. The configuration string is empty.