Exalitics Oracle VM Server Fails To Join The Server Pool After Reimaging It with "Transport endpoint is not connected while mounting /dev/mapper/ovspoolfs"
(Doc ID 2336895.1)
Last updated on JUNE 18, 2020
Applies to:Oracle Cloud Infrastructure - Version N/A and later
Oracle VM - Version 3.2.9 to 3.3.5 [Release OVM32 to OVM33]
After re-imaging the Exalitics Oracle VM Server, it can not be added back into the server pool, in this scenario server was deleted from the Oracle VM Manager, the re-image was done, then the server was discovered from the Oracle VM GUI and finally attempted to be moved into the server pool which failed with the following message:
[2017-11-08 15:24:28 12951] DEBUG (o2cb:174) configure_server_for_cluster error: Command: ['mount', '/dev/mapper/ovspoolfs', '/poolfsmnt <<<<<<========== 0004fb00000500009e36376f9b6c4f68'] failed (1): stderr: mount.ocfs2: Transport endpoint is not connected while mounting /dev/mapper/ovspoolfs on /poolfsmnt /0004fb00000500009e36376f9b6c4f68. Check 'dmesg' for more information on this error.stdout:
Before the server was deleted from the Oracle VM Manager GUI to re-image it the O2CB HEARTBEAT THRESHOLD was changed from default value of 151 to 43201 as indicated on the below document.
Increase O2CB Cluster Heartbeat Timeout on Exalogic Virtual (Doc ID 1995593.1)
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