Ziv_Birer Super Contributor.
Super Contributor.

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

Hi,

 

Good progress!

Please attach octane.yml from /opt/octane/conf

Please also attach /opt/octane/log/wrapper.log (if exists).

-- Ziv

0 Likes
Highlighted
aranjan Absent Member.
Absent Member.

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

Hi,

here is the ocane.yml file view please check thisoctyml.JPG

 

 

 

 

0 Likes
Ziv_Birer Super Contributor.
Super Contributor.

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

Hi,

The value of 'serverDomain' in octane.yml can not be IP address.

It must be real domain like 'company.org'.

Please:

1. modify the value

2. Restart octane by command: service HPALM restart

3. Wait 3 minutes and see if you can connect to octane by open brower and entering 'http://<machine>:8080/ui'. IMPORTANT: do not use IP address instead of machine in this url.

4. If this does not work, please

- attach octane.yml

- wrapper.log

- screenshort of the brower

 

By the way - you can attach files and not just screenshots. 

-- Ziv

aranjan Absent Member.
Absent Member.

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

HI, please tell me thew meaning of real domain as welll as what to u mean by machine in this url.

here is creenshot of octane.yml

tyu.JPG

 

 

0 Likes
aranjan Absent Member.
Absent Member.

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

here is wrapper logtre.JPG

 

 

 

 

0 Likes
Ziv_Birer Super Contributor.
Super Contributor.

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

Hi,

domain - if octane server machine is called server.arajan.com than the domain is arajan.com, It is the domain of network.

machine - it is the name of the machine in the network. If the machine name is server.arajan.com than the url is http://server.arajan.com:8080/ui

About wrapper.log - It seems that it is only part of the file. Can you attach all the file. You don't need to attach screenshot. You can attach also text files.

aranjan Absent Member.
Absent Member.

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

Hi,

Thanks for your help,

after setiing up the domain and using that address of machine i am able to see the octane login page, but when i use to give correct crediential the it starts opeing another page but error occurs. here i am also going to attach that error page also the text file of that "wrapper.log" kindly check and please give solution.

After giving use name and password erro occurAfter giving use name and password erro occur

I have attached the drive link for  wrapper.log complete text file . please check and let me know if u need anything else to resolve this issue.

https://drive.google.com/file/d/0B8hIfbkZizveSldIMVRGNkdmTXM/view

 

Regards,

Alok Ranjan

0 Likes
aranjan Absent Member.
Absent Member.

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

also the saas verison of this octane is not getting launched. same error occuring for saas version launch. so please help

0 Likes
Ziv_Birer Super Contributor.
Super Contributor.

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

Hi,

I don't see real problem from wrapper.log 

I assume there is an issue in the domain information that you configured.

 

Can we have a meeting with you in which we can see your screen?

If yes - do you have some virtual meeting tool that you can use to set a meeting with us in which we will see your screen?

-- Ziv

 

0 Likes
aranjan Absent Member.
Absent Member.

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

hi,

sure we can meeting. I will let u know in 1 hr.

Thanks

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

If you want our assistance, please send an email directly to me: Private Info Erased to schedule a mutually convinient time.

0 Likes
Member.. stime01
Member..

Re: Problem continued : i need help regarding connection issue with elesticsearch parameters.

Hi 

i have the same issue with elasticsearch, I tryed to install ALM Octane and i have this message:

-------------------------
2018/06/11 16:39:36 | jvm 1 | Validating...
2018/06/11 16:39:36 | jvm 1 | -------------------------
2018/06/11 16:39:36 | jvm 1 | * Memory - SUCCESS (1 ms)
2018/06/11 16:39:36 | jvm 1 | * Mandatory parameters - SUCCESS (6 ms)
2018/06/11 16:39:36 | jvm 1 | * ElasticSearch connection
2018/06/11 16:39:47 | jvm 1 | - FAILED !!!!!!!!!!!! (10645 ms)
2018/06/11 16:39:47 | jvm 1 |
2018/06/11 16:39:47 | jvm 1 | ERROR: Validation failed !
2018/06/11 16:39:47 | jvm 1 |
2018/06/11 16:39:47 | jvm 1 |
2018/06/11 16:39:47 | jvm 1 | Validator description: ElasticSearch connection
2018/06/11 16:39:47 | jvm 1 | Validation error: Elastic search not accessible with the parameters provided by the setup file. Hosts: 10.117.67.181, Port: 9200, Cluster name: elasticsearch. Error: None of the configured nodes are available: [{#transport#-1}{10.117.67.181}{10.117.67.181:9200}]
2018/06/11 16:39:47 | jvm 1 |
2018/06/11 16:39:47 | jvm 1 | Possible ways to fix the problem:
2018/06/11 16:39:47 | jvm 1 | - Validate ElasticSearch machine is configured according KM02494295.
2018/06/11 16:39:47 | jvm 1 | - Validate ElasticSearch machine is accessible from current machine.
2018/06/11 16:39:47 | jvm 1 | - Validate ElasticSearch ports are accessible.
2018/06/11 16:39:47 | jvm 1 | - Validate ElasticSearch configuration is correct.
2018/06/11 16:39:47 | jvm 1 |
2018/06/11 16:39:47 | jvm 1 |
2018/06/11 16:39:47 | jvm 1 |
2018/06/11 16:39:47 | jvm 1 | ----------------------
2018/06/11 16:39:47 | jvm 1 | Stack trace (for R&D):
2018/06/11 16:39:47 | jvm 1 | ----------------------
2018/06/11 16:39:47 | jvm 1 |
2018/06/11 16:39:47 | jvm 1 | com.hp.mqm.infra.common.exceptionhandling.MQMServerException: Validation failed:
2018/06/11 16:39:47 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 10.117.67.181, Port: 9200, Cluster name: elasticsearch. Error: None of the configured nodes are available: [{#transport#-1}{10.117.67.181}{10.117.67.181:9200}]
2018/06/11 16:39:47 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.validationFailed(Setup.java:210)
2018/06/11 16:39:47 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.runValidationCheck(Setup.java:182)
2018/06/11 16:39:47 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.initSetup(Setup.java:130)
2018/06/11 16:39:47 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.doSetup(Setup.java:74)
2018/06/11 16:39:47 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.lambda$execute$17(Setup.java:55)
2018/06/11 16:39:47 | jvm 1 | at com.hp.mqm.infra.server.setup.ClusterSetupSynchronizer.sync(ClusterSetupSynchronizer.java:44)
2018/06/11 16:39:47 | jvm 1 | at com.hp.mqm.infra.server.setup.Setup.execute(Setup.java:54)
2018/06/11 16:39:47 | jvm 1 | at com.hp.mqm.infra.server.config.ServerConfiguration.init(ServerConfiguration.java:29)
2018/06/11 16:39:47 | jvm 1 | at com.hp.mqm.infra.server.listeners.MqmAppContextListener.contextInitialized(MqmAppContextListener.java:27)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:41)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:498)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:146)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:440)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:609)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:528)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.Scanner.scan(Scanner.java:391)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:560)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:235)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.server.Server.start(Server.java:387)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.server.Server.doStart(Server.java:354)
2018/06/11 16:39:47 | jvm 1 | at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018/06/11 16:39:47 | jvm 1 | at com.hp.alm.platform.launcher.ALMLauncher.startServer(ALMLauncher.java:77)
2018/06/11 16:39:47 | jvm 1 | at com.hp.alm.platform.launcher.ALMLauncher.main(ALMLauncher.java:33)
2018/06/11 16:39:47 | jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2018/06/11 16:39:47 | jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2018/06/11 16:39:47 | jvm 1 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2018/06/11 16:39:47 | jvm 1 | at java.lang.reflect.Method.invoke(Method.java:498)
2018/06/11 16:39:47 | jvm 1 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:325)
2018/06/11 16:39:47 | jvm 1 | at java.lang.Thread.run(Thread.java:748)
2018/06/11 16:39:47 | jvm 1 | ERROR: Validation failed:
2018/06/11 16:39:47 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 10.117.67.181, Port: 9200, Cluster name: elasticsearch. Error: None of the configured nodes are available: [{#transport#-1}{10.117.67.181}{10.117.67.181:9200}], exception=Validation failed:
2018/06/11 16:39:47 | jvm 1 | Elastic search not accessible with the parameters provided by the setup file. Hosts: 10.117.67.181, Port: 9200, Cluster name: elasticsearch. Error: None of the configured nodes are available: [{#transport#-1}{10.117.67.181}{10.117.67.181:9200}]
2018/06/11 16:39:47 | jvm 1 |
2018/06/11 16:39:47 | jvm 1 |
2018/06/11 16:39:47 | jvm 1 | ************************************************************
2018/06/11 16:39:47 | jvm 1 | ************************************************************
2018/06/11 16:39:47 | jvm 1 | **
2018/06/11 16:39:47 | jvm 1 | ** Server setup failed.
2018/06/11 16:39:47 | jvm 1 | ** IMPORTANT - Please:
2018/06/11 16:39:47 | jvm 1 | ** 1. Stop all server nodes if cluster exists
2018/06/11 16:39:47 | jvm 1 | ** 2. Delete file <repository-folder>/storage/site/setup_sync_file.txt
2018/06/11 16:39:47 | jvm 1 | ** 3. Fix the problem
2018/06/11 16:39:47 | jvm 1 | ** 4. Start again server
2018/06/11 16:39:47 | jvm 1 | **

 

can you help me please

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.