Apecc
Contributor
Contributor

Миграция с Windows vcenter 6.5 на VCSA 6.7

Jump to solution

Коллеги доброго времени вам.

При миграции с Windows vcenter 6.5 на VCSA 6.7 на этапе "2 Get up target vCenter Server and start services" получаю ошибку:

Error

An error occurred while starting service 'vapi-endpoint'
Failed to start the vAPI Endpoint Service
Failed to configure vAPI Endpoint Service at the firstboot time
Resolution

Please file a bug against VAPI

----vapi_firstboot.py_9182_stderr.log

INFO:root:Found 1 matching service. ID is c4aec189-40fd-4f43-bb31-1e39fe92f12b
2021-02-03T08:04:32.842Z ERROR starting vapi-endpoint rc: 1, stdout: , stderr: Start service request failed. Error: Operation timed out

2021-02-03T08:04:32.843Z vapi firstboot failed
Traceback (most recent call last):
File "/usr/lib/vmware-vapi/firstboot/vapi_firstboot.py", line 409, in <module>
sys.exit(Main())
File "/usr/lib/vmware-vapi/firstboot/vapi_firstboot.py", line 387, in Main
vapi_firstboot()
File "/usr/lib/vmware-vapi/firstboot/vapi_firstboot.py", line 375, in vapi_firstboot
actionFirstboot(fbObj)
File "/usr/lib/vmware-vapi/firstboot/vapi_firstboot.py", line 353, in actionFirstboot
actionStart(fbObj)
File "/usr/lib/vmware-vapi/firstboot/vapi_firstboot.py", line 358, in actionStart
startService(msg, fbObj)
File "/usr/lib/vmware-vapi/firstboot/vapi_firstboot.py", line 257, in proxy
return func(*args, **kwargs)
File "/usr/lib/vmware-vapi/firstboot/vapi_firstboot.py", line 312, in startService
fbObj.start_services()
File "/usr/lib/vmware-vapi/firstboot/vapi_firstboot.py", line 187, in start_services
self.start_service()
File "/usr/lib/vmware/site-packages/cis/firstboot.py", line 273, in start_service
service_start(self.get_eff_service_name())
File "/usr/lib/vmware/site-packages/cis/utils.py", line 1006, in service_start
raise ServiceStartException(svc_name)
cis.exceptions.ServiceStartException: {
"detail": [
{
"translatable": "An error occurred while starting service '%(0)s'",
"localized": "An error occurred while starting service 'vapi-endpoint'",
"id": "install.ciscommon.service.failstart",
"args": [
"vapi-endpoint"
]
},
{
"translatable": "Failed to start the vAPI Endpoint Service",
"id": "install.vapi.error.start_service",
"localized": "Failed to start the vAPI Endpoint Service"
},
{
"translatable": "Failed to configure vAPI Endpoint Service at the firstboot time",
"id": "install.vapi.error.firstboot",
"localized": "Failed to configure vAPI Endpoint Service at the firstboot time"
}
],
"resolution": {
"translatable": "Please file a bug against VAPI",
"id": "install.vapi.resolution",
"localized": "Please file a bug against VAPI"
},
"problemId": null,
"componentKey": "vapi"
}

-----

В какую сторону капать?

0 Kudos
1 Solution

Accepted Solutions
Finikiez
Champion
Champion

Да, конечно.

 

VCSA. на который вы перезжаете, должен иметь адрес, который успешно разрешается в имя и наоборот в DNS. Об этом в документации написано

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.upgrade.doc/GUID-A8BD815E-7CA1-45BB...

Network Prerequisites

  • If you plan to assign a static IP address in the temporary network settings of the appliance, verify that you have configured the forward and reverse DNS records for the IP address.
  • If you plan to assign a DHCP IP address in the temporary network settings of the new appliance, verify that the ESXi host on which you want to deploy the new appliance is in the same network as the ESXi host on which the existing vCenter Server Appliance runs.
  • If you plan to assign a DHCP IPv4 address in the temporary network settings of the new appliance, verify that the ESXi host on which you want to deploy the new appliance is connected to at least one network that is associated with a port group which accepts MAC address changes. Note that the default security policy of a distributed virtual switch is to reject MAC address changes. For information about how to configure the security policy for a switch or port group, see vSphere Networking.

 

 

View solution in original post

0 Kudos
9 Replies
Finikiez
Champion
Champion

Добрый день!

 

Не стартует сервис vapi

Причин может быть масса.

Попробуйте посмотреть вот эти статьи

https://kb.vmware.com/s/article/57126

https://kb.vmware.com/s/article/57126

0 Kudos
Apecc
Contributor
Contributor

Доброго времени! 

Эту статью читал. В логе cloudvm.log нет ошибок связанных с днс.

0 Kudos
Finikiez
Champion
Champion

Смотрите. Выходов из ситуации ровно два:

1. Проводить дебаг проблемы по логам или с помощью технической поддержки. Если есть желание - подгрузите архив с логами с аплайнса, где не запускается сервис, попробуем вместе посмотреть.

2. Развернуть новый vcenter сразу 6.7 и виде виртуального аплайнса, переподключив хосты и перенеся нужны настройки. В таком сценарии вы потеряете только исторические данные производительности и историю по task & events.

0 Kudos
Apecc
Contributor
Contributor

Finikiez спасибо что откликнулись на мою беду)

Время поджимало, выбрал 3 путь)) Обновился до 6.7 на windows. На аплайнс решили переходить уже с покупкой 7ки, или позднее попробуем мигрировать на эту же версию.

И все же интересно в чем была ошибка. 

------vmon_syslog.log

...

2021-02-03T08:01:46.692987+00:00 notice vmon <vmcam> Skip service health check. State STOPPED, Curr request 0
2021-02-03T08:01:46.693225+00:00 notice vmon <mbcs> Skip service health check. State STOPPED, Curr request 0
2021-02-03T08:01:46.693476+00:00 notice vmon <content-library> Skip service health check. State STOPPED, Curr request 0
2021-02-03T08:01:46.693715+00:00 notice vmon <pschealth> Skip service health check. State STOPPED, Curr request 0
2021-02-03T08:01:46.693951+00:00 notice vmon <rbd> Skip service health check. State STOPPED, Curr request 0
2021-02-03T08:01:46.694204+00:00 notice vmon <vsm> Skip service health check. State STOPPED, Curr request 0
2021-02-03T08:01:46.694442+00:00 notice vmon <vsan-health> Skip service health check. State STOPPED, Curr request 0
2021-02-03T08:01:46.694682+00:00 notice vmon <updatemgr> Skip service health check. State STOPPED, Curr request 0
2021-02-03T08:01:46.694917+00:00 notice vmon Successfully executed service batch operation API_HEALTH.
2021-02-03T08:01:51.385661+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:01:51.643226+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:01:51.643761+00:00 warning vmon
2021-02-03T08:01:51.664104+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:01:59.665406+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:01:59.959363+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:01:59.959684+00:00 warning vmon
2021-02-03T08:01:59.979998+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:02:07.981780+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:02:08.263721+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:02:08.264109+00:00 warning vmon
2021-02-03T08:02:08.283618+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:02:16.285489+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:02:16.585549+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:02:16.585852+00:00 warning vmon
2021-02-03T08:02:16.608000+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:02:24.610203+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:02:24.905353+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:02:24.905911+00:00 warning vmon
2021-02-03T08:02:24.924674+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:02:32.926200+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:02:33.185812+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:02:33.186294+00:00 warning vmon
2021-02-03T08:02:33.208037+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:02:41.210452+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:02:41.487245+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:02:41.487843+00:00 warning vmon
2021-02-03T08:02:41.507991+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:02:49.509572+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:02:49.768252+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:02:49.768555+00:00 warning vmon
2021-02-03T08:02:49.787868+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:02:57.789654+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:02:58.075624+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:02:58.076502+00:00 warning vmon
2021-02-03T08:02:58.095982+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:03:06.097290+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:03:06.361847+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:03:06.362235+00:00 warning vmon
2021-02-03T08:03:06.387958+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:03:14.390065+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:03:14.645923+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:03:14.646316+00:00 warning vmon
2021-02-03T08:03:14.667985+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:03:22.669466+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:03:22.960048+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:03:22.960385+00:00 warning vmon
2021-02-03T08:03:22.984042+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:03:30.986150+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:03:31.256332+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:03:31.256660+00:00 warning vmon
2021-02-03T08:03:31.280071+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:03:39.281895+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:03:39.555935+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:03:39.556282+00:00 warning vmon
2021-02-03T08:03:39.575975+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:03:47.577365+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:03:47.853147+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:03:47.853471+00:00 warning vmon
2021-02-03T08:03:47.873104+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:03:55.875181+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:03:56.183552+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:03:56.183886+00:00 warning vmon
2021-02-03T08:03:56.211874+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:04:04.214827+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:04:04.491488+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:04:04.491856+00:00 warning vmon
2021-02-03T08:04:04.515997+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:04:12.518466+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:04:12.808668+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:04:12.809063+00:00 warning vmon
2021-02-03T08:04:12.828649+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:04:20.830468+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:04:21.086383+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:04:21.086781+00:00 warning vmon
2021-02-03T08:04:21.107946+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:04:29.110644+00:00 notice vmon <vapi-endpoint-healthcmd> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vapi-endpoint -u /vapiendpoint/health -t 30
2021-02-03T08:04:29.373978+00:00 warning vmon <vapi-endpoint> Service api-health command's stderr: Exception while retrieving health xml from url http://localhost:12346/vapiendpoint/health. Exception: <urlopen error [Errno 111] Connection refused>
2021-02-03T08:04:29.374660+00:00 warning vmon
2021-02-03T08:04:29.394282+00:00 notice vmon <vapi-endpoint> Re-check service health since it is still initializing.
2021-02-03T08:04:32.813112+00:00 notice vmon <vapi-endpoint> Service start operation timed out.
2021-02-03T08:04:32.813714+00:00 warning vmon <vapi-endpoint> Found empty StopSignal parameter in config file. Defaulting to SIGTERM
2021-02-03T08:04:32.841974+00:00 warning vmon <vapi-endpoint> Service exited. Exit code 143
2021-02-03T08:04:42.254161+00:00 notice vmon Client info Uid=0,Gid=0,Pid=15282,Comm=(vmon-cli),PPid=15270,Comm=(service-control),PPid=15122,Comm=(python),PPid=6852,Comm=(invoke_upgrade.),PPid=1,Comm=(systemd),PPid=0
2021-02-03T08:04:42.297959+00:00 notice vmon Client info Uid=0,Gid=0,Pid=15294,Comm=(vmon-cli),PPid=15270,Comm=(service-control),PPid=15122,Comm=(python),PPid=6852,Comm=(invoke_upgrade.),PPid=1,Comm=(systemd),PPid=0
2021-02-03T08:04:42.327855+00:00 notice vmon Client info Uid=0,Gid=0,Pid=15312,Comm=(vmon-cli),PPid=15270,Comm=(service-control),PPid=15122,Comm=(python),PPid=6852,Comm=(invoke_upgrade.),PPid=1,Comm=(systemd),PPid=0

...

-----

0 Kudos
Apecc
Contributor
Contributor

---endpoint.log

повторяется в конце несколько раз

...

2021-02-03T08:04:27.074Z | INFO | state-manager1 | HttpSettingsBuilder | HTTP Endpoint default=http://127.0.0.1, ::1:12346
2021-02-03T08:04:27.074Z | INFO | state-manager1 | DefaultStateManager | Invoking static-configuration-utilities
2021-02-03T08:04:27.110Z | INFO | state-manager1 | DynamicSSLIOSessionStrategy | Reconfiguring trusted certificates.
2021-02-03T08:04:27.112Z | ERROR | state-manager1 | DefaultStateManager | Unexpected error while initializing endpoint runtime state.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sslIoSessionStrategy' defined in class path resource [config-dependent-beans-static.xml]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.vapi.endpoint.api.DynamicSSLIOSessionStrategy]: Factory method 'buildSslIoSessionStrategy' threw exception; nested exception is com.vmware.provider.VecsException: Native platform error [code: 5][Native platform error [code: 5][Begin enum on store 'TRUSTED_ROOTS' failed. [Server: __localhost__, User: __localuser__]]]
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1071)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:511)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:756)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:542)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:105)
at com.vmware.vapi.endpoint.props.ConfigurationUtilitiesBuilder.createApplicationContext(ConfigurationUtilitiesBuilder.java:110)
at com.vmware.vapi.endpoint.props.ConfigurationUtilitiesBuilder.doConfig(ConfigurationUtilitiesBuilder.java:116)
at com.vmware.vapi.endpoint.props.ConfigurationUtilitiesBuilder.buildInitial(ConfigurationUtilitiesBuilder.java:41)
at com.vmware.vapi.state.impl.DefaultStateManager.build(DefaultStateManager.java:353)
at com.vmware.vapi.state.impl.DefaultStateManager$1.doInitialConfig(DefaultStateManager.java:167)
at com.vmware.vapi.state.impl.DefaultStateManager$1.run(DefaultStateManager.java:150)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.vapi.endpoint.api.DynamicSSLIOSessionStrategy]: Factory method 'buildSslIoSessionStrategy' threw exception; nested exception is com.vmware.provider.VecsException: Native platform error [code: 5][Native platform error [code: 5][Begin enum on store 'TRUSTED_ROOTS' failed. [Server: __localhost__, User: __localuser__]]]
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:189)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588)
... 26 more
Caused by: com.vmware.provider.VecsException: Native platform error [code: 5][Native platform error [code: 5][Begin enum on store 'TRUSTED_ROOTS' failed. [Server: __localhost__, User: __localuser__]]]
at com.vmware.provider.VecsKeyStoreEngine.engineAliases(VecsKeyStoreEngine.java:79)
at java.security.KeyStore.aliases(KeyStore.java:1235)
at com.vmware.vapi.endpoint.api.DynamicSSLIOSessionStrategy.createAggregatedStrategy(DynamicSSLIOSessionStrategy.java:89)
at com.vmware.vapi.endpoint.api.DynamicSSLIOSessionStrategy.<init>(DynamicSSLIOSessionStrategy.java:59)
at com.vmware.vapi.endpoint.api.HttpClientFactory.buildSslIoSessionStrategy(HttpClientFactory.java:98)
at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162)
... 27 more
Caused by: com.vmware.identity.vecs.VecsGenericException: Native platform error [code: 5][Begin enum on store 'TRUSTED_ROOTS' failed. [Server: __localhost__, User: __localuser__]]
at com.vmware.identity.vecs.VecsEntryEnumeration.BAIL_ON_ERROR(VecsEntryEnumeration.java:108)
at com.vmware.identity.vecs.VecsEntryEnumeration.beginEnumEntries(VecsEntryEnumeration.java:130)
at com.vmware.identity.vecs.VecsEntryEnumeration.<init>(VecsEntryEnumeration.java:35)
at com.vmware.identity.vecs.VMwareEndpointCertificateStore.enumerateEntries(VMwareEndpointCertificateStore.java:379)
at com.vmware.provider.VecsKeyStoreEngine.engineAliases(VecsKeyStoreEngine.java:71)
... 35 more
2021-02-03T08:04:27.113Z | INFO | state-manager1 | HealthStatusCollectorImpl | HEALTH ORANGE Application error has occurred. Please check log files for more information.
2021-02-03T08:04:27.113Z | INFO | state-manager1 | HealthStatusCollectorImpl | HEALTH GREEN Current vApi Endpoint health status is created between 2021-02-03T08:04:27UTC and 2021-02-03T08:04:27UTC.
2021-02-03T08:04:27.113Z | INFO | state-manager1 | HealthConfigurationEventListener | Computed health status is = ORANGE
2021-02-03T08:04:27.113Z | INFO | state-manager1 | HealthConfigurationEventListener | HEALTH Application error has occurred. Please check log files for more information.
2021-02-03T08:04:27.113Z | INFO | state-manager1 | HealthConfigurationEventListener | HEALTH Current vApi Endpoint health status is created between 2021-02-03T08:04:27UTC and 2021-02-03T08:04:27UTC.
2021-02-03T08:04:27.113Z | INFO | state-manager1 | DefaultStateManager | lock
2021-02-03T08:04:27.113Z | INFO | state-manager1 | DefaultStateManager | Initial state build failed. Will retry after 5 seconds.
2021-02-03T08:04:27.113Z | INFO | state-manager1 | DefaultStateManager | unlock
2021-02-03T08:04:32.113Z | INFO | state-manager1 | DefaultStateManager | Start initializing API Endpoint runtime state. State check interval 240 sec.
2021-02-03T08:04:32.113Z | INFO | state-manager1 | DefaultStateManager | Creating runtime state context.
2021-02-03T08:04:32.114Z | INFO | state-manager1 | DefaultStateManager | Invoking patch-builder
2021-02-03T08:04:32.114Z | INFO | state-manager1 | DefaultStateManager | Invoking log4j-config-builder
2021-02-03T08:04:32.114Z | INFO | state-manager1 | Log4jConfigBuilder | Watching log4j configuration at /etc/vmware-vapi/endpoint-log4j.properties for changes.
2021-02-03T08:04:32.115Z | INFO | state-manager1 | DefaultStateManager | Invoking init-configuration-builder
2021-02-03T08:04:32.115Z | INFO | state-manager1 | DefaultStateManager | Invoking properties-builder
2021-02-03T08:04:32.115Z | INFO | state-manager1 | LocalPropertiesFileStateBuilder | Will be configuring from following locations: file:/etc/vmware-vapi/endpoint.properties
2021-02-03T08:04:32.115Z | INFO | state-manager1 | LocalPropertiesFileStateBuilder | Resource URL [file:/etc/vmware-vapi/endpoint.properties] was parsed successfully into set of properties.
2021-02-03T08:04:32.115Z | INFO | state-manager1 | DefaultStateManager | Invoking feature-state-switch-builder
2021-02-03T08:04:32.115Z | INFO | state-manager1 | DefaultStateManager | Invoking state-manager
2021-02-03T08:04:32.115Z | INFO | state-manager1 | DefaultStateManager | State check interval property found 240.
2021-02-03T08:04:32.116Z | INFO | state-manager1 | DefaultStateManager | State check delay property found 240.
2021-02-03T08:04:32.116Z | INFO | state-manager1 | DefaultStateManager | Invoking keystore-builder
2021-02-03T08:04:32.116Z | INFO | state-manager1 | DefaultStateManager | Invoking endpoint-settings-builder
2021-02-03T08:04:32.122Z | INFO | state-manager1 | DefaultStateManager | Invoking lookup-service-client-builder
2021-02-03T08:04:32.122Z | INFO | state-manager1 | DefaultStateManager | Invoking http-settings-builder
2021-02-03T08:04:32.122Z | INFO | state-manager1 | HttpSettingsBuilder | HTTP Endpoint default=http://127.0.0.1, ::1:12346
2021-02-03T08:04:32.122Z | INFO | state-manager1 | DefaultStateManager | Invoking static-configuration-utilities
2021-02-03T08:04:32.172Z | INFO | state-manager1 | DynamicSSLIOSessionStrategy | Reconfiguring trusted certificates.
2021-02-03T08:04:32.174Z | ERROR | state-manager1 | DefaultStateManager | Unexpected error while initializing endpoint runtime state.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sslIoSessionStrategy' defined in class path resource [config-dependent-beans-static.xml]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.vapi.endpoint.api.DynamicSSLIOSessionStrategy]: Factory method 'buildSslIoSessionStrategy' threw exception; nested exception is com.vmware.provider.VecsException: Native platform error [code: 5][Native platform error [code: 5][Begin enum on store 'TRUSTED_ROOTS' failed. [Server: __localhost__, User: __localuser__]]]
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1071)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:511)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:756)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:542)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:105)
at com.vmware.vapi.endpoint.props.ConfigurationUtilitiesBuilder.createApplicationContext(ConfigurationUtilitiesBuilder.java:110)
at com.vmware.vapi.endpoint.props.ConfigurationUtilitiesBuilder.doConfig(ConfigurationUtilitiesBuilder.java:116)
at com.vmware.vapi.endpoint.props.ConfigurationUtilitiesBuilder.buildInitial(ConfigurationUtilitiesBuilder.java:41)
at com.vmware.vapi.state.impl.DefaultStateManager.build(DefaultStateManager.java:353)
at com.vmware.vapi.state.impl.DefaultStateManager$1.doInitialConfig(DefaultStateManager.java:167)
at com.vmware.vapi.state.impl.DefaultStateManager$1.run(DefaultStateManager.java:150)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.vapi.endpoint.api.DynamicSSLIOSessionStrategy]: Factory method 'buildSslIoSessionStrategy' threw exception; nested exception is com.vmware.provider.VecsException: Native platform error [code: 5][Native platform error [code: 5][Begin enum on store 'TRUSTED_ROOTS' failed. [Server: __localhost__, User: __localuser__]]]
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:189)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588)
... 26 more
Caused by: com.vmware.provider.VecsException: Native platform error [code: 5][Native platform error [code: 5][Begin enum on store 'TRUSTED_ROOTS' failed. [Server: __localhost__, User: __localuser__]]]
at com.vmware.provider.VecsKeyStoreEngine.engineAliases(VecsKeyStoreEngine.java:79)
at java.security.KeyStore.aliases(KeyStore.java:1235)
at com.vmware.vapi.endpoint.api.DynamicSSLIOSessionStrategy.createAggregatedStrategy(DynamicSSLIOSessionStrategy.java:89)
at com.vmware.vapi.endpoint.api.DynamicSSLIOSessionStrategy.<init>(DynamicSSLIOSessionStrategy.java:59)
at com.vmware.vapi.endpoint.api.HttpClientFactory.buildSslIoSessionStrategy(HttpClientFactory.java:98)
at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162)
... 27 more
Caused by: com.vmware.identity.vecs.VecsGenericException: Native platform error [code: 5][Begin enum on store 'TRUSTED_ROOTS' failed. [Server: __localhost__, User: __localuser__]]
at com.vmware.identity.vecs.VecsEntryEnumeration.BAIL_ON_ERROR(VecsEntryEnumeration.java:108)
at com.vmware.identity.vecs.VecsEntryEnumeration.beginEnumEntries(VecsEntryEnumeration.java:130)
at com.vmware.identity.vecs.VecsEntryEnumeration.<init>(VecsEntryEnumeration.java:35)
at com.vmware.identity.vecs.VMwareEndpointCertificateStore.enumerateEntries(VMwareEndpointCertificateStore.java:379)
at com.vmware.provider.VecsKeyStoreEngine.engineAliases(VecsKeyStoreEngine.java:71)
... 35 more
2021-02-03T08:04:32.174Z | INFO | state-manager1 | HealthStatusCollectorImpl | HEALTH ORANGE Application error has occurred. Please check log files for more information.
2021-02-03T08:04:32.174Z | INFO | state-manager1 | HealthStatusCollectorImpl | HEALTH GREEN Current vApi Endpoint health status is created between 2021-02-03T08:04:32UTC and 2021-02-03T08:04:32UTC.
2021-02-03T08:04:32.174Z | INFO | state-manager1 | HealthConfigurationEventListener | Computed health status is = ORANGE
2021-02-03T08:04:32.174Z | INFO | state-manager1 | HealthConfigurationEventListener | HEALTH Application error has occurred. Please check log files for more information.
2021-02-03T08:04:32.174Z | INFO | state-manager1 | HealthConfigurationEventListener | HEALTH Current vApi Endpoint health status is created between 2021-02-03T08:04:32UTC and 2021-02-03T08:04:32UTC.
2021-02-03T08:04:32.175Z | INFO | state-manager1 | DefaultStateManager | lock
2021-02-03T08:04:32.175Z | INFO | state-manager1 | DefaultStateManager | Initial state build failed. Will retry after 5 seconds.
2021-02-03T08:04:32.175Z | INFO | state-manager1 | DefaultStateManager | unlock
2021-02-03T08:04:32.815Z | INFO | shutdown-hook | ApiEndpointServer | Start shutting down...
2021-02-03T08:04:32.815Z | INFO | shutdown-hook | DefaultStateManager | shutdown
2021-02-03T08:04:32.821Z | INFO | shutdown-hook | ApiEndpointServer | Shutdown.

---

 

0 Kudos
Finikiez
Champion
Champion

Если судить по этому логу, то ошибка как раз связана с вопросом разрешения имени на целевом аплайнсе

Это статья в KB - https://kb.vmware.com/s/article/57126

Суть в том, для аплайнса, который разворачивается, должны быть заведены записи в DNS и успешно резолвиться его имя.

0 Kudos
Apecc
Contributor
Contributor

Я правильно понимаю: временный ip надо так же прописать в днс ? Для существующего вц в днс записи настроены корректно, иначе апгрейд бы не прошел.

0 Kudos
Finikiez
Champion
Champion

Да, конечно.

 

VCSA. на который вы перезжаете, должен иметь адрес, который успешно разрешается в имя и наоборот в DNS. Об этом в документации написано

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.upgrade.doc/GUID-A8BD815E-7CA1-45BB...

Network Prerequisites

  • If you plan to assign a static IP address in the temporary network settings of the appliance, verify that you have configured the forward and reverse DNS records for the IP address.
  • If you plan to assign a DHCP IP address in the temporary network settings of the new appliance, verify that the ESXi host on which you want to deploy the new appliance is in the same network as the ESXi host on which the existing vCenter Server Appliance runs.
  • If you plan to assign a DHCP IPv4 address in the temporary network settings of the new appliance, verify that the ESXi host on which you want to deploy the new appliance is connected to at least one network that is associated with a port group which accepts MAC address changes. Note that the default security policy of a distributed virtual switch is to reject MAC address changes. For information about how to configure the security policy for a switch or port group, see vSphere Networking.

 

 

View solution in original post

0 Kudos
Apecc
Contributor
Contributor

Большое СПАСИБО!!! Для временного айпи этого сделано не было, почему то подумал что не надо(((. К сожалению проверить смогу не скоро. Сейчас занимаюсь апгрейдом хостов. 

Tags (1)
0 Kudos