Oracle VM (OVM) (MOSC)

MOSC Banner

ovs-agent.log error after host ip changed

edited Mar 22, 2013 9:47AM in Oracle VM (OVM) (MOSC) 1 commentAnswered
I had to rebuild a vm server and assign a new ip to it.  The host name remained the same.
Seeing the following error in the ovs-agent.log file.

[2013-03-01 13:50:35 7587] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
[2013-03-01 13:50:48 7615] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
[2013-03-01 13:51:02 7639] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
[2013-03-01 13:51:15 7658] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')


192.168.0.40 was the old address. 

VM Server is 3.2.2 and VM Manager is at version 3.2.2


I think the ip address is hanging around in some config file.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center