Hi all,
I'am having an issue with starting VCSA 6.7 latest version (photon os)
Management on port 5480 is working fine.
I'am getting error
Already checked the diskspace (after reading other posts) -> seems no issue to me
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.9G 0 7.9G 0% /dev
tmpfs 7.9G 732K 7.9G 1% /dev/shm
tmpfs 7.9G 684K 7.9G 1% /run
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
/dev/sda3 11G 6.6G 3.5G 66% /
tmpfs 7.9G 864K 7.9G 1% /tmp
/dev/mapper/netdump_vg-netdump 985M 1.3M 916M 1% /storage/netdump
/dev/mapper/seat_vg-seat 25G 542M 23G 3% /storage/seat
/dev/mapper/log_vg-log 9.8G 4.2G 5.1G 46% /storage/log
/dev/mapper/imagebuilder_vg-imagebuilder 9.8G 23M 9.2G 1% /storage/imagebuilder
/dev/mapper/dblog_vg-dblog 15G 150M 14G 2% /storage/dblog
/dev/mapper/autodeploy_vg-autodeploy 9.8G 34M 9.2G 1% /storage/autodeploy
/dev/mapper/core_vg-core 50G 2.1G 45G 5% /storage/core
/dev/mapper/db_vg-db 9.8G 541M 8.7G 6% /storage/db
/dev/sda1 120M 34M 77M 31% /boot
/dev/mapper/updatemgr_vg-updatemgr 99G 77M 94G 1% /storage/updatemgr
/dev/mapper/archive_vg-archive 50G 47G 15M 100% /storage/archive
DNS and reserve DNS resolving is working
When I start the services I get error below..
service-control --start --all
Operation not cancellable. Please wait for it to finish...
Performing start operation on service lwsmd...
Successfully started service lwsmd
Performing start operation on service vmafdd...
Successfully started service vmafdd
Performing start operation on service vmdird...
Successfully started service vmdird
Performing start operation on service vmcad...
Successfully started service vmcad
Performing start operation on service vmware-sts-idmd...
Successfully started service vmware-sts-idmd
Performing start operation on service vmware-stsd...
Successfully started service vmware-stsd
Performing start operation on service vmdnsd...
Successfully started service vmdnsd
Performing start operation on profile: ALL...
Service-control failed. Error: Failed to start services in profile ALL. RC=1, stderr=Failed to start vapi-endpoint, vpxd-svcs services. Error: Operation timed out
The /var/log/vmware/vapi/endpoint/endpoint.log is attached
Tnx you so much for your feedback and help!!
Cheers
Geoffrey
Is this a new deployment that is failing from the beginning or an existing deployment that once worked but now isn't?
Hey ICTKoHo,
Reading a little bit on your logs i found the next error inside the vpxd one:
2020-08-23T21:51:45.436Z error vpxd[21441] [Originator@6876 sub=HostGateway] [CisConnection]: Error getting trusted STS certificates: Fault cause: vmodl.fault.SystemError
This error could be related to your STS certificates to be expired. To re-create them you will need to follow the next procedure; Generate a New STS Signing Certificate on the Appliance
If you hold an external PSC you will need to do it inside the VM that holds that.
agree with Lalegre
There is one guy in the community that faced exactly this issue and he resolved it: vcenter does not start.
Maybe it is easier for you if you follow the full procedure there.
Also want to did you rename the vCenter by any chance after you deploy it? seen that ever before but with renaming vCenter DNS name after deployment in 6.5
Hi all,
First of all a big thank you for your feedback and help. Resetting the CERTS was indeed the right move.
Tnx VPXD service start and I'am able to login to vcenter
Yet one service remains failing to start..
service-control --start vmware-updatemgr
Operation not cancellable. Please wait for it to finish...
Performing start operation on service updatemgr...
Error executing start on service updatemgr. Details {
"problemId": null,
"resolution": null,
"componentKey": null,
"detail": [
{
"translatable": "An error occurred while starting service '%(0)s'",
"args": [
"updatemgr"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'updatemgr'"
}
]
}
Service-control failed. Error: {
"problemId": null,
"resolution": null,
"componentKey": null,
"detail": [
{
"translatable": "An error occurred while starting service '%(0)s'",
"args": [
"updatemgr"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'updatemgr'"
}
]
}
Looking in log /var/log/vmware/vmware-updatemgr/refreshCerts-utility.log
[2020-08-26 21:55:27,241 ERROR] Unable to update VUM service info
[2020-08-26 22:00:43,669 INFO] Creating/Updating key file: /usr/lib/vmware-updatemgr/bin/ssl/rui.key
[2020-08-26 22:00:43,670 INFO] Creating/Updating certificate file: /usr/lib/vmware-updatemgr/bin/ssl/rui.crt
[2020-08-26 22:00:43,672 INFO] Creating/Updating key file: /usr/lib/vmware-updatemgr/bin/ssl/jetty.key
[2020-08-26 22:00:43,672 INFO] Creating/Updating certificate file: /usr/lib/vmware-updatemgr/bin/ssl/jetty.crt
[2020-08-26 22:00:43,673 INFO] Install Key store for Jetty
[2020-08-26 22:00:45,006 INFO] Keystore installed successfully.
[2020-08-26 22:00:45,006 INFO] Enter registerWithVcNoRestart
[2020-08-26 22:00:45,010 INFO] command: ['/usr/lib/vmware-vmafd/bin/vmafd-cli', 'get-ls-location', '--server-name', 'localhost']
[2020-08-26 22:00:45,033 INFO] rc: 0, stdout: https://vcenter.koho.be/lookupservice/sdk
, stderr:
[2020-08-26 22:00:45,033 INFO] lsUrl: https://vcenter.koho.be/lookupservice/sdk
[2020-08-26 22:00:45,089 INFO] command: ['/usr/lib/vmware-vmafd/bin/vmafd-cli', 'get-ls-location', '--server-name', 'localhost']
[2020-08-26 22:00:45,111 INFO] rc: 0, stdout: https://vcenter.koho.be/lookupservice/sdk
, stderr:
[2020-08-26 22:00:45,111 INFO] lsUrl: https://vcenter.koho.be/lookupservice/sdk
[2020-08-26 22:00:45,120 INFO] Querying LS for Local vCenter Server.
[2020-08-26 22:00:45,171 INFO] Found VC(https://vcenter.koho.be:443/sdk)
[2020-08-26 22:00:45,233 INFO] Updating VUM extension with VC
[2020-08-26 22:00:45,460 INFO] Updating VUM service info
[2020-08-26 22:00:45,460 INFO] Enter updateServiceInfo.
[2020-08-26 22:00:45,461 INFO] command: ['/usr/lib/vmware-vmafd/bin/vmafd-cli', 'get-ls-location', '--server-name', 'localhost']
[2020-08-26 22:00:45,494 INFO] rc: 0, stdout: https://vcenter.koho.be/lookupservice/sdk
, stderr:
[2020-08-26 22:00:45,494 INFO] lsUrl: https://vcenter.koho.be/lookupservice/sdk
[2020-08-26 22:00:45,502 INFO] command: ['/usr/lib/vmware-vmafd/bin/vmafd-cli', 'get-ls-location', '--server-name', 'localhost']
[2020-08-26 22:00:45,529 INFO] rc: 0, stdout: https://vcenter.koho.be/lookupservice/sdk
, stderr:
[2020-08-26 22:00:45,529 INFO] lsUrl: https://vcenter.koho.be/lookupservice/sdk
[2020-08-26 22:00:45,570 INFO] Client's property file: /usr/lib/vmware-updatemgr/firstboot/updatemgr.properties
[2020-08-26 22:00:45,583 INFO] Updating version to 6.7.0.42095
[2020-08-26 22:00:45,660 ERROR] Can't update VUM service info: (vmodl.fault.InvalidArgument) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = '',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) [],
invalidProperty = 'Invalid certificate'
}
Traceback (most recent call last):
File "/usr/lib/vmware-updatemgr/bin/vumUtils.py", line 370, in updateServiceInfo
lsClient.ReRegister(vumServiceInfo.serviceId, setSpec)
File "/usr/lib/vmware-updatemgr/bin/vumUtils.py", line 813, in addSecurityctxToRequests
reqMethod(self, *args)
File "/usr/lib/vmware-updatemgr/bin/vumUtils.py", line 823, in ReRegister
sr.Set(svcId, newSpec)
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 557, in <lambda>
self.f(*(self.args + (obj,) + args), **kwargs)
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 363, in _InvokeMethod
return self._stub.InvokeMethod(self, info, args)
File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1418, in InvokeMethod
raise obj # pylint: disable-msg=E0702
pyVmomi.VmomiSupport.vmodl.fault.InvalidArgument: (vmodl.fault.InvalidArgument) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = '',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) [],
invalidProperty = 'Invalid certificate'
}
[2020-08-26 22:00:45,662 ERROR] Unable to update VUM service info
I see -> Invalid certificate
I renewed the certificates with the certificate manager..
Do I need to perform an extra step for the update manager?
Tx all!!
update manager might be using wrong cert i believe and you can try the steps below from kb
/usr/lib/vmware-updatemgr/bin/updatemgr-util refresh-certs
/usr/lib/vmware-updatemgr/bin/updatemgr-util register-vc
service-control --start vmware-updatemgr
thanks,
MS
Hi Msripada,
Tnx for your feedback.
I saw the KB and tried it..
Yet the
/usr/lib/vmware-updatemgr/bin/updatemgr-util refresh-certs
command does not work ->
/usr/lib/vmware-updatemgr/bin/updatemgr-util refresh-certs
bash: /usr/lib/vmware-updatemgr/bin/updatemgr-util: No such file or directory
usage: updatemgr-util [-h] {register-vc,reset-db,config} ...
Using option "reset-db", "register-vc" or "config -s" will restart vSphere Update Manager service if it was already running
positional arguments:
{register-vc,reset-db,config}
register-vc Re-register vSphere Update Manager with vCenter
reset-db Reset vSphere Update Manager Database
config View/Modify vSphere Update Manager configuration file.
optional arguments:
-h, --help show this help message and exit