Highlighted
Julian Kurt Contributor.
Contributor.
1128 views

Stuck at Configuring ALM Octane - Wrong elasticsearch parameters

Jump to solution

Hi, I'm new to ALM Octane and I'm trying to build up a server in my linux environment for simulation.

I already configured and inputted the parameters needed in elasticsearch.yml.

I can curl and ping my three servers with each other (db, elasticsearch, and octane)

After I run ./HPALM file it gives me a output of service running: process ID is X

When I run the ./initserver file it gives me the output of endless "the server still not responding"

When I run also the ./wrapper file it gives me the following error log -

"2018/04/03 01:11:36 | wrapper | --> Wrapper Started as Daemon
2018/04/03 01:11:36 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.32
2018/04/03 01:11:36 | wrapper | Copyright (C) 1999-2017 Tanuki Software, Ltd. All Rights Reserved.
2018/04/03 01:11:36 | wrapper | http://wrapper.tanukisoftware.com
2018/04/03 01:11:36 | wrapper | Licensed to Hewlett-Packard Company for Octane
2018/04/03 01:11:36 | wrapper |
2018/04/03 01:11:37 | wrapper | Launching a JVM...
2018/04/03 01:11:37 | jvm 1 | -XX:CMSInitiatingOccupancyFraction=80 -XX:+CMSScavengeBeforeRemark -XX:+ExplicitGCInvokesConcurrent -XX:+HeapDumpOnOutOfMemoryError -XX:InitialHeapSize=4294967296 -XX:MaxHeapSize=4294967296 -XX:MaxNewSize=2147483648 -XX:MaxTenuringThreshold=6 -XX:NewRatio=2 -XX:OldPLABSize=16 -XX:+PrintCommandLineFlags -XX:-UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:+UseParNewGC
2018/04/03 01:11:37 | jvm 1 | WrapperManager: Initializing...
2018/04/03 01:11:37 | jvm 1 | 2018-04-03 01:11:37.529:INFO::WrapperSimpleAppMain: Logging initialized @499ms
2018/04/03 01:11:37 | jvm 1 | Starting server configuration.
2018/04/03 01:11:37 | jvm 1 | Reading the list of configuration files from: /opt/octane/server/conf/start.ini
2018/04/03 01:11:37 | jvm 1 | Reading configuration from: /opt/octane/server/conf/jetty.xml
2018/04/03 01:11:37 | jvm 1 | Reading configuration from: /opt/octane/server/conf/jetty-deploy.xml
2018/04/03 01:11:37 | jvm 1 | Reading configuration from: /opt/octane/server/conf/jetty-rewrite.xml
2018/04/03 01:11:37 | jvm 1 | Reading configuration from: /opt/octane/server/conf/jetty-stats.xml
2018/04/03 01:11:37 | jvm 1 | Server configured succesfully.
2018/04/03 01:11:37 | jvm 1 | Starting HTTP server.
2018/04/03 01:11:37 | jvm 1 | 2018-04-03 01:11:37.801:INFO:oejs.Server:WrapperSimpleAppMain: jetty-9.2.9.v20150224
2018/04/03 01:11:37 | jvm 1 | 2018-04-03 01:11:37.825:INFO:oejdp.ScanningAppProvider:WrapperSimpleAppMain: Deployment monitor [file:/opt/octane/webapps/] at interval 0
2018/04/03 01:11:39 | jvm 1 | ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
2018/04/03 01:11:39 | jvm 1 | 2018-04-03 01:11:39.852:INFO:root:WrapperSimpleAppMain: Initializing Spring root WebApplicationContext
2018/04/03 01:11:39 | jvm 1 | Start loading Spring context...
2018/04/03 01:11:45 | wrapper | --> Wrapper Started as Console
2018/04/03 01:11:45 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.32
2018/04/03 01:11:45 | wrapper | Copyright (C) 1999-2017 Tanuki Software, Ltd. All Rights Reserved.
2018/04/03 01:11:45 | wrapper | http://wrapper.tanukisoftware.com
2018/04/03 01:11:45 | wrapper | Licensed to Hewlett-Packard Company for Octane
2018/04/03 01:11:45 | wrapper |
2018/04/03 01:11:45 | wrapper | Launching a JVM...
2018/04/03 01:11:45 | jvm 1 | -XX:CMSInitiatingOccupancyFraction=80 -XX:+CMSScavengeBeforeRemark -XX:+ExplicitGCInvokesConcurrent -XX:+HeapDumpOnOutOfMemoryError -XX:InitialHeapSize=4294967296 -XX:MaxHeapSize=4294967296 -XX:MaxNewSize=2147483648 -XX:MaxTenuringThreshold=6 -XX:NewRatio=2 -XX:OldPLABSize=16 -XX:+PrintCommandLineFlags -XX:-UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:+UseParNewGC
2018/04/03 01:11:45 | jvm 1 | WrapperManager: Initializing...
2018/04/03 01:11:46 | jvm 1 | 2018-04-03 01:11:46.162:INFO::WrapperSimpleAppMain: Logging initialized @687ms
2018/04/03 01:11:46 | jvm 1 | Starting server configuration.
2018/04/03 01:11:46 | jvm 1 | Reading the list of configuration files from: /opt/octane/server/conf/start.ini
2018/04/03 01:11:46 | jvm 1 | Reading configuration from: /opt/octane/server/conf/jetty.xml
2018/04/03 01:11:46 | jvm 1 | Reading configuration from: /opt/octane/server/conf/jetty-deploy.xml
2018/04/03 01:11:46 | jvm 1 | Reading configuration from: /opt/octane/server/conf/jetty-rewrite.xml
2018/04/03 01:11:46 | jvm 1 | Reading configuration from: /opt/octane/server/conf/jetty-stats.xml
2018/04/03 01:11:46 | jvm 1 | Server configured succesfully.
2018/04/03 01:11:46 | jvm 1 | Starting HTTP server.
2018/04/03 01:11:46 | jvm 1 | 2018-04-03 01:11:46.869:INFO:oejs.Server:WrapperSimpleAppMain: jetty-9.2.9.v20150224
2018/04/03 01:11:47 | jvm 1 | 2018-04-03 01:11:47.073:INFO:oejdp.ScanningAppProvider:WrapperSimpleAppMain: Deployment monitor [file:/opt/octane/webapps/] at interval 0
2018/04/03 01:11:52 | jvm 1 | ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
2018/04/03 01:11:52 | jvm 1 | 2018-04-03 01:11:52.642:INFO:root:WrapperSimpleAppMain: Initializing Spring root WebApplicationContext
2018/04/03 01:11:53 | jvm 1 | Start loading Spring context...
2018/04/03 01:13:03 | jvm 1 | Spring context loaded in 83810ms
2018/04/03 01:13:03 | jvm 1 | total of bean definitions: 36879
2018/04/03 01:13:04 | jvm 1 | Starting server setup
2018/04/03 01:13:04 | jvm 1 | Loading Apache Log4j configuration from here: /opt/octane/conf/log4j2-conf.xml
2018/04/03 01:13:05 | jvm 1 | Loading octane configuration from /opt/octane/conf/setup.xml
2018/04/03 01:13:05 | jvm 1 | getting setup sync status from file: /opt/octane/repo/storage/site/setup_sync_file.txt
2018/04/03 01:13:05 | jvm 1 | continuing setup as CREATE_NEW
2018/04/03 01:13:05 | jvm 1 |
2018/04/03 01:13:05 | jvm 1 | -------------------------
2018/04/03 01:13:05 | jvm 1 | Validating...
2018/04/03 01:13:05 | jvm 1 | -------------------------
2018/04/03 01:13:05 | jvm 1 | * Memory
2018/04/03 01:13:05 | jvm 1 | * Mandatory parameters
2018/04/03 01:13:05 | jvm 1 | * ElasticSearch connection
2018/04/03 01:13:12 | jvm 1 | FAILED !!!!!!!!!!!!
2018/04/03 01:13:12 | jvm 1 |
2018/04/03 01:13:12 | jvm 1 | ERROR: Validation failed !
2018/04/03 01:13:12 | jvm 1 |
2018/04/03 01:13:12 | jvm 1 |
2018/04/03 01:13:12 | jvm 1 | Validator description: ElasticSearch connection
2018/04/03 01:13:12 | jvm 1 | Validation error: Elastic search not accessible with the parameters provided by the setup file. Hosts: 192.168.59.105, Port: 9300, Cluster name: elasticsearch
2018/04/03 01:13:12 | jvm 1 |
2018/04/03 01:13:12 | jvm 1 | Possible ways to fix the problem:
2018/04/03 01:13:12 | jvm 1 | - Validate ElasticSearch machine is accessible from current machine.
2018/04/03 01:13:12 | jvm 1 | - Validate ElasticSearch ports are accessible.
2018/04/03 01:13:12 | jvm 1 | - Validate ElasticSearch configuration is correct.
2018/04/03 01:13:12 | jvm 1 |
2018/04/03 01:13:12 | jvm 1 |
2018/04/03 01:13:12 | jvm 1 |
2018/04/03 01:13:12 | jvm 1 | ************************************************************
2018/04/03 01:13:12 | jvm 1 | ************************************************************
2018/04/03 01:13:12 | jvm 1 | **
2018/04/03 01:13:12 | jvm 1 | ** Failed to initialize server.
2018/04/03 01:13:12 | jvm 1 | **
2018/04/03 01:13:12 | jvm 1 | ************************************************************
2018/04/03 01:13:12 | jvm 1 | ************************************************************
2018/04/03 01:13:12 | jvm 1 | **
2018/04/03 01:13:12 | jvm 1 | ** Error: com.hp.mqm.infra.common.exceptionhandling.MQMServerException: Validation failed:
2018/04/03 01:13:12 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 192.168.59.105, Port: 9300, Cluster name: elasticsearch
2018/04/03 01:13:12 | jvm 1 |
2018/04/03 01:13:12 | jvm 1 | ************************************************************
2018/04/03 01:13:12 | jvm 1 |
2018/04/03 01:13:12 | jvm 1 |
2018/04/03 01:13:12 | jvm 1 | com.hp.mqm.infra.common.exceptionhandling.MQMServerException: com.hp.mqm.infra.common.exceptionhandling.MQMServerException: Validation failed:
2018/04/03 01:13:12 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 192.168.59.105, Port: 9300, Cluster name: elasticsearch
2018/04/03 01:13:12 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.execute(Setup.java:64)
2018/04/03 01:13:12 | jvm 1 | at com.hp.mqm.infra.server.config.ServerConfiguration.init(ServerConfiguration.java:29)
2018/04/03 01:13:12 | jvm 1 | at com.hp.mqm.infra.server.listeners.MqmAppContextListener.contextInitialized(MqmAppContextListener.java:25)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:41)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:498)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:146)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:440)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:609)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:528)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.Scanner.scan(Scanner.java:391)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:560)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:235)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.server.Server.start(Server.java:387)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.server.Server.doStart(Server.java:354)
2018/04/03 01:13:12 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/04/03 01:13:12 | jvm 1 | at com.hp.alm.platform.launcher.ALMLauncher.startServer(ALMLauncher.java:77)
2018/04/03 01:13:12 | jvm 1 | at com.hp.alm.platform.launcher.ALMLauncher.main(ALMLauncher.java:33)
2018/04/03 01:13:12 | jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2018/04/03 01:13:12 | jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2018/04/03 01:13:12 | jvm 1 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2018/04/03 01:13:12 | jvm 1 | at java.lang.reflect.Method.invoke(Method.java:498)
2018/04/03 01:13:12 | jvm 1 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:325)
2018/04/03 01:13:12 | jvm 1 | at java.lang.Thread.run(Thread.java:748)
2018/04/03 01:13:12 | jvm 1 | Caused by: com.hp.mqm.infra.common.exceptionhandling.MQMServerException: Validation failed:
2018/04/03 01:13:12 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 192.168.59.105, Port: 9300, Cluster name: elasticsearch
2018/04/03 01:13:12 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.validationFailed(Setup.java:213)
2018/04/03 01:13:12 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.runValidationCheck(Setup.java:185)
2018/04/03 01:13:12 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.initSetup(Setup.java:131)
2018/04/03 01:13:12 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.doSetup(Setup.java:78)
2018/04/03 01:13:12 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.lambda$execute$26(Setup.java:59)
2018/04/03 01:13:12 | jvm 1 | at com.hp.mqm.infra.server.setup.ClusterSetupSynchronizer.sync(ClusterSetupSynchronizer.java:44)
2018/04/03 01:13:12 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.execute(Setup.java:48)
2018/04/03 01:13:12 | jvm 1 | ... 42 more
2018/04/03 01:13:12 | jvm 1 | Failed to start server, reason: com.hp.mqm.infra.common.exceptionhandling.MQMServerException: Validation failed:
2018/04/03 01:13:12 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 192.168.59.105, Port: 9300, Cluster name: elasticsearch. See logs for detailed information
2018/04/03 01:13:14 | wrapper | <-- Wrapper Stopped
2018/04/03 01:13:27 | jvm 1 | Spring context loaded in 94364ms
2018/04/03 01:13:27 | jvm 1 | total of bean definitions: 36879
2018/04/03 01:13:27 | jvm 1 | Starting server setup
2018/04/03 01:13:27 | jvm 1 | Loading Apache Log4j configuration from here: /opt/octane/conf/log4j2-conf.xml
2018/04/03 01:13:27 | jvm 1 | Loading octane configuration from /opt/octane/conf/setup.xml
2018/04/03 01:13:27 | jvm 1 | getting setup sync status from file: /opt/octane/repo/storage/site/setup_sync_file.txt
2018/04/03 01:13:27 | jvm 1 | continuing setup as CREATE_NEW
2018/04/03 01:13:28 | jvm 1 |
2018/04/03 01:13:28 | jvm 1 | -------------------------
2018/04/03 01:13:28 | jvm 1 | Validating...
2018/04/03 01:13:28 | jvm 1 | -------------------------
2018/04/03 01:13:28 | jvm 1 | * Memory
2018/04/03 01:13:28 | jvm 1 | * Mandatory parameters
2018/04/03 01:13:28 | jvm 1 | * ElasticSearch connection
2018/04/03 01:13:39 | jvm 1 | FAILED !!!!!!!!!!!!
2018/04/03 01:13:39 | jvm 1 |
2018/04/03 01:13:39 | jvm 1 | ERROR: Validation failed !
2018/04/03 01:13:39 | jvm 1 |
2018/04/03 01:13:39 | jvm 1 |
2018/04/03 01:13:39 | jvm 1 | Validator description: ElasticSearch connection
2018/04/03 01:13:39 | jvm 1 | Validation error: Elastic search not accessible with the parameters provided by the setup file. Hosts: 192.168.59.105, Port: 9300, Cluster name: elasticsearch
2018/04/03 01:13:39 | jvm 1 |
2018/04/03 01:13:39 | jvm 1 | Possible ways to fix the problem:
2018/04/03 01:13:39 | jvm 1 | - Validate ElasticSearch machine is accessible from current machine.
2018/04/03 01:13:39 | jvm 1 | - Validate ElasticSearch ports are accessible.
2018/04/03 01:13:39 | jvm 1 | - Validate ElasticSearch configuration is correct.
2018/04/03 01:13:39 | jvm 1 |
2018/04/03 01:13:39 | jvm 1 |
2018/04/03 01:13:39 | jvm 1 |
2018/04/03 01:13:39 | jvm 1 | ************************************************************
2018/04/03 01:13:39 | jvm 1 | ************************************************************
2018/04/03 01:13:39 | jvm 1 | **
2018/04/03 01:13:39 | jvm 1 | ** Failed to initialize server.
2018/04/03 01:13:39 | jvm 1 | **
2018/04/03 01:13:39 | jvm 1 | ************************************************************
2018/04/03 01:13:39 | jvm 1 | ************************************************************
2018/04/03 01:13:39 | jvm 1 | **
2018/04/03 01:13:39 | jvm 1 | ** Error: com.hp.mqm.infra.common.exceptionhandling.MQMServerException: Validation failed:
2018/04/03 01:13:39 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 192.168.59.105, Port: 9300, Cluster name: elasticsearch
2018/04/03 01:13:39 | jvm 1 |
2018/04/03 01:13:39 | jvm 1 | ************************************************************
2018/04/03 01:13:39 | jvm 1 |
2018/04/03 01:13:39 | jvm 1 |
2018/04/03 01:13:39 | jvm 1 | com.hp.mqm.infra.common.exceptionhandling.MQMServerException: com.hp.mqm.infra.common.exceptionhandling.MQMServerException: Validation failed:
2018/04/03 01:13:39 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 192.168.59.105, Port: 9300, Cluster name: elasticsearch
2018/04/03 01:13:39 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.execute(Setup.java:64)
2018/04/03 01:13:39 | jvm 1 | at com.hp.mqm.infra.server.config.ServerConfiguration.init(ServerConfiguration.java:29)
2018/04/03 01:13:39 | jvm 1 | at com.hp.mqm.infra.server.listeners.MqmAppContextListener.contextInitialized(MqmAppContextListener.java:25)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:41)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:498)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:146)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:440)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:609)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:528)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.Scanner.scan(Scanner.java:391)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:560)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:235)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.server.Server.start(Server.java:387)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.server.Server.doStart(Server.java:354)
2018/04/03 01:13:39 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/04/03 01:13:39 | jvm 1 | at com.hp.alm.platform.launcher.ALMLauncher.startServer(ALMLauncher.java:77)
2018/04/03 01:13:39 | jvm 1 | at com.hp.alm.platform.launcher.ALMLauncher.main(ALMLauncher.java:33)
2018/04/03 01:13:39 | jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2018/04/03 01:13:39 | jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2018/04/03 01:13:39 | jvm 1 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2018/04/03 01:13:39 | jvm 1 | at java.lang.reflect.Method.invoke(Method.java:498)
2018/04/03 01:13:39 | jvm 1 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:325)
2018/04/03 01:13:39 | jvm 1 | at java.lang.Thread.run(Thread.java:748)
2018/04/03 01:13:39 | jvm 1 | Caused by: com.hp.mqm.infra.common.exceptionhandling.MQMServerException: Validation failed:
2018/04/03 01:13:39 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 192.168.59.105, Port: 9300, Cluster name: elasticsearch
2018/04/03 01:13:39 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.validationFailed(Setup.java:213)
2018/04/03 01:13:39 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.runValidationCheck(Setup.java:185)
2018/04/03 01:13:39 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.initSetup(Setup.java:131)
2018/04/03 01:13:39 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.doSetup(Setup.java:78)
2018/04/03 01:13:39 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.lambda$execute$26(Setup.java:59)
2018/04/03 01:13:39 | jvm 1 | at com.hp.mqm.infra.server.setup.ClusterSetupSynchronizer.sync(ClusterSetupSynchronizer.java:44)
2018/04/03 01:13:39 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.execute(Setup.java:48)
2018/04/03 01:13:39 | jvm 1 | ... 42 more
2018/04/03 01:13:39 | jvm 1 | Failed to start server, reason: com.hp.mqm.infra.common.exceptionhandling.MQMServerException: Validation failed:
2018/04/03 01:13:39 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 192.168.59.105, Port: 9300, Cluster name: elasticsearch. See logs for detailed information
2018/04/03 01:13:41 | wrapper | <-- Wrapper Stopped"

 

Although I inputted the correct parameters for elasticsearch, it still gaves me the error. I already did a fresh install of the elasticsearch on my end but still same error. 

Please help me.

Thank you.

 

 

 

0 Likes
1 Solution

Accepted Solutions
Ziv_Birer Super Contributor.
Super Contributor.

Re: Stuck at Configuring ALM Octane - Wrong elasticsearch parameters

Jump to solution

Hi,

My name is Ziv Birer and I am from Octane R&D. I will be happy to assist you.

The issue that you have is that octane server fail to connect ot elasticsearch.

The common cause to this problem is missing parameters in elasticsearch configuration file (elasticsearch.yml). Please validate that you added the parameters that octane require according to 

https://softwaresupport.hpe.com/km/KM02494295

 

If you did and you still have problems, please:

(1) Send us setup.xml and octane.yml from octane 'conf' folder.

(2) Send us updated wrapper.log from 'log' folder.

(3) Send us 'elasticsearch.yml' from each elastic server machine.

 

Best regards,

Ziv

 

6 Replies
Ziv_Birer Super Contributor.
Super Contributor.

Re: Stuck at Configuring ALM Octane - Wrong elasticsearch parameters

Jump to solution

Hi,

My name is Ziv Birer and I am from Octane R&D. I will be happy to assist you.

The issue that you have is that octane server fail to connect ot elasticsearch.

The common cause to this problem is missing parameters in elasticsearch configuration file (elasticsearch.yml). Please validate that you added the parameters that octane require according to 

https://softwaresupport.hpe.com/km/KM02494295

 

If you did and you still have problems, please:

(1) Send us setup.xml and octane.yml from octane 'conf' folder.

(2) Send us updated wrapper.log from 'log' folder.

(3) Send us 'elasticsearch.yml' from each elastic server machine.

 

Best regards,

Ziv

 

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: Stuck at Configuring ALM Octane - Wrong elasticsearch parameters

Jump to solution

Hi Julian

I work at Micro Focus Professionnal Services. I faced and solved the same issue at a customer site.

Both port 9200 and 9300 Elasticsearch host ports must be accessible from ALM Octane server.
(Checking HTTP connection through curl on port 9200 does not suffice).

Ensure you can connect through telnet on port 9300 too from ALM Octane server.

Regards

Laurent

0 Likes
Contributor.. WiscoWorm Contributor..
Contributor..

Re: Stuck at Configuring ALM Octane - Wrong elasticsearch parameters

Jump to solution

Hi Laurent - I verified that I can use CURL method with port 9200 but how do I verify TELNET method with port 9300?  I have been told that we wouldn't be blocking these ports internally within our firewall.  I have the same issue as the above user (Julian) and the wrapper.log file says, "Elastic search not accessible with the parameters provided by the setup file."  Any help you can provide would be appreciated.  Thank you!

0 Likes
Ziv_Birer Super Contributor.
Super Contributor.

Re: Stuck at Configuring ALM Octane - Wrong elasticsearch parameters

Jump to solution

Hi,

Please verify tat that elasticsearch.yml is configured according https://softwaresupport.hpe.com/km/KM02494295

Please also verify that setup.xml have correct values for elasticsearch.

You can TELNET to port 9300 of elastic machine just to see that someone listen to that port. The port is used for binary messages so you can't send any message to see if you get valid response.

 

If you still have problems, please:

1. Attach entire 'conf' folder (as ZIP)

2. Attach entire 'log' folder

3. Attach elasticsearch.yml

4. Attach output of TELNET elastic 9300 (so we can see if connection was refused or not and what is the error message).

 

Regards,

Ziv

0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: Stuck at Configuring ALM Octane - Wrong elasticsearch parameters

Jump to solution

Type :
telnet your.elasticsearch.domain 9300
Where your.elasticsearch.domain is the hostname of your elasticsearch host (or it could be an IP address instead)

If it doesn't answer, it means 9300 port is not accessible (blocked by a firewall).


Regards

Laurent

 

474240 Trusted Contributor.
Trusted Contributor.

Re: Stuck at Configuring ALM Octane - Wrong elasticsearch parameters

Jump to solution

HI Ziv,

 

We have upgraded the Elastic Search , but we have not understand what we need to do in the below steps. Could you please help on this.

 

  1. Create index template

Replace num_shards and num_replicas in the template below with the values you removed from the elasticsearch.yml file earlier.

PUT _template/mqm_index_template

{

"order": 0,

"template": "mqm*",

"settings": {

    "index": {

      "number_of_shards": "num_shards",

      "number_of_replicas": "num_replicas"

    }

},

"mappings": {},

"aliases": {}

}

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.