Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

VM Manager - add new server - status unreachable

739112Dec 4 2009 — edited Dec 7 2009
I've used VM Manager (2.2.0) to get two servers successfully added to my server pool but when I add the third Oracle VM Server (2.2.0) it immediately goes to status unreachable. I'm using the exact procedure I used to add the second server but I don't know why tihs one is not working. I've even completely re-installed Oracle VM Server and I get the same results.

From the ocj4.log on the VM Manager:
2009-12-04 11:59:42.376 NOTIFICATION Judging the server ftl-bld1-9.moss.local ha
s been managed or not...
2009-12-04 11:59:42.499 WARNING failed: <Exception: master_ip has not been registered yet.>

StackTrace:
File "/opt/ovs-agent-2.3/OVSSiteRMServer.py", line 357, in get_master_ip
raise Exception("*master_ip has not been registered yet*.")

From the ovs_query.log on the VM Server:
"2009-12-04 12:00:10" INFO=> get_rpm_version: success:agent_version=2.3-19
"2009-12-04 12:00:10" INFO=> get_agent_version: success:agent_version=2.3-19
"2009-12-04 12:00:11" ERROR=> get_master_ip: failed. => <Exception: master_ip has not been registered yet.>

StackTrace:
File "/opt/ovs-agent-2.3/OVSSiteRMServer.py", line 357, in get_master_ip
raise Exception("*master_ip has not been registered yet*.")

"2009-12-04 12:00:16" INFO=> get_rpm_version: success:agent_version=2.3-19
"2009-12-04 12:00:16" INFO=> get_agent_version: success:agent_version=2.3-19
"2009-12-04 12:00:16" ERROR=> get_master_ip: failed. => <Exception: master_ip has not been registered yet.>

From the ovs_root.log on the VM Server:
"2009-12-04 11:22:17" INFO=> clusterm_init_root_sr: {"status": "SUCC", "value": {"cluster_root_dir": "/var/ovs/mount/55D577
ED39C3427596C02A9571BDEEC3"}}
"2009-12-04 11:22:18" INFO=> ha_set_shutdown_mode: inform master agent, leave shutdown mode.
"2009-12-04 11:22:18" DEBUG=> ha_set_shutdown_mode: no master access information available.
"2009-12-04 11:22:18" INFO=> ha_set_shutdown_mode: remove shutdown mode flag.
"2009-12-04 11:44:14" INFO=> OVSAgentServer start serving!
"2009-12-04 11:44:15" INFO=> clusterm_init_root_sr: {"status": "SUCC", "value": {"cluster_root_dir": "/var/ovs/mount/55D577
ED39C3427596C02A9571BDEEC3"}}
"2009-12-04 11:44:16" INFO=> ha_set_shutdown_mode: inform master agent, leave shutdown mode.
"2009-12-04 11:44:16" DEBUG=> ha_set_shutdown_mode: no master access information available.
"2009-12-04 11:44:16" INFO=> ha_set_shutdown_mode: remove shutdown mode flag.

Can someone please help explain what this master ip is, where I can define it, and how to overcome this problem?
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jan 4 2010
Added on Dec 4 2009
7 comments
2,746 views