VxRail: I controlli preliminari hanno esito negativo quando si arresta l'intero cluster VxRail PrecheckException

Summary: I controlli preliminari dei messaggi di errore hanno esito negativo quando si arresta l'intero cluster VxRail Appliance e si esegue il controllo preliminare di PrecheckException.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Arresto dell'appliance VxRail: il
controllo preliminare finale di VxRail non è riuscito a causa di errori interni.

Durante un arresto completo di VxRail Appliance, si verificava il timeout di tutte le azioni di vCenter. Disabilitazione della disponibilità elevata, migrazione delle VM di servizio e così via

Marvin.log 
2018-09-13T22:21:52:702Z [ERROR] [MessageBroker-2] o.s.s.s.TaskUtils$LoggingErrorHandler:95 - Unexpected error occurred in scheduled task.
2018-09-13T22:34:22:028Z [ERROR] [localhost-startStop-1] c.v.m.c.s.m.PlatformInformationService:252 - Unable to determine platform type: Failed to find primary host
2018-09-13T22:34:23:254Z [ERROR] [localhost-startStop-1] c.v.m.c.s.m.PlatformInformationService:252 - Unable to determine platform type: Failed to find primary host
2018-09-13T22:34:23:492Z [ERROR] [localhost-startStop-1] c.v.m.c.s.m.PlatformInformationService:252 - Unable to determine platform type: Failed to find primary host
Connectors-cluster.log 
Sep 13 22:31:19,167 GMT 2018  ERROR [AMQP Connection 127.0.0.1:5672] CachingConnectionFactory$DefaultChannelCloseLogger.log:1089 - Channel shutdown: connection error
Sep 13 22:31:19,167 GMT 2018  ERROR [AMQP Connection 127.0.0.1:5672] CachingConnectionFactory$DefaultChannelCloseLogger.log:1089 - Channel shutdown: connection error
Sep 13 22:31:19,167 GMT 2018  ERROR [AMQP Connection 127.0.0.1:5672] CachingConnectionFactory$DefaultChannelCloseLogger.log:1089 - Channel shutdown: connection error
Sep 13 23:13:00,858 GMT 2018  ERROR [SimpleAsyncTaskExecutor-1] PrecheckMQListener.check:66 - com.emc.mystic.manager.commons.emc.precheck.exception.PrecheckException

Sep 14 00:17:12,499 GMT 2018  ERROR [pool-51-thread-1] ServiceUtil.waitForTask:466 - Message The operation is not allowed in the current state.
Sep 14 00:17:12,499 GMT 2018  ERROR [pool-51-thread-1] VimOperator.migrateVMs:2016 - Migrating VM fails: vm-14
Sep 14 00:17:12,499 GMT 2018  ERROR [pool-51-thread-1] VimOperator.migrateVMs:2020 - Migrate VM failed:com.vmware.vim25.ManagedObjectReference@ 36891641  
java.lang.RuntimeException: Migrating VM fails: vm-14
 at com.emc.mystic.manager.commons.vmware.VimOperator.migrateVMs(VimOperator.java:2017) [mystic.manager.commons.vmware-4.0.401.jar:?]
 at com.emc.mystic.manager.connectors.cluster.ShutdownStartupServiceImpl$1.run(ShutdownStartupServiceImpl.java:162) [mystic.manager.connectors.cluster-4.0.401-lib.jar:?]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_141]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_141]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_141]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_141]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141]
Sep 14 00:17:12,500 GMT 2018  ERROR [pool-51-thread-1] ShutdownStartupServiceImpl$1.run:197 - Shutdown error
com.emc.mystic.manager.connectors.cluster.ClusterShutdownException: java.lang.RuntimeException: Migrating VM fails: vm-14
 at com.emc.mystic.manager.connectors.cluster.ClusterShutdownException.getClusterShutDownException(ClusterShutdownException.java:56) ~[mystic.manager.connectors.cluster-4.0.401-lib.jar:?]
 at com.emc.mystic.manager.connectors.cluster.ShutdownStartupServiceImpl$1.run(ShutdownStartupServiceImpl.java:164) [mystic.manager.connectors.cluster-4.0.401-lib.jar:?]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_141]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_141]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_141]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_141]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141]
Caused by: java.lang.RuntimeException: Migrating VM fails: vm-14
 at com.emc.mystic.manager.commons.vmware.VimOperator.migrateVMs(VimOperator.java:2017) ~[mystic.manager.commons.vmware-4.0.401.jar:?]
 at com.emc.mystic.manager.connectors.cluster.ShutdownStartupServiceImpl$1.run(ShutdownStartupServiceImpl.java:162) ~[mystic.manager.connectors.cluster-4.0.401-lib.jar:?]
 ... 5 more

Cause

vCenter non è in grado di funzionare a causa della mancanza di DNS.  Nell'ambiente di questo cliente, le VM DNS si trovano sull'appliance VxRail come una normale VM.

Resolution

Soluzione alternativa: Accendere una delle VM del server DNS e riprovare a spegnerla manualmente dopo l'arresto di tutte le altre VM.  
In alternativa, puntare vCenter Appliance su un server DNS non su VxRail.

Additional Information

Consigli: VxRail vCenter Appliance deve avere il DNS che punta a un server non in hosting sul VxRail Cluster.
In caso contrario, la VM DNS deve essere una delle ultime VM da arrestare e deve essere posizionata sull'ultimo ESXi server ad essere arrestato.

Un cliente ha anche riscontrato questo problema con la macchina virtuale di Log Insight ancora in esecuzione. 
Sep 13 23:46:57,625 GMT 2018  ERROR [pool-49-thread-1] ServiceUtil.waitForTask:466 - Message A general system error occurred: PBM error occurred during PreMigrateCheckCallback: Operation timed out
Sep 13 23:46:57,625 GMT 2018  ERROR [pool-49-thread-1] VimOperator.migrateVMs:2016 - Migrating VM fails: vm-17
Sep 13 23:46:57,625 GMT 2018  ERROR [pool-49-thread-1] VimOperator.migrateVMs:2020 - Migrate VM failed : com.vmware.vim25.ManagedObjectReference6f7a5a92
java.lang.RuntimeException: Migrating VM fails: vm-17
 at com.emc.mystic.manager.commons.vmware.VimOperator.migrateVMs(VimOperator.java:2017) [mystic.manager.commons.vmware-4.0.401.jar:?]
 at com.emc.mystic.manager.connectors.cluster.ShutdownStartupServiceImpl$1.run(ShutdownStartupServiceImpl.java:162) [mystic.manager.connectors.cluster-4.0.401-lib.jar:?]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_141]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_141]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_141]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_141]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141]
Sep 13 23:46:57,626 GMT 2018  ERROR [pool-49-thread-1] ShutdownStartupServiceImpl$1.run:197 - Shutdown error
com.emc.mystic.manager.connectors.cluster.ClusterShutdownException: java.lang.RuntimeException: Migrating VM fails: vm-17
 at com.emc.mystic.manager.connectors.cluster.ClusterShutdownException.getClusterShutDownException(ClusterShutdownException.java:56) ~[mystic.manager.connectors.cluster-4.0.401-lib.jar:?]
 at com.emc.mystic.manager.connectors.cluster.ShutdownStartupServiceImpl$1.run(ShutdownStartupServiceImpl.java:164) [mystic.manager.connectors.cluster-4.0.401-lib.jar:?]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_141]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_141]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_141]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_141]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141]
Caused by: java.lang.RuntimeException: Migrating VM fails: vm-17
 at com.emc.mystic.manager.commons.vmware.VimOperator.migrateVMs(VimOperator.java:2017) ~[mystic.manager.commons.vmware-4.0.401.jar:?]
 at com.emc.mystic.manager.connectors.cluster.ShutdownStartupServiceImpl$1.run(ShutdownStartupServiceImpl.java:162) ~[mystic.manager.connectors.cluster-4.0.401-lib.jar:?]
 ... 5 more

Affected Products

VxRail 460 and 470 Nodes

Products

VxRail 460 and 470 Nodes
Article Properties
Article Number: 000054970
Article Type: Solution
Last Modified: 05 Sep 2025
Version:  7
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.