API tools faq
paste
riteshchikatwar

Untitled

riteshchikatwar
Feb 10th, 2020
156
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 24.07 KB | None | 0 0
raw download clone embed print report
  1. 2020-02-10 16:27:08,391+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60) [313a966e] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Installing Host monster. Gather the rpm package facts.
  2. 2020-02-10 16:27:08,399+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60) [313a966e] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Installing Host monster. Check if post tasks file exists.
  3. 2020-02-10 16:27:11,655+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60) [313a966e] EVENT_ID: VDS_ANSIBLE_INSTALL_FINISHED(561), Ansible host-deploy playbook execution has successfully finished on host monster.
  4. 2020-02-10 16:27:11,667+05 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to /10.70.43.53
  5. 2020-02-10 16:27:13,414+05 INFO [org.ovirt.engine.core.bll.host.HostConnectivityChecker] (EE-ManagedThreadFactory-engine-Thread-60) [313a966e] Engine managed to communicate with VDSM agent on host 'monster' with address '10.70.43.53' ('60f990c6-4333-4c51-baa6-8f3a511ea746')
  6. 2020-02-10 16:27:20,441+05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] Before acquiring lock-timeout 'EngineLock:{exclusiveLocks='[HOST_NETWORK60f990c6-4333-4c51-baa6-8f3a511ea746=HOST_NETWORK]', sharedLocks=''}'
  7. 2020-02-10 16:27:20,442+05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] Lock-timeout acquired to object 'EngineLock:{exclusiveLocks='[HOST_NETWORK60f990c6-4333-4c51-baa6-8f3a511ea746=HOST_NETWORK]', sharedLocks=''}'
  8. 2020-02-10 16:27:20,482+05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] Running command: HostSetupNetworksCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDSAction group CONFIGURE_HOST_NETWORK with role type ADMIN
  9. 2020-02-10 16:27:20,482+05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] Before acquiring lock in order to prevent monitoring for host 'monster' from data-center 'Default'
  10. 2020-02-10 16:27:20,482+05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] Lock acquired, from now a monitoring of host will be skipped for host 'monster' from data-center 'Default'
  11. 2020-02-10 16:27:20,487+05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] START, HostSetupNetworksVDSCommand(HostName = monster, HostSetupNetworksVdsCommandParameters:{hostId='60f990c6-4333-4c51-baa6-8f3a511ea746', vds='Host[monster,60f990c6-4333-4c51-baa6-8f3a511ea746]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', networks='[HostNetwork:{defaultRoute='true', bonding='false', networkName='ovirtmgmt', vdsmName='ovirtmgmt', nicName='ens7', vlan='null', vmNetwork='true', stp='false', properties='null', ipv4BootProtocol='DHCP', ipv4Address='null', ipv4Netmask='null', ipv4Gateway='null', ipv6BootProtocol='POLY_DHCP_AUTOCONF', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='null'}]', removedNetworks='[]', bonds='[]', removedBonds='[]', clusterSwitchType='LEGACY', managementNetworkChanged='true'}), log id: 28bfc19a
  12. 2020-02-10 16:27:20,490+05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] FINISH, HostSetupNetworksVDSCommand, return: , log id: 28bfc19a
  13. 2020-02-10 16:27:37,649+05 WARN [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for <JsonRpcResponse id: "d0b627db-3c95-445a-94d7-b2662b088c6e" result: true>
  14. 2020-02-10 16:27:37,860+05 WARN [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for <JsonRpcResponse id: "1a8b0b92-4262-46e3-84ce-ce1eaccfd033" result: true>
  15. 2020-02-10 16:27:38,196+05 WARN [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for <JsonRpcResponse id: "13af429b-6c6d-4d3b-82f7-319416e52c51" result: true>
  16. 2020-02-10 16:27:38,748+05 WARN [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for <JsonRpcResponse id: "104c567f-3ad5-4b23-a1a1-3136b74c07dd" result: true>
  17. 2020-02-10 16:27:38,974+05 WARN [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for <JsonRpcResponse id: "c1f823a8-dfc8-4d32-a34c-ed28cafda1c7" result: true>
  18. 2020-02-10 16:27:39,297+05 WARN [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for <JsonRpcResponse id: "80ac4104-e8d9-4ed9-906c-ee800d0e7352" result: true>
  19. 2020-02-10 16:27:40,298+05 WARN [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for <JsonRpcResponse id: "4035d7c7-f477-44d8-bf25-f851f5a27e54" result: true>
  20. 2020-02-10 16:27:41,480+05 WARN [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for <JsonRpcResponse id: "0182063c-ba87-4cf6-b216-42a6c57f9935" result: true>
  21. 2020-02-10 16:27:43,218+05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] Host setup networks finished. Lock released. Monitoring can run now for host 'monster' from data-center 'Default'
  22. 2020-02-10 16:27:43,221+05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] Lock freed to object 'EngineLock:{exclusiveLocks='[HOST_NETWORK60f990c6-4333-4c51-baa6-8f3a511ea746=HOST_NETWORK]', sharedLocks=''}'
  23. 2020-02-10 16:27:43,249+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] START, SetVdsStatusVDSCommand(HostName = monster, SetVdsStatusVDSCommandParameters:{hostId='60f990c6-4333-4c51-baa6-8f3a511ea746', status='Initializing', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 36a509ba
  24. 2020-02-10 16:27:43,251+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] FINISH, SetVdsStatusVDSCommand, return: , log id: 36a509ba
  25. 2020-02-10 16:27:43,252+05 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] After Installation host monster, VDS
  26. 2020-02-10 16:27:43,255+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] EVENT_ID: VDS_INSTALL(504), Host monster installed
  27. 2020-02-10 16:27:43,257+05 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-60) [8ab4622] Lock freed to object 'EngineLock:{exclusiveLocks='[60f990c6-4333-4c51-baa6-8f3a511ea746=VDS]', sharedLocks=''}'
  28. 2020-02-10 16:27:45,571+05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [] START, GetHardwareInfoAsyncVDSCommand(HostName = monster, VdsIdAndVdsVDSCommandParametersBase:{hostId='60f990c6-4333-4c51-baa6-8f3a511ea746', vds='Host[monster,60f990c6-4333-4c51-baa6-8f3a511ea746]'}), log id: 6c4f3593
  29. 2020-02-10 16:27:45,572+05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [] FINISH, GetHardwareInfoAsyncVDSCommand, return: , log id: 6c4f3593
  30. 2020-02-10 16:27:45,610+05 INFO [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [60b717dc] Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDS
  31. 2020-02-10 16:27:45,610+05 ERROR [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [60b717dc] Could not find server cpu for server 'monster' (60f990c6-4333-4c51-baa6-8f3a511ea746), flags: 'rep_good,vpid,umip,apic,mce,pse,cpuid,mmx,nx,hypervisor,cx16,msr,tpr_shadow,flexpriority,tsc_adjust,tsc,cmov,constant_tsc,popcnt,sse2,tsc_known_freq,sep,vnmi,x2apic,lahf_lm,vmx,vme,clflush,arch-capabilities,mca,syscall,cx8,xtopology,fpu,sse,pge,nopl,lm,mtrr,pse36,ept,pat,ssse3,sse4_1,tsc-deadline,de,skip-l1dfl-vmentry,pae,sse4_2,pni,arat,pti,fxsr,model_Conroe,model_486,model_pentium3,model_qemu64,model_Opteron_G1,model_kvm64,model_kvm32,model_Penryn,model_pentium2,model_qemu32,model_pentium,model_Opteron_G2'
  32. 2020-02-10 16:27:45,622+05 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [6a557ffb] Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDS
  33. 2020-02-10 16:27:45,624+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [6a557ffb] START, SetVdsStatusVDSCommand(HostName = monster, SetVdsStatusVDSCommandParameters:{hostId='60f990c6-4333-4c51-baa6-8f3a511ea746', status='NonOperational', nonOperationalReason='CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 2136e461
  34. 2020-02-10 16:27:45,626+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [6a557ffb] FINISH, SetVdsStatusVDSCommand, return: , log id: 2136e461
  35. 2020-02-10 16:27:45,661+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [6a557ffb] EVENT_ID: VDS_SET_NONOPERATIONAL(517), Host monster moved to Non-Operational state.
  36. 2020-02-10 16:27:45,665+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [6a557ffb] EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host monster moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all
  37. 2020-02-10 16:27:45,669+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [6a557ffb] EVENT_ID: VDS_DETECTED(13), Status of host monster was set to NonOperational.
  38. 2020-02-10 16:27:47,062+05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [] START, GetHardwareInfoAsyncVDSCommand(HostName = monster, VdsIdAndVdsVDSCommandParametersBase:{hostId='60f990c6-4333-4c51-baa6-8f3a511ea746', vds='Host[monster,60f990c6-4333-4c51-baa6-8f3a511ea746]'}), log id: 26541b06
  39. 2020-02-10 16:27:47,063+05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [] FINISH, GetHardwareInfoAsyncVDSCommand, return: , log id: 26541b06
  40. 2020-02-10 16:27:47,147+05 INFO [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [7780e24e] Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDS
  41. 2020-02-10 16:27:47,149+05 ERROR [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [7780e24e] Could not find server cpu for server 'monster' (60f990c6-4333-4c51-baa6-8f3a511ea746), flags: 'rep_good,vpid,umip,apic,mce,pse,cpuid,mmx,nx,hypervisor,cx16,msr,tpr_shadow,flexpriority,tsc_adjust,tsc,cmov,constant_tsc,popcnt,sse2,tsc_known_freq,sep,vnmi,x2apic,lahf_lm,vmx,vme,clflush,arch-capabilities,mca,syscall,cx8,xtopology,fpu,sse,pge,nopl,lm,mtrr,pse36,ept,pat,ssse3,sse4_1,tsc-deadline,de,skip-l1dfl-vmentry,pae,sse4_2,pni,arat,pti,fxsr,model_Conroe,model_486,model_pentium3,model_qemu64,model_Opteron_G1,model_kvm64,model_kvm32,model_Penryn,model_pentium2,model_qemu32,model_pentium,model_Opteron_G2'
  42. 2020-02-10 16:27:47,178+05 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [52ca8642] Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDS
  43. 2020-02-10 16:27:47,184+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [52ca8642] START, SetVdsStatusVDSCommand(HostName = monster, SetVdsStatusVDSCommandParameters:{hostId='60f990c6-4333-4c51-baa6-8f3a511ea746', status='NonOperational', nonOperationalReason='CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 6f17c0f4
  44. 2020-02-10 16:27:47,189+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [52ca8642] FINISH, SetVdsStatusVDSCommand, return: , log id: 6f17c0f4
  45. 2020-02-10 16:27:47,252+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [52ca8642] EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host monster moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all
  46. 2020-02-10 16:27:47,260+05 INFO [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [6e6da66e] Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDS
  47. 2020-02-10 16:27:47,260+05 ERROR [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [6e6da66e] Could not find server cpu for server 'monster' (60f990c6-4333-4c51-baa6-8f3a511ea746), flags: 'rep_good,vpid,umip,apic,mce,pse,cpuid,mmx,nx,hypervisor,cx16,msr,tpr_shadow,flexpriority,tsc_adjust,tsc,cmov,constant_tsc,popcnt,sse2,tsc_known_freq,sep,vnmi,x2apic,lahf_lm,vmx,vme,clflush,arch-capabilities,mca,syscall,cx8,xtopology,fpu,sse,pge,nopl,lm,mtrr,pse36,ept,pat,ssse3,sse4_1,tsc-deadline,de,skip-l1dfl-vmentry,pae,sse4_2,pni,arat,pti,fxsr,model_Conroe,model_486,model_pentium3,model_qemu64,model_Opteron_G1,model_kvm64,model_kvm32,model_Penryn,model_pentium2,model_qemu32,model_pentium,model_Opteron_G2'
  48. 2020-02-10 16:27:47,270+05 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [3c20f0e2] Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDS
  49. 2020-02-10 16:27:47,272+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [3c20f0e2] START, SetVdsStatusVDSCommand(HostName = monster, SetVdsStatusVDSCommandParameters:{hostId='60f990c6-4333-4c51-baa6-8f3a511ea746', status='NonOperational', nonOperationalReason='CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 2a498d6b
  50. 2020-02-10 16:27:47,274+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [3c20f0e2] FINISH, SetVdsStatusVDSCommand, return: , log id: 2a498d6b
  51. 2020-02-10 16:27:47,279+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [3c20f0e2] EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host monster moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all
  52. 2020-02-10 16:27:47,281+05 INFO [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [4cfb1528] Running command: HandleVdsVersionCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDS
  53. 2020-02-10 16:27:47,283+05 INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [4cfb1528] Host 'monster'(60f990c6-4333-4c51-baa6-8f3a511ea746) is already in NonOperational status for reason 'CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER'. SetNonOperationalVds command is skipped.
  54. 2020-02-10 16:27:50,466+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-10) [] EVENT_ID: VDS_LOW_DISK_SPACE_ERROR(24), Critical, Low disk space. Host monster has less than 500 MB of free space left on: /var/run/vdsm/. Low disk space might cause an issue upgrading this host.
  55. 2020-02-10 16:27:50,485+05 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-10) [] Received first domain report for host monster
  56. 2020-02-10 16:27:52,503+05 INFO [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-83) [] Fetched 0 VMs from VDS '60f990c6-4333-4c51-baa6-8f3a511ea746'
  57. 2020-02-10 16:30:00,019+05 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [] Autorecovering 1 hosts
  58. 2020-02-10 16:30:00,019+05 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [] Autorecovering hosts id: 60f990c6-4333-4c51-baa6-8f3a511ea746 , name : monster
  59. 2020-02-10 16:30:00,023+05 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [8046a44] Lock Acquired to object 'EngineLock:{exclusiveLocks='[60f990c6-4333-4c51-baa6-8f3a511ea746=VDS]', sharedLocks=''}'
  60. 2020-02-10 16:30:00,032+05 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [8046a44] Running command: ActivateVdsCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDSAction group MANIPULATE_HOST with role type ADMIN
  61. 2020-02-10 16:30:00,032+05 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [8046a44] Before acquiring lock in order to prevent monitoring for host 'monster' from data-center 'Default'
  62. 2020-02-10 16:30:00,032+05 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [8046a44] Lock acquired, from now a monitoring of host will be skipped for host 'monster' from data-center 'Default'
  63. 2020-02-10 16:30:00,041+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [8046a44] START, SetVdsStatusVDSCommand(HostName = monster, SetVdsStatusVDSCommandParameters:{hostId='60f990c6-4333-4c51-baa6-8f3a511ea746', status='Unassigned', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 210321c2
  64. 2020-02-10 16:30:00,106+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [8046a44] FINISH, SetVdsStatusVDSCommand, return: , log id: 210321c2
  65. 2020-02-10 16:30:00,111+05 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [8046a44] Activate host finished. Lock released. Monitoring can run now for host 'monster' from data-center 'Default'
  66. 2020-02-10 16:30:00,118+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [8046a44] EVENT_ID: VDS_ACTIVATE_ASYNC(9,502), Host monster was autorecovered.
  67. 2020-02-10 16:30:00,119+05 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [8046a44] Lock freed to object 'EngineLock:{exclusiveLocks='[60f990c6-4333-4c51-baa6-8f3a511ea746=VDS]', sharedLocks=''}'
  68. 2020-02-10 16:30:03,733+05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [] START, GetHardwareInfoAsyncVDSCommand(HostName = monster, VdsIdAndVdsVDSCommandParametersBase:{hostId='60f990c6-4333-4c51-baa6-8f3a511ea746', vds='Host[monster,60f990c6-4333-4c51-baa6-8f3a511ea746]'}), log id: bf465e1
  69. 2020-02-10 16:30:03,734+05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [] FINISH, GetHardwareInfoAsyncVDSCommand, return: , log id: bf465e1
  70. 2020-02-10 16:30:03,766+05 INFO [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [22ff0863] Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDS
  71. 2020-02-10 16:30:03,768+05 ERROR [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [22ff0863] Could not find server cpu for server 'monster' (60f990c6-4333-4c51-baa6-8f3a511ea746), flags: 'rep_good,vpid,umip,apic,mce,pse,cpuid,mmx,nx,hypervisor,cx16,msr,tpr_shadow,flexpriority,tsc_adjust,tsc,cmov,constant_tsc,popcnt,sse2,tsc_known_freq,sep,vnmi,x2apic,lahf_lm,vmx,vme,clflush,arch-capabilities,mca,syscall,cx8,xtopology,fpu,sse,pge,nopl,lm,mtrr,pse36,ept,pat,ssse3,sse4_1,tsc-deadline,de,skip-l1dfl-vmentry,pae,sse4_2,pni,arat,pti,fxsr,model_Conroe,model_486,model_pentium3,model_qemu64,model_Opteron_G1,model_kvm64,model_kvm32,model_Penryn,model_pentium2,model_qemu32,model_pentium,model_Opteron_G2'
  72. 2020-02-10 16:30:03,800+05 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7687703] Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 60f990c6-4333-4c51-baa6-8f3a511ea746 Type: VDS
  73. 2020-02-10 16:30:03,804+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7687703] START, SetVdsStatusVDSCommand(HostName = monster, SetVdsStatusVDSCommandParameters:{hostId='60f990c6-4333-4c51-baa6-8f3a511ea746', status='NonOperational', nonOperationalReason='CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 2c4f610f
  74. 2020-02-10 16:30:03,808+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7687703] FINISH, SetVdsStatusVDSCommand, return: , log id: 2c4f610f
  75. 2020-02-10 16:30:03,815+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7687703] EVENT_ID: VDS_SET_NONOPERATIONAL(517), Host monster moved to Non-Operational state.
  76. 2020-02-10 16:30:03,824+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7687703] EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host monster moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!