<div>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</div><div><br></div><div>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, </div><div><br></div><div><br></div><div><div>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</div><div>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</div><div>2018-04-25 18:35:06,411+08 INFO [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher] (EE-ManagedThreadFactory-engineScheduled-Thread-2) [] Failed to fetch vms info for host 'hosted-engine1' - skipping VMs monitoring.</div><div>2018-04-25 18:35:21,420+08 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to hosted-engine1/192.168.122.66</div><div>2018-04-25 18:35:24,430+08 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] Command 'GetAllVmStatsVDSCommand(HostName = hosted-engine1, VdsIdVDSCommandParametersBase:{hostId='1b5f799a-125d-4f4e-8aef-cb2ecdd63136'})' execution failed: java.net.NoRouteToHostException: No route to host</div><div>2018-04-25 18:35:24,431+08 INFO [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] Failed to fetch vms info for host 'hosted-engine1' - skipping VMs monitoring.</div><div>2018-04-25 18:35:39,438+08 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to hosted-engine1/192.168.122.66</div></div><div><br></div><div><br></div><div><br></div><div id="origbody"><div style="background: #f2f2f2;">----- Original Message -----<br>From: Martin Sivak <msivak@redhat.com><br>To: dhy336 <dhy336@sina.com><br>Cc: users <users@ovirt.org><br>Subject: Re: [ovirt-users] �ظ���Re: Hosted-engine can not_switch<br>Date: 2018-04-25 20:27<br></div><br><br>The engine will try connecting to all registered hosts all the time.<br>That is normal.<br>If your host can reach the engine then check whether it can reach<br>http://{fqdn}/ovirt-engine/services/health as that is what is used to<br>make sure the engine is alive.<br>Best regards<br>Martin Sivak<br>On Wed, Apr 25, 2018 at 2:15 PM, <dhy336@sina.com> wrote:<br>> Hi Martin,<br>><br>> thank you for answer<br>> my host can reach the engine, I confuse why engine connect to another host<br>> which has been power off by me?<br>><br>> ----- Original Message -----<br>> From: Martin Sivak <msivak@redhat.com><br>> To: dhy336 <dhy336@sina.com>, users <users@ovirt.org><br>> Subject: Re: Re: Re: Re: Re: Re: [ovirt-users] �ظ���Re: Hosted-engine can<br>> not_switch<br>> Date: 2018-04-25 19:12<br>><br>> It is as I expected:<br>> Engine status : {"reason": "failed liveliness check"<br>> The host can't talk to the ovirt-engine service. Please make sure the<br>> host can reach the engine fqdn as configured in<br>> /etc/ovirt-hosted-engine/hosted-engine.conf on the fqdn= line.<br>> You can check it manually by executing $(hosted-engine<br>> --check-liveliness) from the host.<br>> Best regards<br>> Martin Sivak<br>> On Wed, Apr 25, 2018 at 12:51 PM, <dhy336@sina.com> wrote:<br>>> Hi,<br>>><br>>> two node :<br>>> 192.168.122.66 hosted-engine1<br>>> 192.168.122.223 hosted-engine2<br>>><br>>> I power off hosted-engine1, so I do not attach hosted-engine1`s log,<br>>><br>>> [root@hosted-engine2 ~]# hosted-engine --vm-status<br>>><br>>> --== Host 1 status ==--<br>>><br>>> conf_on_shared_storage : True<br>>> Status up-to-date : False<br>>> Hostname : hosted-engine1<br>>> Host ID : 1<br>>> Engine status : unknown stale-data<br>>> Score : 3400<br>>> stopped : False<br>>> Local maintenance : False<br>>> crc32 : a7af0afa<br>>> local_conf_timestamp : 11485<br>>> Host timestamp : 11485<br>>> Extra metadata (valid at timestamp):<br>>> metadata_parse_version=1<br>>> metadata_feature_version=1<br>>> timestamp=11485 (Wed Apr 25 10:08:34 2018)<br>>> host-id=1<br>>> score=3400<br>>> vm_conf_refresh_time=11485 (Wed Apr 25 10:08:34 2018)<br>>> conf_on_shared_storage=True<br>>> maintenance=False<br>>> state=EngineUp<br>>> stopped=False<br>>><br>>><br>>> --== Host 2 status ==--<br>>><br>>> conf_on_shared_storage : True<br>>> Status up-to-date : True<br>>> Hostname : hosted-engine2<br>>> Host ID : 2<br>>> Engine status : {"reason": "failed liveliness check",<br>>> "health": "bad", "vm": "up", "detail": "Up"}<br>>> Score : 3000<br>>> stopped : False<br>>> Local maintenance : False<br>>> crc32 : a2e82883<br>>> local_conf_timestamp : 6278<br>>> Host timestamp : 6278<br>>> Extra metadata (valid at timestamp):<br>>> metadata_parse_version=1<br>>> metadata_feature_version=1<br>>> timestamp=6278 (Wed Apr 25 10:37:44 2018)<br>>> host-id=2<br>>> score=3000<br>>> vm_conf_refresh_time=6278 (Wed Apr 25 10:37:44 2018)<br>>> conf_on_shared_storage=True<br>>> maintenance=False<br>>> state=EngineStop<br>>> stopped=False<br>>> timeout=Thu Jan 1 09:49:38 1970<br>>><br>>><br>>><br>>> ----- Original Message -----<br>>> From: Martin Sivak <msivak@redhat.com><br>>> To: dhy336 <dhy336@sina.com>, users <users@ovirt.org><br>>> Subject: Re: Re: Re: Re: Re: [ovirt-users] �ظ���Re: Hosted-engine can<br>>> not_switch<br>>> Date: 2018-04-25 17:41<br>>><br>>><br>>> Please attach the output of hosted-engine --vm-status and the<br>>> /var/log/ovirt-hosted-engine-ha/agent.log file from both hosts.<br>>> The VM will restart if the ovirt-engine service does not become<br>>> available within timeout. And that might mean couple of things - the<br>>> FQDN of the engine is wrong, the engine needs something that was only<br>>> available on the dead host (A) like some storage, host B cannot ping<br>>> the gateway..<br>>> Best regards<br>>> Martin Sivak<br>>> On Wed, Apr 25, 2018 at 11:33 AM, <dhy336@sina.com> wrote:<br>>>> sorry, I mis-represent,<br>>>><br>>>> I hava two node, A:192.168.122.65 , B:192.168.122.66 with hosted-engine.<br>>>><br>>>> testing engine HA :<br>>>><br>>>> first two node is up, and hosted-engine VM run in A, then I poweroff A,<br>>>> and<br>>>> after 3 minutes, B start it`s hosted engine VM,<br>>>> But it`s ovirt-engine connect to host A, and continue for about 10<br>>>> minutes,<br>>>> then hosted engine VM restart.<br>>>> ----- Original Message -----<br>>>> From: Martin Sivak <msivak@redhat.com><br>>>> To: dhy336 <dhy336@sina.com><br>>>> Subject: Re: Re: Re: Re: [ovirt-users] �ظ���Re: Hosted-engine can<br>>>> not_switch<br>>>> Date: 2018-04-25 17:11<br>>>><br>>>><br>>>> Your hosted engine VM has its own address that does not depend on<br>>>> which host it is currently running. So it should be available on the<br>>>> same address no matter where the VM is running.<br>>>> Best regards<br>>>> Martin Sivak<br>>>> On Wed, Apr 25, 2018 at 9:07 AM, <dhy336@sina.com> wrote:<br>>>>>>> I deploy two node for hosted engine, first hosted engine VM run in<br>>>>>>> 192.168.122.65, I power off this host, hosted-engine VM switch<br>>>>>>> another host��but ovirt engine still connect 192.168.122.65. if restart<br>>>>>>> ovirt-engine server, it is work.<br>>>>><br>>>>> I think this issue is error, because hosted engine VM has power up in<br>>>>> another host( 192.168.122.66), so hosted engine should<br>>>>> connect to host( 192.168.122.66), not connet to host(192.168.122.66)?<br>>>>><br>>>>> thanks<br>>>>><br>>>>> ----- Original Message -----<br>>>>> From: Martin Sivak <msivak@redhat.com><br>>>>> To: dhy336 <dhy336@sina.com><br>>>>> Cc: users <users@ovirt.org><br>>>>> Subject: Re: Re: Re: [ovirt-users] �ظ���Re: Hosted-engine can not_switch<br>>>>> Date: 2018-04-20 18:28<br>>>>><br>>>>><br>>>>> Hi,<br>>>>> No, this is not an error. You killed the host without moving it to<br>>>>> maintenance first. The engine has no way to distinguish this from<br>>>>> temporary network failure for example. Give it some time and the host<br>>>>> will move its status to one of the error states and handle the highly<br>>>>> available VMs on it (if fencing is properly configured).<br>>>>> Best regards<br>>>>> Martin Sivak<br>>>>> On Fri, Apr 20, 2018 at 12:13 PM, <dhy336@sina.com> wrote:<br>>>>>> this process is not error ?<br>>>>>> ----- Original Message -----<br>>>>>> From: Martin Sivak <msivak@redhat.com><br>>>>>> To: dhy336 <dhy336@sina.com><br>>>>>> Cc: users <users@ovirt.org><br>>>>>> Subject: Re: Re: [ovirt-users] �ظ���Re: Hosted-engine can not_switch<br>>>>>> Date: 2018-04-20 18:05<br>>>>>><br>>>>>><br>>>>>> Hi,<br>>>>>> the engine does not know you killed the host. It will notice<br>>>>>> eventually and handle the situation. Just give it time (5 minutes or<br>>>>>> so).<br>>>>>> Best regards<br>>>>>> --<br>>>>>> Martin Sivak<br>>>>>> SLA / oVirt<br>>>>>> On Fri, Apr 20, 2018 at 12:00 PM, <dhy336@sina.com> wrote:<br>>>>>>> Hi�� thanks for your feedback. I hava another qeustions<br>>>>>>><br>>>>>>> I deploy two node for hosted engine, first hosted engine VM run in<br>>>>>>> 192.168.122.65, I power off this host, hosted-engine VM switch<br>>>>>>> another host��but ovirt engine still connect 192.168.122.65. if restart<br>>>>>>> ovirt-engine server, it is work.<br>>>>>>><br>>>>>>><br>>>>>>> 2018-04-20 17:13:04,692+08 ERROR<br>>>>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]<br>>>>>>> (EE-ManagedThreadFactory-en gineScheduled-Thread-98) [] Command<br>>>>>>> 'GetAllVmStatsVDSCommand(HostName = hosted-engine2,<br>>>>>>> VdsIdVDSCommandParametersBase:{hos<br>>>>>>> tId='a5428ef7-9df6-4a86-91de-7e36fda340fa'})' execution failed:<br>>>>>>> java.net.NoRouteToHostException: No route to host<br>>>>>>> 6568 2018-04-20 17:13:04,693+08 INFO<br>>>>>>> [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher]<br>>>>>>> (EE-ManagedThreadFactory-engi neScheduled-Thread-98) [] Failed to<br>>>>>>> fetch<br>>>>>>> vms info for host 'hosted-engin2' - skipping VMs monitoring.<br>>>>>>> 6569 2018-04-20 17:13:19,710+08 INFO<br>>>>>>> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp<br>>>>>>> Reactor)<br>>>>>>> [] Connecting to hosted-engine2/192.168.122.656570 2018-04-20<br>>>>>>> 17:13:22,730+08 ERROR<br>>>>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]<br>>>>>>> (EE-ManagedThreadFactory-en gineScheduled-Thread-45) [] Command<br>>>>>>> 'GetAllVmStatsVDSCommand(HostName = hosted-engine-tchyp2,<br>>>>>>> VdsIdVDSCommandParametersBase:{hos<br>>>>>>> tId='a5428ef7-9df6-4a86-91de-7e36fda340fa'})' execution failed:<br>>>>>>> java.net.NoRouteToHostException: No route to host<br>>>>>>> 6571 2018-04-20 17:13:22,732+08 INFO<br>>>>>>> [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher]<br>>>>>>> (EE-ManagedThreadFactory-engi neScheduled-Thread-45) [] Failed to<br>>>>>>> fetch<br>>>>>>> vms info for host 'hosted-engine2' - skipping VMs monitoring.<br>>>>>>><br>>>>>>> ----- Original Message -----<br>>>>>>> From: Martin Sivak <msivak@redhat.com><br>>>>>>> To: dhy336 <dhy336@sina.com><br>>>>>>> Cc: users <users@ovirt.org><br>>>>>>> Subject: Re: [ovirt-users] �ظ���Re: Hosted-engine can not_switch<br>>>>>>> Date: 2018-04-20 16:40<br>>>>>>><br>>>>>>><br>>>>>>> Hi,<br>>>>>>> your ovirt-hosted-engine-ha package is too old. You need at least<br>>>>>>> 2.1.9 to properly support 4.2 engine. The same applies to vdsm. Please<br>>>>>>> upgrade the node.<br>>>>>>> Best regards<br>>>>>>> Martin Sivak<br>>>>>>> On Fri, Apr 20, 2018 at 3:58 AM, <dhy336@sina.com> wrote:<br>>>>>>>> Hi I find some error logs in /var/log/ovirt-hosted-engine-ha/broker.<br>>>>>>>><br>>>>>>>> [root@hosted-engine2 ~]# ll /rhev/data-center/mnt<br>>>>>>>> total 0<br>>>>>>>> drwxr-xr-x. 3 vdsm kvm 76 Apr 18 22:28 192.168.122.218:_exports_data<br>>>>>>>> drwxr-xr-x. 3 vdsm kvm 76 Apr 18 22:12<br>>>>>>>> 192.168.122.218:_exports_hosted-engine-test1<br>>>>>>>> [root@hosted-engine2 ~]# ll<br>>>>>>>> /rhev/data-center/mnt/192.168.122.218\:_exports_hosted-engine-test1/<br>>>>>>>> total 0<br>>>>>>>> drwxr-xr-x. 5 vdsm kvm 50 Apr 18 22:14<br>>>>>>>> 8a734205-65b7-4801-b7f0-d380eb45dbae<br>>>>>>>> -rwxr-xr-x. 1 vdsm kvm 0 Apr 20 09:54 __DIRECT_IO_TEST__<br>>>>>>>><br>>>>>>>> uuid 8a734205-65b7-4801-b7f0-d380eb45dbae is in<br>>>>>>>> /rhev/data-center/mnt/192.168.122.218\:_exports_hosted-engine-test1/<br>>>>>>>> but broker find it in /rhev/data-center/mnt, is it my version is<br>>>>>>>> error?<br>>>>>>>> my<br>>>>>>>> ovirt-hosted-engine-ha version is 2.1.5, vdsm is 4.20.5��<br>>>>>>>> ovirt-engine is 4.2<br>>>>>>>><br>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> 19:26:31,479::listener::41::ovirt_hosted_engine_ha.broker.listener.Listener::(__init__)<br>>>>>>>> Initializing SocketServer<br>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> 19:26:31,480::listener::56::ovirt_hosted_engine_ha.broker.listener.Listener::(__init__)<br>>>>>>>> SocketServer ready<br>>>>>>>> Thread-1::INFO::2018-04-19<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> 19:26:31,558::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup)<br>>>>>>>> Connection established<br>>>>>>>> Thread-1::ERROR::2018-04-19<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> 19:26:31,559::listener::192::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)<br>>>>>>>> Error handling request, data: 'set-storage-domain FilesystemBackend<br>>>>>>>> dom_type=nfs3 sd_uuid=8a734205-65b7-4801-b7f0-d380eb45dbae'<br>>>>>>>> Traceback (most recent call last):<br>>>>>>>> File<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py",<br>>>>>>>> line 166, in handle<br>>>>>>>> data)<br>>>>>>>> File<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py",<br>>>>>>>> line 299, in _dispatch<br>>>>>>>> .set_storage_domain(client, sd_type, **options)<br>>>>>>>> File<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",<br>>>>>>>> line 66, in set_storage_domain<br>>>>>>>> self._backends[client].connect()<br>>>>>>>> File<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py",<br>>>>>>>> line 462, in connect<br>>>>>>>> self._dom_type)<br>>>>>>>> File<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py",<br>>>>>>>> line 107, in get_domain_path<br>>>>>>>> " in {1}".format(sd_uuid, parent))<br>>>>>>>> BackendFailureException: path to storage domain<br>>>>>>>> 8a734205-65b7-4801-b7f0-d380eb45dbae not found in<br>>>>>>>> /rhev/data-center/mnt<br>>>>>>>> Thread-1::INFO::2018-04-19<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> 19:26:31,563::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)<br>>>>>>>> Connection closed<br>>>>>>>> Thread-2::INFO::2018-04-19<br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>><br>>>>>>>> 19:26:44,601::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup)<br>>>>>>>> Connection established<br>>>>>>>><br>>>>>>>> ----- ԭʼ�ʼ� -----<br>>>>>>>> �����ˣ�<dhy336@sina.com><br>>>>>>>> �ռ��ˣ�"Martin Sivak" <msivak@redhat.com><br>>>>>>>> �����ˣ�users <users@ovirt.org><br>>>>>>>> ���⣺[ovirt-users] �ظ���Re: Hosted-engine can not_switch<br>>>>>>>> ���ڣ�2018��04��20�� 09��30��<br>>>>>>>><br>>>>>>>> libvirt has not error logs . I only find some error for vdsm.<br>>>>>>>> vdsm log is:<br>>>>>>>> 2018-04-20 09:24:52,610+0800 INFO (jsonrpc/1) [vdsm.api] FINISH<br>>>>>>>> getVolumeInfo return={'info': {'status': 'OK', 'domain':<br>>>>>>>> '8a734205-65b7-4801-b7f0-d380eb45dbae', 'voltype': 'LEAF',<br>>>>>>>> 'description':<br>>>>>>>> 'hosted-engine.lockspace', 'parent':<br>>>>>>>> '00000000-0000-0000-0000-000000000000',<br>>>>>>>> 'format': 'RAW', 'generation': 0, 'image':<br>>>>>>>> '611272bd-c2cc-42bc-94e2-9aa52e754c35', 'ctime': '1524032037',<br>>>>>>>> 'disktype':<br>>>>>>>> '2', 'legality': 'LEGAL', 'mtime': '0', 'apparentsize': '1048576',<br>>>>>>>> 'children': [], 'pool': '', 'capacity': '1048576', 'uuid':<br>>>>>>>> u'7037aac6-7c8e-4efd-82f7-ca618c953fe6', 'truesize': '1048576',<br>>>>>>>> 'type':<br>>>>>>>> 'PREALLOCATED', 'lease': {'owners': [], 'version': None}}}<br>>>>>>>> from=::1,48306,<br>>>>>>>> task_id=03a7938e-8afb-4b16-b8dd-126c2b1f5d52 (api:52)<br>>>>>>>> 2018-04-20 09:24:52,611+0800 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer]<br>>>>>>>> RPC<br>>>>>>>> call Volume.getInfo succeeded in 0.03 seconds (__init__:630)<br>>>>>>>> 2018-04-20 09:24:54,113+0800 ERROR (periodic/3)<br>>>>>>>> [virt.periodic.Operation]<br>>>>>>>> <vdsm.virt.sampling.VMBulkstatsMonitor object at 0x1e92f90> operation<br>>>>>>>> failed<br>>>>>>>> (periodic:215)<br>>>>>>>> Traceback (most recent call last):<br>>>>>>>> File "/usr/lib/python2.7/site-packages/vdsm/virt/periodic.py", line<br>>>>>>>> 213,<br>>>>>>>> in __call__<br>>>>>>>> self._func()<br>>>>>>>> File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line<br>>>>>>>> 522,<br>>>>>>>> in __call__<br>>>>>>>> self._send_metrics()<br>>>>>>>> File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line<br>>>>>>>> 538,<br>>>>>>>> in _send_metrics<br>>>>>>>> vm_sample.interval)<br>>>>>>>> File "/usr/lib/python2.7/site-packages/vdsm/virt/vmstats.py", line<br>>>>>>>> 45,<br>>>>>>>> in<br>>>>>>>> produce<br>>>>>>>> networks(vm, stats, first_sample, last_sample, interval)<br>>>>>>>> File "/usr/lib/python2.7/site-packages/vdsm/virt/vmstats.py", line<br>>>>>>>> 322,<br>>>>>>>> in<br>>>>>>>> networks<br>>>>>>>> if nic.name.startswith('hostdev'):<br>>>>>>>> AttributeError: name<br>>>>>>>> 2018-04-20 09:24:54,800+0800 INFO (Reactor thread)<br>>>>>>>> [ProtocolDetector.AcceptorImpl] Accepted connection from ::1:48308<br>>>>>>>> (protocoldetector:61)<br>>>>>>>> 2018-04-20 09:24:54,810+0800 INFO (Reactor thread)<br>>>>>>>> [ProtocolDetector.Detector] Detected protocol stomp from ::1:48308<br>>>>>>>> (protocoldetector:125)<br>>>>>>>> 2018-04-20 09:24:54,810+0800 INFO (Reactor thread)<br>>>>>>>> [Broker.StompAdapter]<br>>>>>>>> Processing CONNECT request (stompreactor:103)<br>>>>>>>> 2018-04-20 09:24:54,818+0800 INFO (JsonRpc (StompReactor))<br>>>>>>>> [Broker.StompAdapter] Subscribe command received (stompreactor:132)<br>>>>>>>> 2018-04-20 09:24:55,119+0800 INFO (jsonrpc/6) [api.host] START<br>>>>>>>> getHardwareInfo() from=::1,48308 (api:46)<br>>>>>>>><br>>>>>>>> ----- ԭʼ�ʼ� -----<br>>>>>>>> �����ˣ�Martin Sivak <msivak@redhat.com><br>>>>>>>> �ռ��ˣ�dhy336 <dhy336@sina.com><br>>>>>>>> �����ˣ�users <users@ovirt.org><br>>>>>>>> ���⣺Re: [ovirt-users] Hosted-engine can not switch<br>>>>>>>> ���ڣ�2018��04��19�� 20��16��<br>>>>>>>><br>>>>>>>><br>>>>>>>> We need more than just this small log snippet. Please check the vdsm<br>>>>>>>> and libvirt logs as well.<br>>>>>>>> Best regards<br>>>>>>>> Martin Sivak<br>>>>>>>> On Thu, Apr 19, 2018 at 2:05 PM, <dhy336@sina.com> wrote:<br>>>>>>>>> Hi��<br>>>>>>>>> I deploy three node with hosted engine, I force shut down a node<br>>>>>>>>> which<br>>>>>>>>> Host-engine VM is run, But hosted engine VM in other nodes can not<br>>>>>>>>> run.<br>>>>>>>>><br>>>>>>>>> I find some error in /var/log/ovirt-hosted-engine-ha/agent.log<br>>>>>>>>><br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:35,787::hosted_engine::1192::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_clean_vdsm_state)<br>>>>>>>>> Cleaning state for non-running VM<br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:42,587::hosted_engine::1176::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_clean_vdsm_state)<br>>>>>>>>> Vdsm state for VM clean<br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:42,589::hosted_engine::1125::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_start_engine_vm)<br>>>>>>>>> Starting vm using `/usr/sbin/hosted-engine --vm-start`<br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:47,599::hosted_engine::1131::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_start_engine_vm)<br>>>>>>>>> stdout:<br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:47,600::hosted_engine::1132::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_start_engine_vm)<br>>>>>>>>> stderr: Virtual machine does not exist: {'vmId':<br>>>>>>>>> u'08bbd680-a8a7-4267-82e7-89f36e87e930'}<br>>>>>>>>><br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:47,600::hosted_engine::1144::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_start_engine_vm)<br>>>>>>>>> Engine VM started on localhost<br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:47,609::brokerlink::111::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify)<br>>>>>>>>> Trying: notify time=1524139007.61 type=state_transition<br>>>>>>>>> detail=EngineStart-EngineStarting hostname='hosted-engine2'<br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:47,670::brokerlink::121::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify)<br>>>>>>>>> Success, was notification of state_transition<br>>>>>>>>> (EngineStart-EngineStarting)<br>>>>>>>>> sent? sent<br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:47,670::hosted_engine::604::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_vdsm)<br>>>>>>>>> Initializing VDSM<br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:50,095::hosted_engine::630::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_storage_images)<br>>>>>>>>> Connecting the storage<br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:50,096::storage_server::220::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(validate_storage_server)<br>>>>>>>>> Validating storage server<br>>>>>>>>> MainThread::INFO::2018-04-19<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> 19:56:52,449::hosted_engine::639::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_storage_images)<br>>>>>>>>> Storage domain reported as valid and reconnect is not forced.<br>>>>>>>>><br>>>>>>>>><br>>>>>>>>> _______________________________________________<br>>>>>>>>> Users mailing list<br>>>>>>>>> Users@ovirt.org<br>>>>>>>>> http://lists.ovirt.org/mailman/listinfo/users<br>>>>>>>>><br>>>>>>>> _______________________________________________<br>>>>>>>> Users mailing list<br>>>>>>>> Users@ovirt.org<br>>>>>>>> http://lists.ovirt.org/mailman/listinfo/users<br></div>