3:32 a.m.
sorry, I used 192.168.223 to replace 192.168.122.65, forget tell you,
hosted-engine.ovirt.com=192.168.122.91, it is engine VM, visit hosted-engine.ovirt.com
show me web UI. 发自网易邮箱手机版 在2018年04月26日 14:52，Martin Sivak 写道： Hi, > hosted-engine1 :
192.168.122.66 > hosted-engine2 : 192.168.122.223 But you said in an earlier email
that: > I hava two node, A:192.168.122.65 , B:192.168.122.66 Make sure your names
resolve properly. So far it does exactly what it is supposed to do - when the engine is
unreachable, it tries restarting it. Did you really use hosted-engine.ovirt.com as the
fqdn? Are you sure it resolves to whatever IP the VM has (192.168.122.91)? Maybe you used
/etc/hosts to configure the name on the first host and in the VM, but miss the record on
the second host? What does $(host hosted-engine.ovirt.com) show you? > I can not visit
web UI, but my engine VM is run, i can login it. engine has > some error > >
VdsIdVDSCommandParametersBase:{hostId='1b5f799a-125d-4f4e-8aef-cb2ecdd63136'})'
> execution failed: java.net.NoRouteToHostException: No route to host I told you
before. This is normal as it is trying to figure out whether the host is up. Best regards
Martin Sivak On Thu, Apr 26, 2018 at 4:14 AM, <dhy336(a)sina.com> wrote: > engine
VM：192.168.122.91 > hosted-engine1 : 192.168.122.66 > hosted-engine2 :
192.168.122.223 > > I can not visit web UI, but my engine VM is run, i can login it.
engine has > some error > > 2018-04-25 18:35:03,401+08 INFO >
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) > []
Connecting to hosted-engine1/192.168.122.66 > 2018-04-25 18:35:06,411+08 ERROR >
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] >
(EE-ManagedThreadFactory-engineScheduled-Thread-2) [] Command >
'GetAllVmStatsVDSCommand(HostName = hosted-engine1, > >
VdsIdVDSCommandParametersBase:{hostId='1b5f799a-125d-4f4e-8aef-cb2ecdd63136'})'
> execution failed: java.net.NoRouteToHostException: No route to host >
----------------------------------------------------------------------------------------------------------------------------------------
> [root@hosted-engine2 ~]# hosted-engine --check-liveliness > Hosted Engine is not
up! >
-----------------------------------------------------------------------------------------------------------------------------------------
> [root@hosted-engine2 ~]# curl >
http://hosted-engine.ovirt.com/ovirt-engine/services/health >
<html><head><title>Error</title></head><body>404 - Not
Found</body></html> > > Note： this command is blocked ,it takes 5
minutes >
-----------------------------------------------------------------------------------------------------------------------------------------
> --== Host 1 status ==-- > > conf_on_shared_storage : True >
Status up-to-date : False > Hostname :
hosted-engine1 > Host ID : 1 > Engine status
: unknown stale-data > Score : 3400 > stopped
: False > Local maintenance : False >
crc32 : 1eae8968 > local_conf_timestamp :
48907 > Host timestamp : 48907 > Extra metadata (valid at
timestamp): > metadata_parse_version=1 > metadata_feature_version=1 >
timestamp=48907 (Thu Apr 26 01:57:14 2018) > host-id=1 > score=3400 >
vm_conf_refresh_time=48907 (Thu Apr 26 01:57:15 2018) > conf_on_shared_storage=True
> maintenance=False > state=EngineUp > stopped=False > > > --== Host 2
status ==-- > > conf_on_shared_storage : True > Status up-to-date
: True > Hostname : hosted-engine2 > Host ID
: 2 > Engine status :
{"reason": "failed liveliness check", > "health":
"bad", "vm": "up", "detail": "Up"} >
Score : 3000 > stopped : False
> Local maintenance : False > crc32 :
1b92756d > local_conf_timestamp : 44057 > Host timestamp
: 44057 > Extra metadata (valid at timestamp): > metadata_parse_version=1 >
metadata_feature_version=1 > timestamp=44057 (Thu Apr 26 02:00:57 2018) > host-id=2
> score=3000 > vm_conf_refresh_time=44057 (Thu Apr 26 02:00:57 2018) >
conf_on_shared_storage=True > maintenance=False > state=EngineStarting >
stopped=False > > > > > > > ----- Original Message -----ovirt >
From: Martin Sivak <msivak(a)redhat.com> > To: dhy336 <dhy336(a)sina.com> >
Cc: users <users(a)ovirt.org> > Subject: Re: Re: [ovirt-users] 回复：Re: Hosted-engine
can not_switch > Date: 2018-04-25 20:41 > > >> 2018-04-25 18:35:06,411+08
ERROR >> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-2) [] Command >>
'GetAllVmStatsVDSCommand(HostName = hosted-engine1, >> >>
VdsIdVDSCommandParametersBase:{hostId='1b5f799a-125d-4f4e-8aef-cb2ecdd63136'})'
>> execution failed: java.net.NoRouteToHostException: No route to host > This is
expected and normal. The ovirt-engine service is trying to > find out whether host A is
still unreachable or not. This is not the > issue you are looking for. >>
192.168.122.66 has been powered off, and hosted engine VM run in >> 192.168.122.223,
I think engine should connect to 192.168.122.223, > You are mixing the IP of the engine
VM and the IP of a host. The > engine runs in VM with stable .122.223 (independent on
which host the > VM runs at) and manages two hosts .122.65 and .122.66. The engine >
constantly monitors all its hosts and that means it is trying to > connect to them
every now and then. > Please execute the two following commands on Host B and show us
the > results (use the proper fqdn): > $(hosted-engine --check-liveliness) >
$(curl http://{fqdn}/ovirt-engine/services/health) > Best regards > Martin Sivak
> On Wed, Apr 25, 2018 at 2:34 PM, <dhy336(a)sina.com> wrote: >> I login in
engine VM by (#hosted-engine --console) , I find ovirt-engine >> process. and I find
some error in /var/log/ovirt-engine/engine.log >> >> 192.168.122.66 has been
powered off, and hosted engine VM run in >> 192.168.122.223, I think engine should
connect to 192.168.122.223, >> >> >> 2018-04-25 18:35:03,401+08 INFO
>> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
>> [] Connecting to hosted-engine1/192.168.122.66 >> 2018-04-25
18:35:06,411+08 ERROR >>
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] >>
(EE-ManagedThreadFactory-engineScheduled-Thread-2) [] Command >> 'Get