Unable to connect to Appliance URL. Java.net.NoRouteToHostExeption: No Route to host

[dykum]

It stopped 93% during installation of Morpheus, so I looked at the log and found the log as below

What should I do?

2025-02-28 16:48:20 WARN: Unable to connect to https://hpevmemanager.techi-test-domain.com. Trying again in 15 seconds...
java.net.NoRouteToHostException: No route to host
at java.base@21.0.4/sun.nio.ch.Net.connect0(Native Method)
at java.base@21.0.4/sun.nio.ch.Net.connect(Net.java:589)
at java.base@21.0.4/sun.nio.ch.Net.connect(Net.java:578)
at java.base@21.0.4/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:583)
at java.base@21.0.4/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base@21.0.4/java.net.Socket.connect(Socket.java:751)
at java.base@21.0.4/sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:304)
at java.base@21.0.4/sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:181)
at java.base@21.0.4/sun.net.NetworkClient.doConnect(NetworkClient.java:183)
at java.base@21.0.4/sun.net.www.http.HttpClient.openServer(HttpClient.java:531)
at java.base@21.0.4/sun.net.www.http.HttpClient.openServer(HttpClient.java:636)
at java.base@21.0.4/sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:264)
at java.base@21.0.4/sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:377)
at java.base@21.0.4/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:193)
at java.base@21.0.4/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1237)
at java.base@21.0.4/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1123)
at java.base@21.0.4/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:179)
at java.base@21.0.4/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1675)
at java.base@21.0.4/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1599)
at java.base@21.0.4/java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:531)
at java.base@21.0.4/sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:307)
at com.morpheusdata.mvm.console.util.MvmUtility.waitForWebappStart(MvmUtility.java:510)
at com.morpheusdata.mvm.console.util.MvmUtility.waitForWebappStart(MvmUtility.java:498)
at com.morpheusdata.mvm.console.InstallMorpheus.lambda$show$4(InstallMorpheus.java:351)
at java.base@21.0.4/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
at java.base@21.0.4/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base@21.0.4/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base@21.0.4/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base@21.0.4/java.lang.Thread.runWith(Thread.java:1596)
at java.base@21.0.4/java.lang.Thread.run(Thread.java:1583)
at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:896)
at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:872)

This is the hostnamectl

Static hostname: vmem-01
Icon name: computer-server
Chassis: server
Operating System: Ubuntu 22.04.5 LTS
Kernel: Linux 5.15.0-133-generic
Architecture: x86-64
Hardware Vendor: HPE
Hardware Model: ProLiant DL380 Gen11

This is the /etc/hosts

#127.0.0.1 localhost
10.10.11.2 vmem-01.techi-test-domain.com vmem-01
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

This is the /etc/resolv.conf

nameserver 10.10.11.2
#nameserver 168.126.63.1
search techi-test-domain.com

This is the /etc/bind/zones/db.techi-test-domain.com

 $TTL 604800
@ IN SOA techi-test-domain.com. root.techi-test-domain.com. (
2 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;

@ IN NS techi-test-domain.com.
techi-test-domain.com. IN A 10.10.11.2
hpevmemanager.techi-test-domain.com. IN A 10.10.11.75

This is the netplan setting.

network:
version: 2
ethernets:
ens15f0:
mtu: 9000
ens15f1:
mtu: 9000
bridges:
mgmt:
addresses:
- 10.10.11.2/24
nameservers:
addresses:
- 10.10.11.2
- 168.126.63.1
search:
- techi-test-domain.com
mtu: 9000
interfaces:
- bond0
openvswitch: {}
routes:
- to: default
via: 10.10.11.89
bonds:
bond0:
mtu: 9000
interfaces:
- ens15f0
- ens15f1
parameters:
mode: 802.3ad
lacp-rate: fast
transmit-hash-policy: layer2+3

nslookup 10.10.11.75 nslookup also give me the correct value

75.11.10.10.in-addr.arpa name = hpevmemanager.techi-test-domain.com.

I entered the morpheus settings as below.

IP Address: 10.10.11.75

Netmask: 255.255.255.0

Gateway: 10.10.11.89

DNS Server: 10.10.11.2

Appliance URL: https://hpevmemanager.techi-test-domain.com

Hostname: hpevmemanager

Image URI: file:///root/hpe-vme-8.0.3.1.qcow2

Management Interface: mgmt

[pkbin]

Hi @dykum ,

Could you please check if the hpevmemanager is accessible from the KVM host? 

Provide me the below command outputs to validate

#virsh list  --all
#nslookup hpevmemanager.techi-test-domain.com
#ping hpevmemanager.techi-test-domain.com
#ping hpevmemanager

Thanks 

[mnavada]

Hi,
I observed the two issues here.
1. Linux kernel is not updated. It is OLD.  it is 5.x
Execute "apt install -y linux-generic-hwe-22.04" to upgrade the kernel which will support GFS too. Once upgradation done, server needs to reboot. Check the kernel update by executing "hostnamectl"

2. While perforing "Morpheus Install", the following information provided.

Netmask: 255.255.255.0
Gateway: 10.10.11.89
DNS Server: 10.10.11.2
Appliance URL: https://hpevmemanager.techi-test-domain.com
Hostname: hpevmemanager
Image URI: file:///root/hpe-vme-8.0.3.1.qcow2
Management Interface: mgmt      < == this should be the interface name to which you have assign the static IP

Refer: https://hpevm-docs.morpheusdata.com/en/latest/vme_getting_started/vme_getting_started.html#installation

Hope this helps.

Manjunath

[mnavada]

@dykum ,

if you still finding the same issue after following my suggestion, please feel free to send an email to hpe-sw-trial-vmessentials@hpe.com
So, we can plan for remote session.