I am observing that in our monitoring tool , while getting the datastore status through api call , we get connection time out error.
Operation timed out after 30000 milliseconds with 0 out of -1 bytes received (28)
This error is active for 5-7 minutes daily at a fixed time and then disappears. Thereafter vcenter functions normal.
During the error vcenter remains inactive and does not accept new session authentication.
Hi Guys
We've been Experiencing this error / bug / problem in vCenter 7 whenever we do the ff:
- Test High Availability (VMs restarts on the other server except for the vCenter Server)
After powering on the esxi host where the vCenter is residing and the vCenter Server the error occurs
Tried the ff: re-installing, checking VM Hardware Version, checking the OS: no Photon OS in the list. restarting services but nothing works
in the end we need to restore our back-up.
Screen shot below
Thanks!
Hi guys,
I am trying to replace ssl certificate for vcenter 6.7. In which I am having client certificate and client key. But I dont have any idea about Signing certificate. I am having commercial pfx certificate for my domain. Can I create Signing certificate from this using openssl? If so, how?
Any help?
I'm looking for the best strategy for moving our vCenter Appliance to a new management subnet (subnet B), and that VCSA is currently on the same subnet as the hosts in the cluster (subnet A). Our setup is below.
Environment (1 cluster):
3 ESXi 6.5 hosts on subnet A
1 VCSA 6.5 on subnet A
Management (subnet B) is firewalled/routed from subnet A
Questions:
How do I change the IP/Hostname of the VCSA to one in subnet B, and still manage the hosts in subnet A? What ports are required for a firewall for the VCSA to manage them, and if I want to change the hosts to subnet B, will I need to remove them from the cluster, change their IPs/hostnames and then add them back?
Hello,
We have couple "DataCenters" in the VCenter.
I hold full administrative rights on my.
All work fine except of i can't add users and create alarms
following error occur
you do not hold privilege "system > read" on folder "data centers"
Any directions when to start investigate?
Hi,
I'm setting up the CL in our environment and only got an issue in 1 vCenter.
The team who will be using the CL are having the error below for CHVPK (HOU150-MASTER)
but don't have any issues on the other two. As already mentioned on the title. These 3 sites are on linked mode and only one having permission issues.
Any idea what's the problem?
Thanks
Dear all !
Is technically possible to clone a VM (Windows 2016) with vCenter/VUM (6.7.0) from one ESXi host (version 6.5.0 U2) where that vCenter/VUM VM is running on to an other ESXi host (version 6.7.0 P01) in the same cluster ?
My intention is to clone that vCenter/VUM VM from host 1 to host 2, shut down vCenter/VUM VM on host 1, register the cloned VM via vSphere Web Client on host 2 (if needed at all when not already registered by vCenter cloning before), start that cloned VM on host 2, do the ESXi upgrade of host 1 via vCenter/VUM, clone vCenter/VUM from host 2 to host 1, shut down vCenter/VUM VM on host 2, register the cloned VM via vSphere Web Client on host 1 (if needed at all when not already registered by vCenter cloning before), start that VM on host 1 and delete the cloned VM on host 2 and the former original VM on host 1.
I can neither use vMotion (not licensed) nor Veeam B&R as "Planned Failover" etc. scenarios do not work as that job is also dependent on vCenter running as it serves as the "root" of the infrastructure...when such "Planned Failover" job for that vCenter VM is started the replication works well as well as the shut down of the vCenter/VUM VM but then the job ends with error...as the vCenter/VUM - as the root of the infrastructure - does not exist anymore.
Many thx for your thoughts !
If this does not work at all of course a manual upgrade of host 1 via iso or zip via vib etc. will work always but I like using vCenter/VUM quite much.
Kind regards
Christian
(this is on the latest version of vCenter 6.7)
I had to re-install vCenter which I did with the same FQDN and IP address.
When I try to connect via Safari I get the message 'Safari can't open the page "FQDN" because Safari can't establish a secure connection to the server "FQDN"
I can connect via Firefox and Chrome just fine. I have cleared cache, cookies, history and still didn't work.
Last time I had this problem I had to completely re-install my Mac. Surely there must be an easier solution.
The vCenter Console Access permissions on vm's works fine and the user's are able to view the Console of the vm from vCenter, but when they connect to the vCenter via VMware Workstation they are unable to view the Console of the vm's where they have the Console Access permissions. So now what kind of permissions are required to view the vm Console via VMware Workstation ?
vCenter ver 6.5
Workstation ver 15.x
On vCenter 6.7 when I reboot I have to restart the statsmonitor service every time, what is the fix for this ?
Author : Joseph Sciallo
Topic Name : Active Directory LDAP Server and OpenLDAP Server Identity Source Settings
Publication Name : Platform Services Controller Administration
Product/Version : VMware vSphere/6.7
Question :
How can I check whether the source can be reached via port 636. I'm using the vcsa console
So I ran into an issue where the datastore my VCSA (6.7 U2a) sat on ran out of space which caused all sorts of issues. Fortunately I was able to free up some space but since then I haven't been able to get into the VCSA UI, I can access the VAMI but that's it...
I checked the services and can see most of them haven't started
So I attempted to start VMware-vpxd but unfortunately it just fails with the error:
In the vpxd-svcs log I noticed an error stating it couldn't access the LDAP server so I checked and confirmed vmdird is currently stopped. I tried to start this but it failed im seeing these errors now:
Does anyone have any suggestions on how to fix this?
Hello all,
We have a new security policy for passwords expiration in place, this is causing all windows user passwords to expire after 90 days, we have had some problems with vcenter service users as when they expire vcenter crashes, i'm working to mark those user as service user id's to make them non-expiry but a there is a requisite to disable RDP for all of them, my doubt is, disabling RDP feature on vCenter local winows users would affect vCenter functionality in any way?
Thanks in advance for your help.
I have just installed two Vcenter 6.5 systems and they are in linked mode. When I login with the administrator@vsphere.local account and all works fine. I have setup the SSO and I can login with my user account but the linked vcenter does not appear as a linked system? I seems like when I am logged in as the administrator@vsphere.local account the SSO information is the same on both systems.
Any ideas what to check?
Running VCSA 6.7.0.42300 and attempting to upgrade to 7.0.0.10100. The new VCSA is deployed fine, and during stage 2 right after the pre-upgrade tests are run I receive the following error.
Internal error occurs during execution of upgrade process.
Please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.
I reviewed the logs and in the "requirements-upgrade-runner.log" the last error is this:
2020-04-03T05:27:57.786Z INFO utils.loginspec_utils User credentials based login specification.
2020-04-03T05:27:57.787Z INFO utils.loginspec_utils The vCenter Server username and password are specified.
2020-04-03T05:27:57.804Z INFO bindings.vc_binding User credentials based authentication.
2020-04-03T05:27:57.863Z INFO deployer.migration_env_deployer Updating extension -- com.vmware.migrate-connector.127.0.0.1
2020-04-03T05:27:57.932Z ERROR UpgradeRunner Upgrade Runner has encountered an exception
Traceback (most recent call last):
File "/tmp/vmware-upgrade-temp-dirdvIaAnB9OK/tmp8khvlEWIMa/UpgradeRunner.py", line 1889, in main
envDeployer.setup(srcTargets, destTargets, isRegVcExt)
File "/tmp/vmware-upgrade-temp-dirdvIaAnB9OK/tmp8khvlEWIMa/py/deployer/migration_env_deployer.py", line 563, in setup
self._setupTargets(srcTargetsToSetup, False, isRegVcExt)
File "/tmp/vmware-upgrade-temp-dirdvIaAnB9OK/tmp8khvlEWIMa/py/deployer/migration_env_deployer.py", line 535, in _setupTargets
self._registerTargetAsExtension(targetConfig)
File "/tmp/vmware-upgrade-temp-dirdvIaAnB9OK/tmp8khvlEWIMa/py/deployer/migration_env_deployer.py", line 345, in _registerTargetAsExtension
_registerExtension(srcSi, extKey, extCertificate)
File "/tmp/vmware-upgrade-temp-dirdvIaAnB9OK/tmp8khvlEWIMa/py/deployer/migration_env_deployer.py", line 78, in _registerExtension
em.UpdateExtension(ext)
File "/tmp/vmware-upgrade-temp-dirdvIaAnB9OK/tmp8khvlEWIMa/libs/pyVmomi.zip/pyVmomi/VmomiSupport.py", line 556, in <lambda>
self.f(*(self.args + (obj,) + args), **kwargs)
File "/tmp/vmware-upgrade-temp-dirdvIaAnB9OK/tmp8khvlEWIMa/libs/pyVmomi.zip/pyVmomi/VmomiSupport.py", line 368, in _InvokeMethod
return self._stub.InvokeMethod(self, info, args)
File "/tmp/vmware-upgrade-temp-dirdvIaAnB9OK/tmp8khvlEWIMa/libs/pyVmomi.zip/pyVmomi/SoapAdapter.py", line 1481, in InvokeMethod
raise obj # pylint: disable-msg=E0702
pyVmomi.VmomiSupport.vmodl.fault.SystemError: (vmodl.fault.SystemError) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = 'lookup.fault.EntryNotFoundFault',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) [],
reason = 'Invalid fault'
}
Please advise on how to further troubleshoot the upgrade.
Hi,
I have now upgraded my older vCenter Essentials 6.7U3 to the
After the complete check I was unable go to the updates menus (baselines, HW Tools, VM Hardware). I have there still the rotating wheel.
So I cant acces the Baselines and set it to upgrade my hosts.
I have also I thing with it builded another issues or problems:
1. In LifeCycle manager I have these error: Status 404 - https://x.x.x.x/ui/vum-ui/rest/vcenters/5a8080e2-5dca-434a-87f4-303c3cb3f9b1/compliance
2. Anny update menu (submenu or settins) end with rotating wheel
3. By patch Setup menu have unexpected error
Please is possible to help me?
Thanks.
Hello,
We are currently seeing the following error when upgrading to VCSA 7.0 from 6.7, this error occurs durning step 2 of the new VCSA.
Error
Encountered an internal error. Traceback (most recent call last): File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1752, in main vmidentityFB.boot() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 367, in boot self.registerTokenServiceWithLookupService() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 654, in registerTokenServiceWithLookupService raise e File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 650, in registerTokenServiceWithLookupService dynVars=dynVars) File "/usr/lib/vmware-cm/bin/cloudvmcisreg.py", line 710, in cloudvm_sso_cm_register serviceId = do_lsauthz_operation(cisreg_opts_dict) File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 1058, in do_lsauthz_operation ls_obj = LookupServiceClient(ls_url, retry_count=60) File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 314, in __init__ self._init_service_content() File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 294, in do_retry return req_method(self, *args, **kargs) File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 304, in _init_service_content self.service_content = si.RetrieveServiceContent() File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 556, in <lambda> self.f(*(self.args + (obj,) + args), **kwargs) File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 368, in _InvokeMethod return self._stub.InvokeMethod(self, info, args) File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1448, in InvokeMethod conn.request('POST', self.path, req, headers) File "/usr/lib/python3.7/http/client.py", line 1252, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1298, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1247, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1026, in _send_output self.send(msg) File "/usr/lib/python3.7/http/client.py", line 966, in send self.connect() File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1085, in connect six.moves.http_client.HTTPSConnection.connect(self) File "/usr/lib/python3.7/http/client.py", line 1414, in connect super().connect() File "/usr/lib/python3.7/http/client.py", line 938, in connect (self.host,self.port), self.timeout, self.source_address) File "/usr/lib/python3.7/socket.py", line 727, in create_connection raise err File "/usr/lib/python3.7/socket.py", line 716, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused
Resolution
This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.
We are currently unsure why this error is occurring. This error appears as the Security Token Service (STS) is starting up during the install.
is it possible to install VC appliance version 7 machine with my existing Vcenter 6.7.
not comfortable of upgrade but rather install a new VM instead of upgrade is it possible? if not, can you provide me upgrade path and documents.
Thanks
Our vCenter 6.7 server has crashed and it wont come up
I'm planning to do a fresh installation of vCenter 6.7. I'm not well versed in vCenter so I have few queries.
1) Do I need to migrate the postgres DB ?
2) Any additional licenses required for vCenter or can we use the same license key which we use in the ESXi servers ?
vcenter 6.5 u2 is not starting . Also I restored from backup ( 15 days ago ) but I get the same error again.
Successfully started service vmware-psc-client
Service-control failed. Error Failed to start vmon services.vmon-cli RC=2, stderr=Failed to start sca, cm services. Error: Service crashed while starting
root@photon-machine [ ~ ]# service-control –status
Service-control failed. Error Exactly one operation must be specified.
root@photon-machine [ ~ ]#
503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x000055dcd9b8e220] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)