Spoke connection failed (1865 Views)
Reply
Occasional Contributor
TomerLevy
Posts: 4
Registered: ‎04-11-2011
Message 1 of 6 (1,865 Views)

Spoke connection failed


Hi,

I have a clean install of HP SA and when opening the UI, it fails with the following error:

com.opsware.rmi.SpokeConnectionException: Spoke connection failed.

The UI opens up but it is unable to view "Unmanaged Servers".

The only relevant thread talked about proxy settings which I don't have both on IE and on the UI console.

I did tcpdump and keep on receiving these ICMP packets when ever I try to scan for machines.

"ICMP host truth unreachable - admin prohibited, length 84"


This is the debug from the Java debug console
com.jcraft.jsch.JSchException: Gateway proxy java.net.ConnectException: Connection timed out: connect

Java Web Start 1.4.2_15 Console, started Mon Apr 11 11:59:30 IDT 2011
Java 2 Runtime Environment: Version 1.6.0_18 by Sun Microsystems Inc.
Logging to file: C:\Users\yigal.INTIGUA\Application Data\HP BSA\deployment\log\javaws\javaws1927178846567383564.log
Apr 11, 2011 11:59:31 AM java.util.prefs.WindowsPreferences
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
SEVERE Hub initialization failed:
com.opsware.rmi.SpokeConnectionException: Spoke connection failed.
at com.opsware.rmi.ClientEndpoint.connect(ClientEndpoint.java:230)
at com.opsware.rmi.ClientEndpoint.initialize(ClientEndpoint.java:160)
at com.opsware.ngui.client.SpokeClient.initialize(Unknown Source)
at com.opsware.ngui.client.ClientApp.initSpoke(Unknown Source)
at com.opsware.ngui.client.ClientApp.postLoginInit(Unknown Source)
at com.opsware.ngui.client.ClientApp.loginAndStartup(Unknown Source)
at com.opsware.ngui.client.ClientApp.doLogin(Unknown Source)
at com.opsware.ngui.main.NguiMain.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.continueLaunch(Unknown Source)
at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.jcraft.jsch.JSchException: Gateway proxy java.net.ConnectException: Connection timed out: connect
at com.opsware.rmi.GatewayProxy.connect(GatewayProxy.java:110)
at com.jcraft.jsch.Session.connect(Unknown Source)
at com.opsware.rmi.ClientEndpoint$HubSession.connect(ClientEndpoint.java:464)
at com.opsware.rmi.ClientEndpoint.bind(ClientEndpoint.java:308)
at com.opsware.rmi.ClientEndpoint.connect(ClientEndpoint.java:225)
... 18 more

WARNING getErrorsString(ErrorsSupport:-1): Details of handled exception:
java.lang.NullPointerException
at com.opsware.ngui.adt.model.HubClient.remoteExec(Unknown Source)
at com.opsware.ngui.adt.model.HubClient.remoteExec(Unknown Source)
at com.opsware.ngui.adt.model.RemoteDeploymentHelperStandIn.getGatewayDeviceForRealm(Unknown Source)
at com.opsware.ngui.adt.model.RemoteDeploymentHelperStandIn.retrieveHelper(Unknown Source)
at com.opsware.ngui.adt.model.RemoteDeploymentHelperStandIn.getDeploymentHelper(Unknown Source)
at com.opsware.ngui.adt.ui.ADTPanel$2.doWork(Unknown Source)
at com.opsware.ngui.common.support.ProgressDialog$1.run(Unknown Source)

WARNING getErrorsString(ErrorsSupport:-1): Details of handled exception:
java.lang.NullPointerException
at com.opsware.ngui.adt.model.HubClient.remoteExec(Unknown Source)
at com.opsware.ngui.adt.model.HubClient.remoteExec(Unknown Source)
at com.opsware.ngui.adt.model.RemoteDeploymentHelperStandIn.getGatewayDeviceForRealm(Unknown Source)
at com.opsware.ngui.adt.model.RemoteDeploymentHelperStandIn.retrieveHelper(Unknown Source)
at com.opsware.ngui.adt.model.RemoteDeploymentHelperStandIn.getDeploymentHelper(Unknown Source)
at com.opsware.ngui.adt.ui.ADTPanel$2.doWork(Unknown Source)
at com.opsware.ngui.common.support.ProgressDialog$1.run(Unknown Source)


Any help would be highly appreciated..
Occasional Visitor
Phil Nash
Posts: 1
Registered: ‎04-21-2011
Message 2 of 6 (1,865 Views)

Re: Spoke connection failed

Is your truth database up and running? Does the server that hosts truth, accept ICMP packets? On your core server, are there any errors shown when /etc/init.d/opsware-sas health is run?
Occasional Visitor
Bradley524
Posts: 4
Registered: ‎04-21-2011
Message 3 of 6 (1,865 Views)

Re: Spoke connection failed

Most of the time I find that this is caused by a blockage of the port 8080. This can be be done by a network filters/ ACLs. Another reason could be system firewalls. System Firewalls - Like IPtables or Windows firewalls will cause port 8080 not to speak to spoke (I had to say it). Lastly if your on your on Linux workstation then make sure you check your wrappers and/or SELinux.

Also if your using Putty ensure that the tunnel is setup for 8080. A good test is to command line or cmd windows and telnet coreip 8080.

Good Luck
Bradley
Frequent Advisor
ITRC_J
Posts: 80
Registered: ‎03-12-2009
Message 4 of 6 (1,865 Views)

Re: Spoke connection failed

This Error usually occurs due to Umask bit being set to u27 which should be u22 instead.

Fix:
1) Edit the following file:

/etc/rc.d/init.d/functions

Near the start of the file, locate "umask". By default, this is set to:

umask 022

If you are not seeing the above (e.g., you are seeing something else, such as "umask 027"), be sure to edit and make the correction, then save the file.

In order for this change to take effect, the server MUST be rebooted.

Be sure to also check these files for similar umask mistakes and set them to umask 022 if they are set otherwise:

/etc/profile
/etc/bashrc
/etc/profile.d/*



Regards,
Jay
Occasional Contributor
TomerLevy
Posts: 4
Registered: ‎04-11-2011
Message 5 of 6 (1,865 Views)

Re: Spoke connection failed

I actually installed the core again and the problem was solved. Thanks for your support!
Occasional Visitor
skeng
Posts: 2
Registered: ‎11-06-2013
Message 6 of 6 (887 Views)

Re: Spoke connection failed

I'm not sure if this thread is still open or if anyone is monitoring it... in any case, I hope someone would respond. Thanks in advance.

 

My instance of HPSA was working without any issues on this RHEL5.8 server. But after applying the system patches (non-kernel), I'm having problems connecting to the SA instance with the Java Client. I get this (Spoke connection failed) error everytime I try to connect to it. And ofcourse, one major thing that stopped working for us is ability to spawn server shell from SA client.

 

Has anyone come across this issue and if yes, what was the resolution. Your help would be greatly appreciated.

 

 

Exception:   com.opsware.rmi.SpokeConnectionException
Spoke connection failed.

Caused by:

Exception:   java.io.IOException
EOF while reading HTTP status line.

 

 

Thanks again,

-sk

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.