Oracle VM: Unable to Add New OVM Server To Pool with "o2cb: Bad IP Address" error
(Doc ID 2087861.1)
Last updated on DECEMBER 04, 2020
Applies to:
Oracle VM - Version 3.3.1 and laterOracle Cloud Infrastructure - Version N/A and later
Linux x86-64
Symptoms
Unable to add new fresh-installed OVM Server to Pool with "o2cb: Bad IP Address" error.
AdminServer.log:
<2015-07-03T18:11:44.957+0200> <Error> <com.oracle.ovm.mgr.api.job.InternalJob> <hostname> <AdminServer> <Odof Tcp Client Thread: /127.0.0.1:54321/32048233> <
[Fri Jul 03 18:11:44 CEST 2015] [Fri Jul 03 18:11:44 CEST 2015]
at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:502) at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:420)
...Server error: org.apache.xmlrpc.XmlRpcException: <type 'exceptions.RuntimeError'>:Command: ['/sbin/o2cb', '--config-file=/etc/ocfs2/cluster.conf', 'add-node', '--ip=', '--port=7777', '--number=0', 'bbd23c3b6a044fd0', 'hostname'] failed (1): stderr: o2cb: Bad IP Address ''
Changes
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 |
Changes |
Cause |
Solution |
References |