My Oracle Support Banner

Oracle Linux / Oracle VM Servers rebooted with error "iscsid: connect to X.X.X.X:X failed (No route to host)" (Doc ID 2082697.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle VM - Version 3.0.1 and later
Linux OS - Version Oracle Linux 4.4 and later
Linux x86-64

Symptoms

 On Oracle VM 3.X.X, or Oracle Linux making use of the Oracle Clustered File System version 2 (OCFS2) and an ISCSI file system as pool device (OVM) or heartbeat device (OL), servers are getting in a reboot loop, printing this kind of error messages :

Feb 10 11:05:26 ovs1 iscsid: connect to 192.168.100.2:3260 failed (No route to host)
Feb 10 11:05:26 ovs1 iscsid: connect to 192.168.100.5:3260 failed (No route to host)
Feb 10 11:05:26 ovs1 iscsid: connect to 192.168.100.2:3260 failed (No route to host)

 On the other nodes part of the server pool for Oracle VM or on the other nodes part of the OCFS2 cluster on Oracle Linux, the following kind of errors get logged in the /var/log/messages :

Feb 10 10:09:24 ovs2 kernel: o2cb: o2dlm has evicted node 0 from domain ocfs2

 Followed by a node reboot on the node that prints the iscsid error message. This can possibly be a reboot loop.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.