Hi,
i installed a new VCenter 6.7 Appliance. But if i want to add the a new Storage Provider for my EMC Unity Vcenter tells me he cannot create a new signed Certificate
My first try was to reset all the Certificates for the Vcenter over SSH. But dosent Help.
Bei der Bereitstellung eines signierten Zertifikats der VMware Certificate Authority (VMCA) für den Anbieter ist ein Problem aufgetreten.
Hello, new to vmware ESXI vCenter. Always used the standalone vpshere app or web interface for administration.
I've installed a new Windows 2016 Standard edition VM, joined it to the domain (lets call that labs.xyz.com) and installed the latest vcenter 6.7 Windows installer.
It's installed without issue - If I load up the vcenter link, I've installed the login plugins required as well as enabled Flash for that only (as it moans about needing it).
I just can't seem to login whatever I try.
I've tried Administrator@labs.xyz.com and administrator@labs.zyx.com, in case it is case sensitive in the SSO. The password for this I am using the domain login, which works fine.
I've tried administrator on it's own, plus the SSO password set during the install process.
I've also tried using root, administrator and many other combinations, sometimes with "vmware" as the password, as some places online suggest this.
I've also tried the NETBIOS login, which is LABS\Administrator or LABS\administrator but that doesn't work.
I last tried vcenter about 6 years ago, much earlier version and not on a domain and had a very similar problem - so gave up then. Hoping someone can help with this please?
Every login attempt says "Invalid credentials" and eventually requests the sign in is closed and restarted.
I have an issue where I am getting constant notification of events as below:
Health of Memory changed from red to green. Sensor name: Memory Device 1B 12: Uncorrectable ECC, Current state: Deassert (raw value).
I have switched memory, but socket number stayed the same, so have been in contact with server manufacturer, who have replaced the memory - same event, and replaced the motherboard with a faulty motherboard, so they put the original back in.
However looking at the IDRAC and logs etc, there are no errors showing on the hardware device.
I have tried to reset the sensor in the webclient, but this has not fixed the event.
Help please?
Thank you
Hi everyone,
We recently had to recover the VCenter Appliance from a vmdk, as well as the Platform Services Controller, but whenever I try to stop and start the VPXD service, it comes up with the following error output. Any ideas?
INFO:root:Service: vmware-vpxd, Action: start
Service: vmware-vpxd, Action: start
2018-08-07T18:30:21.431Z Running command: ['/sbin/chkconfig', u'vmware-vpxd']
2018-08-07T18:30:21.507Z Done running command
2018-08-07T18:30:21.507Z Running command: ['/sbin/service', u'vmware-vpxd', 'status']
2018-08-07T18:30:22.126Z Done running command
2018-08-07T18:30:22.126Z Running command: ['/sbin/chkconfig', '--force', u'vmware-vpxd', 'on']
2018-08-07T18:30:22.187Z Done running command
2018-08-07T18:30:22.187Z Running command: ['/sbin/service', u'vmware-vpxd', 'start']
2018-08-07T18:40:35.855Z Done running command
2018-08-07T18:40:35.855Z Invoked command: ['/sbin/service', u'vmware-vpxd', 'start']
2018-08-07T18:40:35.855Z RC = 1
Stdout = vmware-vpxd: VC SSL Certificate does not exist, it will be generated by vpxd
Waiting for the embedded database to start up: success
Executing pre-startup scripts...
vmware-vpxd: Starting vpxd by administrative request.
success
vmware-vpxd: Waiting for vpxd to start listening for requests on 8089
Waiting for vpxd to initialize: ..........................................................Tue Aug 7 18:40:13 UTC 2018 Captured live core: /var/core/live_core.vpxd.16169.08-07-2018-18-40-13
[INFO] writing vpxd process dump retry:2 Time(Y-M-D H:M:S):2018-08-07 18:40:11
.Tue Aug 7 18:40:25 UTC 2018 Captured live core: /var/core/live_core.vpxd.16169.08-07-2018-18-40-25
[INFO] writing vpxd process dump retry:1 Time(Y-M-D H:M:S):2018-08-07 18:40:23
.failed
failed
vmware-vpxd: vpxd failed to initialize in time.
vpxd is already starting up. Aborting the request.
Stderr =
2018-08-07T18:40:35.856Z {
"resolution": null,
"detail": [
{
"args": [
"Command: ['/sbin/service', u'vmware-vpxd', 'start']\nStderr: "
],
"id": "install.ciscommon.command.errinvoke",
"localized": "An error occurred while invoking external command : 'Command: ['/sbin/service', u'vmware-vpxd', 'start']\nStderr: '",
"translatable": "An error occurred while invoking external command : '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
ERROR:root:Unable to start service vmware-vpxd, Exception: {
"resolution": null,
"detail": [
{
"args": [
"vmware-vpxd"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'vmware-vpxd'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Unable to start service vmware-vpxd, Exception: {
"resolution": null,
"detail": [
{
"args": [
"vmware-vpxd"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'vmware-vpxd'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
Hello,
We have a 3 node cluster where the (blade) hosts have Intel Xeon E5-2630 v4 - Broadwell CPUs
We can only now buy blade servers with Skylake processors.
I just wanted to check, we will be able to add a SkyLake host into the existing EVC cluster?
Can anyone confirm that it is ok to do this - I thought not, but the below says that it is compatible?
Thanks for any advice,
Al
root@XXXXX[ ~ ]# service-control --start vmware-sts-idmd
Perform start operation. vmon_profile=None, svc_names=['vmware-sts-idmd'], include_coreossvcs=False, include_leafossvcs=False
2018-08-08T22:46:01.701Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'vmware-sts-idmd']
2018-08-08T22:46:01.718Z Done running command
2018-08-08T22:46:01.726Z Service vmware-sts-idmd does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.
2018-08-08T22:46:01.726Z Running command: ['/sbin/service', u'vmware-sts-idmd', 'status']
2018-08-08T22:46:01.785Z Done running command
2018-08-08T22:46:01.794Z Running command: ['/usr/bin/systemctl', 'daemon-reload']
2018-08-08T22:46:01.956Z Done running command
2018-08-08T22:46:01.956Z Running command: ['/usr/bin/systemctl', 'set-property', u'vmware-sts-idmd.service', 'MemoryAccounting=true', 'CPUAccounting=true', 'BlockIOAccounting=true']
2018-08-08T22:46:01.984Z Done running command
2018-08-08T22:46:03.226Z RC = 1
Stdout =
Stderr = Job for vmware-sts-idmd.service failed because the control process exited with error code. See "systemctl status vmware-sts-idmd.service" and "journalctl -xe" for details.
2018-08-08T22:46:03.226Z {
"resolution": null,
"detail": [
{
"args": [
"Stderr: Job for vmware-sts-idmd.service failed because the control process exited with error code. See \"systemctl status vmware-sts-idmd.service\" and \"journalctl -xe\" for details.\n"
],
"id": "install.ciscommon.command.errinvoke",
"localized": "An error occurred while invoking external command : 'Stderr: Job for vmware-sts-idmd.service failed because the control process exited with error code. See \"systemctl status vmware-sts-idmd.service\" and \"journalctl -xe\" for details.\n'",
"translatable": "An error occurred while invoking external command : '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Error executing start on service vmware-sts-idmd. Details {
"resolution": null,
"detail": [
{
"args": [
"vmware-sts-idmd"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'vmware-sts-idmd'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Service-control failed. Error {
"resolution": null,
"detail": [
{
"args": [
"vmware-sts-idmd"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'vmware-sts-idmd'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
please if you can help me I need to solve this issue since not all the services of the external psc upload
Message was edited by: Jose Franco
After many hours of debugging it looks like we hit a regression bug in 6.5 affecting customers with custom certificates on ESXi hosts. Has anyone else seen this behavior?
Thanks,
Thorsten
The vSphere 6.5 product documentation states replacing ESXi SSL certificates is supported when using RSA keys with key sizes of 2048 bits or
more.
While custom certificates with exactly 2048 bit keys work fine, larger key sizes subtly break the ESXi to vCenter communication. vCenter's vpxd cannot cryptographically verify heartbeat messages from such hosts and repeatedly declares them disconnected.
Adding ESXi 5.5 hosts to VCSA 6.5 does not show this behavior with larger RSAkeys, which qualifies this as a regression bug.
After adding the ESXi with a custom certificate to vCenter, the vCenter intermittently looses connection to the host. Every now and then, the default host connection alarm in vCenter is triggered and cleared within a second.
Besides the symptoms described above, there is a number of log lines in vpxd.log looking suspicious:
error vpxd[7FB5BFF7E700] [Originator@6876 sub=vpxCrypt opID=HeartbeatModuleStart-4b63962d] [bool VpxPublicKey::Verify(const EVP_MD*, const unsigned char*, size_t, const unsigned char*, size_t)] ERR error:04091077:rsa routines:INT_RSA_VERIFY:wrong signature length
warning vpxd[7FB5BFF7E700] [Originator@6876 sub=Heartbeat opID=HeartbeatModuleStart-4b63962d] Failed to verify signature; host: host-42, cert: (**THUMBPRINT_REMOVED**), signature : (**RSA_SIGNATURE_REMOVED**)
# in case of 3072 bit keys
warning vpxd[7FB5BFF7E700] [Originator@6876 sub=Heartbeat opID=HeartbeatModuleStart-4b63962d] Received incorrect size for heartbeat Expected size (334) Received size (462) Host host-87
# in case of 4096 bit keys
warning vpxd[7FB5BFF7E700] [Originator@6876 sub=Heartbeat opID=HeartbeatModuleStart-4b63962d] Received incorrect size for heartbeat Expected size (334) Received size (590) Host host-87
It looks like the latest VPX API leverages digital signatures to verify the integrity and authenticity of ESXi heartbeat messages sent to vCenters. Apparently, there are some hard expectations about the size of these heartbeat messages. They should be exactly 334 bytes long, which is true if a host uses a 2048 bit RSA key to sign the message.
Signing heartbeat messages with 3072 bit keys leads to a message size of 462 bytes, 128 bytes larger than in the 2048 bit case. Moving to 4096 bits grows the signature another 128 bytes. This is interesting, as it is exactly the growth one would expect for PKCS#1 encoded RSA signatures.
I am not sure if the heartbeat package is truncated before it is passed to VpxPublicKey::Verify or if the method makes hard assumptions on the payload size by itself. It's probably the latter and can relatively easily be fixed.
Of course, the heartbeat protocol should be tolerant to heartbeats having different packet sizes as long as RSA digital signatures are used to authenticate the message.
I do not know why VMware chose digital signatures over HMACs in this instance. They should provide all necessary properties with the benefit of fixed size packages and less dependence on the choice of the asymmetric cipher.
I have inherited a vCenter 5.5 server running on Windows 2008R2. My predecessor installed some kind of a script, I either powershell or maybe perl, that allows it to communicate with our support ticketing system, such that a ticket is opened automatically any time there is an alarm on the system. The problem is the script wasn't finished, so we get tickets on *any* change of alarm state, including green and grey alarms which really don't warrant any action. Needless to say our callout people are getting more than a little tired of this thing paging them at all hours of day and night. I have looked through the alarm definitions and there are no actions to run a script attached to any of them, yet it is creating tickets for all of them. I can't even find where the script file lives on the server.
Can anyone suggest how he might have done this, and how I can remove it? It doesn't seem to be polled, it's definitely event-driven. An example of the information it sends follows. Thanks very much.
Metric:
alarm.HealthStatusChangedAlarm - Event: Status change (9943329) Summary:
[FQDN of server] (vCenter) status changed from red to green
Date: 09/08/2018 03:48:55 User name: Health Service Arguments: componentId =
E871136A-6708-4DE3-8E8B-6E4E560A93D2 componentName =
[FQDN of server] (vCenter) newStatus = green oldStatus = red |
NewStatus: Gray | ObjectName: Datacenters | ObjectType: other | OldStatus: Gray
I called a VM ole'windows2012r2 in vCenter 6.7. When taking and removing snapshots, the Recent Tasks pane incorrectly displays the x27 character code.
Even though it displays correctly in the Hosts & Clusters view here:
If anyone from support sees this, is there already an engineering report for this? I know it's small, but kinda silly that parts of the UI render differently and should be an easy fix to correctly display the characters.
I think it's a generic issue encoding the characters, since a " also does something similar:
vCenter is build 8546293
ESXi is build 8941472
From tasks/event I see
From Hosts and clusters tree, I see:
Hello there, we are trying to configure our host profile to remove the esxadmin from config.hostagent.plugins.hostsvc.esxadminsgroup. We can do it to each host using a script command to change the group to something other than the ESXadmins but how can I do that using a host profile? If we have to reboot anything it defaults back to esxadmins, we need this to stop. I know a script changing it back or setting it after the reboot is an option but we need it to NOT be reset. Any thoughts?
I upgraded my VMware environment from 5.5 to 6.0u3 a few weeks ago, but just noticed that I can't get historical data beyond a day on anything (VMs / Hosts etc)...I.E. Performance \ Chart Options if I pick anything further then "Past day" on ANY category I get "Performance data is currently not available for this entity". Where is this controlled and what should it be set to? And same thing regardless of the front end (Web or VI client) I get the same results.
Thanks...
There is an vcenter 6.5 with "vCloud Director-1" extension installed.
It can be deinstalled via MOB: https://vcenter.local/mob/?moid=ExtensionManager&method=unregisterExtension
But after vcenter reboot, this extension is presented again!
How to deinstall it permanently?
Hello
I have two vCenter Servers, Production and Recovery Site, both Windows boxes, apart of same SSO domain, in linked mode and both at the latest build of 5.5. I am trying to upgrade my recovery site first to 6.0U2 using the migration assistant to create an appliance. The upgrade is failing in the pre-upgrade checker with the below errors in the migration-assistant.log:
2016-11-02 13:16:27.406Z| migration-assistant-4191364| E: LaunchUpgradeRunnerCommon: Failed to run pre-upgrade phase: "C:\mig58D2.tmp\PFiles\VMware\CIS\python\python.exe" "C:\mig58D2.tmp\PFiles\VMware\CIS\cis_upgrade_runner\UpgradeRunner.py" --mode=requirements --configFile="C:\Users\MS_VCE~1\AppData\Local\Temp\UpgradeRunnerInput.json" --logDir="C:\Users\MS_VCE~1\AppData\Local\Temp\vcsMigration" --locale=en --outputFile="C:\Users\MS_VCE~1\AppData\Local\Temp\UpgradeRunnerPreupgradeOutput.json"
2016-11-02 13:16:27.406Z| migration-assistant-4191364| I: RemoveDirectoryIfEmpty: Successfully deleted empty directory C:\mig58D2.tmp.
2016-11-02 13:16:27.407Z| migration-assistant-4191364| I: LaunchUpgradeRunnerCommon: Successfully deleted file: C:\Users\MS_VCE~1\AppData\Local\Temp\UpgradeRunnerInput.json
2016-11-02 13:16:27.407Z| migration-assistant-4191364| I: Leaving function: LaunchUpgradeRunnerCommon
2016-11-02 13:16:27.407Z| migration-assistant-4191364| I: ParseExportEstimatesFromPreUpgradeOutput: Component 'upgrade_framework': Export disk req [0 MB], Export time estimate [0 mins] and Import time estimate [0 mins].
Error: Failed to discover a system name that is compatible with both your VMware vCenter Server certificate and your VMware Single Sign-On certificate that can be used to migrate to a VMware vCenter Server Appliance with an embedded Platform Services Controller.
2016-11-02 13:16:27.439Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Resolution: Regenerate your VMware vCenter Server SSL certificate and your VMware Single Sign-On SSL certificate to have a common system name that can be used to migrate your system to VMware vCenter Server Appliance with Platform Services Controller. DHCP IP Address cannot be used as a system name to migrate to a VMware vCenter Server Appliance.
So I have done my due diligence and replaced the certs on the vCenter (Embedded deployment with external/remote SQL DB) but I am still getting the same error. I can confirm the certificates have been regenerated and applied successfully. Also did a complete uninstall and re-install to no avail.
Thoughts?
I'm looking for some clarification on information found in VMware KB 2143565. The instructions state to change the numeric values in the following lines:
log4j.appender.LOGFILE.MaxFileSize
log4j.appender.LOGFILE.MaxBackupIndex
log4j.appender.PERFLOG.MaxBackupIndex
However, these lines are not present in the 'log4j.properties' file on this VCSA, version 6.0.0.30100.
The mount point is 10 GB in size and 100% utilized
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 11G 5.6G 4.6G 56% /
udev 4.0G 164K 4.0G 1% /dev
tmpfs 4.0G 112K 4.0G 1% /dev/shm
/dev/sda1 128M 41M 81M 34% /boot
/dev/mapper/core_vg-core 25G 3.1G 21G 14% /storage/core
/dev/mapper/log_vg-log 9.9G 9.8G 0 100% /storage/log
/dev/mapper/db_vg-db 9.9G 313M 9.1G 4% /storage/db
/dev/mapper/dblog_vg-dblog 5.0G 187M 4.5G 4% /storage/dblog
/dev/mapper/seat_vg-seat 9.9G 513M 8.9G 6% /storage/seat
/dev/mapper/netdump_vg-netdump 1001M 18M 932M 2% /storage/netdump
/dev/mapper/autodeploy_vg-autodeploy 9.9G 165M 9.2G 2% /storage/autodeploy
/dev/mapper/invsvc_vg-invsvc 5.0G 167M 4.6G 4% /storage/invsvc
I have attached a copy of the log4j.properties file along with drive utilization of the /storage/log/vmware directory.
Any assistance or suggestion are greatly appreciated.
Regards,
Hallo,
we just installed a latest 6.5 vCenter on Windows 2012R2 with the latest patches.
Memory 16 GB / 4 Cores in a ESXi 6.0 VM, plenty of HD memory free.
The first few days the server worked very well. Without any changes it begun to get more and more unresponsive.
Finally we can't work anymore with it. After restart it is now not responding anymore. See below ...
After startup is finished the Web Client shows the following message.
The URL: https://192.168.2.10/vsphere-client/?csp
Show the login screen:
After login, the mask (sectioned screen, On the left "Hosts and Clusters" is selected by default.) without content in the white areas, appears. It never fills (waited 30 minutes).
On top a message says:
"Es konnte keine Verbindung zu einem oder mehreren vCenter Server-Systemen hergestellt werden:
https://vCenter.test.com:443/sdk"
When I go to this url I get this message:
Going to Home (Button on top) shows the expected screen.
But "Hosts and Clusters" does not respond.
All other Menues on the left do work.
Memory consumption is 7,5GB of 16GB, no load on CPU (4%).
-------
I triple checked all hosts files and IP addresses.
I checked vsphere_client_virgo.log and found many exceptions.
.....
[2016-11-30T23:56:57.349-08:00] [WARN ] cm-catalog-manager-pool-17
com.vmware.vise.vim.cm.CmCatalogManager
downloadResourceBundle: Download C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\cmCatalog\com.vmware.imagebuilder.imagebuilder.zip
from https://vCenter.test.com:443/sca/resourcebundle/imagebuilderResourceBundle.zip failed, but previous local cache exists and will be used.
Error message is: org.apache.http.conn.HttpHostConnectException: Connect to vCenter.test.com:443 [vCenter.test.com/192.168.2.10, vCenter.test.com/10.1.1.10, vCenter.test.com/0:0:0:0:0:0:0:1]
failed: Connection refused: connect
....
[2016-12-01T06:08:04.549-08:00] [ERROR] CEIPSynchronizerTimer com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl Exception occured while locating TargetVCService. As a result session cannot be simulated, since there is no VC to work with. For more details see the underlying exception: Unexpected status code: 503 com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 503
at com.vmware.vim.vmomi.client.common.Response$Status.getStatus(Response.java:58)
at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:150)
at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:48)
at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226)
at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:110)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:581)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:562)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:344)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:304)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:178)
at com.sun.proxy.$Proxy617.retrieveContent(Unknown Source)
at com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl.initializeVmomi(VcServiceImpl.java:1429)
at com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl.<init>(VcServiceImpl.java:322)
at com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl.createVcService(LinkedVcGroupImpl.java:554)
at com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl.<init>(LinkedVcGroupImpl.java:187)
at com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl.<init>(LinkedVcGroupImpl.java:150)
at com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl.<init>(LinkedVcGroupImpl.java:125)
at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl$VcGroupsRegistryProvider$LinkedVcGroupFactory.create(DsSessionSimulatorImpl.java:627)
at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl$VcGroupsRegistryProvider.getLinkedVcGroupRegistry(DsSessionSimulatorImpl.java:362)
at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl.simulate(DsSessionSimulatorImpl.java:118)
at com.vmware.ph.ceip.impl.Synchronizer$1.run(Synchronizer.java:71)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
[2016-12-01T15:55:03.498+01:00] [WARN ] data-service-pool-136 70000186 100003 200002 c.v.l.client.cis.ls.impl.CacheAuthorizationManagerWrapperImpl Cannot cache licensing admin privilege granted for scope: licensing_service_version1;
AuthorizationException occurred: com.vmware.license.client.cis.ls.AuthorizationException: com.vmware.vim.binding.vmodl.RuntimeFault: Berechtigungen k n nicht berechnet werden. Weitere Details finden Sie im Protokoll.
at com.vmware.license.client.cis.ls.impl.VpxAuthorizationManagerImpl.isLicensingAdminPrivilegeGranted(VpxAuthorizationManagerImpl.java:69)
at com.vmware.license.client.cis.ls.impl.CacheAuthorizationManagerWrapperImpl.isLicensingAdminPrivilegeGranted(CacheAuthorizationManagerWrapperImpl.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at com.sun.proxy.$Proxy360.isLicensingAdminPrivilegeGranted(Unknown Source)
at com.vmware.license.client.cis.impl.LicensingGlobalDataEditorImpl.isLicensingAdminPrivilegeGranted(LicensingGlobalDataEditorImpl.java:90)
at com.vmware.license.client.cis.impl.LicensingGlobalDataEditorImpl.getLicensingGlobalData(LicensingGlobalDataEditorImpl.java:69)
at com.vmware.license.client.cis.adapter.LicensingGlobalDataProviderAdapterImpl.getObjectsByUris(LicensingGlobalDataProviderAdapterImpl.java:67)
at com.vmware.license.client.cis.adapter.LicensingGlobalDataProviderAdapterImpl.getObjectsByUris(LicensingGlobalDataProviderAdapterImpl.java:18)
at com.vmware.license.client.cis.adapter.BaseLicensingObjectsDataProviderAdapterImpl.getObjectsByRefs(BaseLicensingObjectsDataProviderAdapterImpl.java:230)
at com.vmware.license.client.cis.adapter.BaseLicensingObjectsDataProviderAdapterImpl.getObjectsByQuerySpec(BaseLicensingObjectsDataProviderAdapterImpl.java:196)
at com.vmware.license.client.cis.adapter.BaseLicensingObjectsDataProviderAdapterImpl.getResultSet(BaseLicensingObjectsDataProviderAdapterImpl.java:42)
at com.vmware.license.client.cis.adapter.BaseDataProviderAdapterImpl.processQuery(BaseDataProviderAdapterImpl.java:66)
at com.vmware.license.client.cis.adapter.BaseDataProviderAdapterImpl.getData(BaseDataProviderAdapterImpl.java:39)
at com.vmware.vise.data.query.impl.DataAdapterUtil.getDataFromAdapter(DataAdapterUtil.java:218)
at com.vmware.vise.data.query.impl.DataAdapterUtil.getResultFromAdapter(DataAdapterUtil.java:175)
at com.vmware.vise.data.query.impl.DataAdapterUtil.access$000(DataAdapterUtil.java:42)
at com.vmware.vise.data.query.impl.DataAdapterUtil$1.call(DataAdapterUtil.java:81)
at com.vmware.vise.data.query.impl.DataAdapterUtil$1.call(DataAdapterUtil.java:78)
at com.vmware.vise.util.concurrent.ExecutorUtil$2.call(ExecutorUtil.java:654)
at com.vmware.vise.util.concurrent.ExecutorUtil$ThreadContextPropagatingTask.call(ExecutorUtil.java:957)
at com.vmware.vise.data.query.internal.profiling.MdcAwareExecutorService$1.call(MdcAwareExecutorService.java:148)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.vmware.vim.binding.vmodl.RuntimeFault: Berechtigungen k n nicht berechnet werden. Weitere Details finden Sie im Protokoll.
at com.vmware.vise.vim.security.impl.LegacyAuthorizationServiceImpl.throwRuntimeFault(LegacyAuthorizationServiceImpl.java:259)
at com.vmware.vise.vim.security.impl.LegacyAuthorizationServiceImpl.getPrivilegesInternal(LegacyAuthorizationServiceImpl.java:161)
at com.vmware.vise.vim.security.impl.LegacyAuthorizationServiceImpl.getPrivileges(LegacyAuthorizationServiceImpl.java:131)
at com.vmware.vise.vim.security.impl.LegacyAuthorizationServiceImpl.checkPrivileges(LegacyAuthorizationServiceImpl.java:98)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at com.sun.proxy.$Proxy353.checkPrivileges(Unknown Source)
at com.vmware.license.client.cis.ls.impl.VpxAuthorizationManagerImpl.isVpxLicenseAdminPrivilegeGranted(VpxAuthorizationManagerImpl.java:85)
at com.vmware.license.client.cis.ls.impl.VpxAuthorizationManagerImpl.isLicensingAdminPrivilegeGranted(VpxAuthorizationManagerImpl.java:64)
... 34 common frames omitted
Caused by: com.vmware.vim.binding.vmodl.MethodFault: Die Verbindung zu vCenter Server '93e45013-0c89-43ad-9680-152f09f10333' wurde unterbrochen.
at com.vmware.vise.vim.commons.MixedUtil.getMethodFault(MixedUtil.java:98)
at com.vmware.vise.vim.data.adapters.search.impl.PropertyCollectorDataAdapter.getResultSet(PropertyCollectorDataAdapter.java:747)
at com.vmware.vise.vim.data.adapters.search.impl.PropertyCollectorDataAdapter.getResultSet(PropertyCollectorDataAdapter.java:630)
at com.vmware.vise.vim.data.adapters.search.impl.PropertyCollectorDataAdapter.getProperties(PropertyCollectorDataAdapter.java:340)
at com.vmware.vise.data.query.impl.DataManager.getDataFromPropertyProvider(DataManager.java:1301)
at com.vmware.vise.data.query.impl.DataManager.getResultFromPropertyProvider(DataManager.java:1269)
at com.vmware.vise.data.query.impl.DataManager.access$000(DataManager.java:78)
at com.vmware.vise.data.query.impl.DataManager$1.call(DataManager.java:784)
at com.vmware.vise.data.query.impl.DataManager$1.call(DataManager.java:780)
... 7 common frames omitted
Caused by: com.vmware.vise.vim.commons.vcservice.PeerVcConnectionError: Die Verbindung zu vCenter Server '93e45013-0c89-43ad-9680-152f09f10333' wurde unterbrochen.
at com.vmware.vise.vim.data.adapters.search.impl.PropertyCollectorDataAdapter.createPropertyCollectorStub(PropertyCollectorDataAdapter.java:804)
at com.vmware.vise.vim.data.adapters.search.impl.PropertyCollectorDataAdapter.getResultSet(PropertyCollectorDataAdapter.java:688)
... 14 common frames omitted
[2016-12-01T15:55:03.501+01:00] [ERROR] data-service-pool-136 70000186 100003 200002 com.vmware.license.client.cis.impl.LicensingGlobalDataEditorImpl Error when retrieving licensing admin privileges. com.vmware.license.client.cis.ls.AuthorizationException: com.vmware.vim.binding.vmodl.RuntimeFault: Berechtigungen k n nicht berechnet werden. Weitere Details finden Sie im Protokoll.
at com.vmware.license.client.cis.ls.impl.VpxAuthorizationManagerImpl.isLicensingAdminPrivilegeGranted(VpxAuthorizationManagerImpl.java:69)
at com.vmware.license.client.cis.ls.impl.CacheAuthorizationManagerWrapperImpl.isLicensingAdminPrivilegeGranted(CacheAuthorizationManagerWrapperImpl.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at com.sun.proxy.$Proxy360.isLicensingAdminPrivilegeGranted(Unknown Source)
at com.vmware.license.client.cis.impl.LicensingGlobalDataEditorImpl.isLicensingAdminPrivilegeGranted(LicensingGlobalDataEditorImpl.java:90)
at com.vmware.license.client.cis.impl.LicensingGlobalDataEditorImpl.getLicensingGlobalData(LicensingGlobalDataEditorImpl.java:69)
at com.vmware.license.client.cis.adapter.LicensingGlobalDataProviderAdapterImpl.getObjectsByUris(LicensingGlobalDataProviderAdapterImpl.java:67)
at com.vmware.license.client.cis.adapter.LicensingGlobalDataProviderAdapterImpl.getObjectsByUris(LicensingGlobalDataProviderAdapterImpl.java:18)
at com.vmware.license.client.cis.adapter.BaseLicensingObjectsDataProviderAdapterImpl.getObjectsByRefs(BaseLicensingObjectsDataProviderAdapterImpl.java:230)
at com.vmware.license.client.cis.adapter.BaseLicensingObjectsDataProviderAdapterImpl.getObjectsByQuerySpec(BaseLicensingObjectsDataProviderAdapterImpl.java:196)
at com.vmware.license.client.cis.adapter.BaseLicensingObjectsDataProviderAdapterImpl.getResultSet(BaseLicensingObjectsDataProviderAdapterImpl.java:42)
at com.vmware.license.client.cis.adapter.BaseDataProviderAdapterImpl.processQuery(BaseDataProviderAdapterImpl.java:66)
at com.vmware.license.client.cis.adapter.BaseDataProviderAdapterImpl.getData(BaseDataProviderAdapterImpl.java:39)
at com.vmware.vise.data.query.impl.DataAdapterUtil.getDataFromAdapter(DataAdapterUtil.java:218)
at com.vmware.vise.data.query.impl.DataAdapterUtil.getResultFromAdapter(DataAdapterUtil.java:175)
at com.vmware.vise.data.query.impl.DataAdapterUtil.access$000(DataAdapterUtil.java:42)
at com.vmware.vise.data.query.impl.DataAdapterUtil$1.call(DataAdapterUtil.java:81)
at com.vmware.vise.data.query.impl.DataAdapterUtil$1.call(DataAdapterUtil.java:78)
at com.vmware.vise.util.concurrent.ExecutorUtil$2.call(ExecutorUtil.java:654)
at com.vmware.vise.util.concurrent.ExecutorUtil$ThreadContextPropagatingTask.call(ExecutorUtil.java:957)
at com.vmware.vise.data.query.internal.profiling.MdcAwareExecutorService$1.call(MdcAwareExecutorService.java:148)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.vmware.vim.binding.vmodl.RuntimeFault: Berechtigungen k n nicht berechnet werden. Weitere Details finden Sie im Protokoll.
at com.vmware.vise.vim.security.impl.LegacyAuthorizationServiceImpl.throwRuntimeFault(LegacyAuthorizationServiceImpl.java:259)
at com.vmware.vise.vim.security.impl.LegacyAuthorizationServiceImpl.getPrivilegesInternal(LegacyAuthorizationServiceImpl.java:161)
at com.vmware.vise.vim.security.impl.LegacyAuthorizationServiceImpl.getPrivileges(LegacyAuthorizationServiceImpl.java:131)
at com.vmware.vise.vim.security.impl.LegacyAuthorizationServiceImpl.checkPrivileges(LegacyAuthorizationServiceImpl.java:98)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at com.sun.proxy.$Proxy353.checkPrivileges(Unknown Source)
at com.vmware.license.client.cis.ls.impl.VpxAuthorizationManagerImpl.isVpxLicenseAdminPrivilegeGranted(VpxAuthorizationManagerImpl.java:85)
at com.vmware.license.client.cis.ls.impl.VpxAuthorizationManagerImpl.isLicensingAdminPrivilegeGranted(VpxAuthorizationManagerImpl.java:64)
... 34 common frames omitted
Caused by: com.vmware.vim.binding.vmodl.MethodFault: Die Verbindung zu vCenter Server '93e45013-0c89-43ad-9680-152f09f10333' wurde unterbrochen.
at com.vmware.vise.vim.commons.MixedUtil.getMethodFault(MixedUtil.java:98)
at com.vmware.vise.vim.data.adapters.search.impl.PropertyCollectorDataAdapter.getResultSet(PropertyCollectorDataAdapter.java:747)
at com.vmware.vise.vim.data.adapters.search.impl.PropertyCollectorDataAdapter.getResultSet(PropertyCollectorDataAdapter.java:630)
at com.vmware.vise.vim.data.adapters.search.impl.PropertyCollectorDataAdapter.getProperties(PropertyCollectorDataAdapter.java:340)
at com.vmware.vise.data.query.impl.DataManager.getDataFromPropertyProvider(DataManager.java:1301)
at com.vmware.vise.data.query.impl.DataManager.getResultFromPropertyProvider(DataManager.java:1269)
at com.vmware.vise.data.query.impl.DataManager.access$000(DataManager.java:78)
at com.vmware.vise.data.query.impl.DataManager$1.call(DataManager.java:784)
at com.vmware.vise.data.query.impl.DataManager$1.call(DataManager.java:780)
... 7 common frames omitted
Caused by: com.vmware.vise.vim.commons.vcservice.PeerVcConnectionError: Die Verbindung zu vCenter Server '93e45013-0c89-43ad-9680-152f09f10333' wurde unterbrochen.
at com.vmware.vise.vim.data.adapters.search.impl.PropertyCollectorDataAdapter.createPropertyCollectorStub(PropertyCollectorDataAdapter.java:804)
at com.vmware.vise.vim.data.adapters.search.impl.PropertyCollectorDataAdapter.getResultSet(PropertyCollectorDataAdapter.java:688)
... 14 common frames omitted
[2016-12-01T15:55:03.503+01:00] [ERROR] data-service-pool-136 70000186 100003 200002 c.vmware.license.client.cis.adapter.BaseDataProviderAdapterImpl Unable to retrieve licensing data: com.vmware.license.client.cis.management.ManagementException: Bei der Pr g des Global.Licenses-Rechts ist ein Fehler aufgetreten.
at com.vmware.license.client.cis.impl.LicensingGlobalDataEditorImpl.isLicensingAdminPrivilegeGranted(LicensingGlobalDataEditorImpl.java:95)
at com.vmware.license.client.cis.impl.LicensingGlobalDataEditorImpl.getLicensingGlobalData(LicensingGlobalDataEditorImpl.java:69)
at com.vmware.license.client.cis.adapter.LicensingGlobalDataProviderAdapterImpl.getObjectsByUris(LicensingGlobalDataProviderAdapterImpl.java:67)
at com.vmware.license.client.cis.adapter.LicensingGlobalDataProviderAdapterImpl.getObjectsByUris(LicensingGlobalDataProviderAdapterImpl.java:18)
at com.vmware.license.client.cis.adapter.BaseLicensingObjectsDataProviderAdapterImpl.getObjectsByRefs(BaseLicensingObjectsDataProviderAdapterImpl.java:230)
at com.vmware.license.client.cis.adapter.BaseLicensingObjectsDataProviderAdapterImpl.getObjectsByQuerySpec(BaseLicensingObjectsDataProviderAdapterImpl.java:196)
at com.vmware.license.client.cis.adapter.BaseLicensingObjectsDataProviderAdapterImpl.getResultSet(BaseLicensingObjectsDataProviderAdapterImpl.java:42)
at com.vmware.license.client.cis.adapter.BaseDataProviderAdapterImpl.processQuery(BaseDataProviderAdapterImpl.java:66)
at com.vmware.license.client.cis.adapter.BaseDataProviderAdapterImpl.getData(BaseDataProviderAdapterImpl.java:39)
at com.vmware.vise.data.query.impl.DataAdapterUtil.getDataFromAdapter(DataAdapterUtil.java:218)
at com.vmware.vise.data.query.impl.DataAdapterUtil.getResultFromAdapter(DataAdapterUtil.java:175)
at com.vmware.vise.data.query.impl.DataAdapterUtil.access$000(DataAdapterUtil.java:42)
at com.vmware.vise.data.query.impl.DataAdapterUtil$1.call(DataAdapterUtil.java:81)
at com.vmware.vise.data.query.impl.DataAdapterUtil$1.call(DataAdapterUtil.java:78)
at com.vmware.vise.util.concurrent.ExecutorUtil$2.call(ExecutorUtil.java:654)
at com.vmware.vise.util.concurrent.ExecutorUtil$ThreadContextPropagatingTask.call(ExecutorUtil.java:957)
at com.vmware.vise.data.query.internal.profiling.MdcAwareExecutorService$1.call(MdcAwareExecutorService.java:148)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Thank you for your help!
Frank
I keep getting this alert in a vcenter 6.0
I restarted the vapiendpoint service with the service-control command and did not resolve it
any idea?
Hi,
How can I limit specific logging in vsphere server appliance?
For instance i have the default /storage/log 10G partition with almost 1G in /storage/log/vmware/vsphere-client/logs/access/.
Those are uncompressed .txt files dating back from almost a year ago.
Shouldn't there be logrotate and compression in place??
I already followed the KB#2143565 and loosened the sso logs. Is there a similar config for vsphere-client logging?
There are also other massive logs:
# du -h -d1 /storage/log/vmware/
1.2G /storage/log/vmware/sso
15M /storage/log/vmware/vsan-health
31M /storage/log/vmware/vmware-sps
4.0K /storage/log/vmware/netdumper
28K /storage/log/vmware/rbd
3.9M /storage/log/vmware/applmgmt
93M /storage/log/vmware/invsvc
4.0K /storage/log/vmware/vapi-endpoint
69M /storage/log/vmware/vmcad
520M /storage/log/vmware/sca
8.0K /storage/log/vmware/vmafd
698M /storage/log/vmware/vsphere-client
1.3M /storage/log/vmware/rhttpproxy
72M /storage/log/vmware/cm
1008M /storage/log/vmware/vpxd
10M /storage/log/vmware/syslog
11M /storage/log/vmware/vsm
519M /storage/log/vmware/vmafdd
32M /storage/log/vmware/iiad
12K /storage/log/vmware/vws
113M /storage/log/vmware/eam
4.0K /storage/log/vmware/vctop
4.0K /storage/log/vmware/mbcs
60M /storage/log/vmware/vmdird
68K /storage/log/vmware/rsyslogd
29M /storage/log/vmware/vapi
818M /storage/log/vmware/cloudvm
2.0M /storage/log/vmware/psc-client
45M /storage/log/vmware/workflow
1.4G /storage/log/vmware/vdcs
79M /storage/log/vmware/perfcharts
764K /storage/log/vmware/vpostgres
16K /storage/log/vmware/vmdir
110M /storage/log/vmware/cis-license
6.8G /storage/log/vmware/
Thanks.
i migrated vcenter and esxi from 5.5 to 6.5 now . my plan is vmtools, hardware and vmfs . i have a question about migration . now first i must upgrade vmtools then hardware version or the exact opposite ( with snapshot or backup ). and my another question is about vmfs update. i have ms cluster in vcenter infrastructure how i can upgrade this datastore. so i dont know ms cluster virtual hard disk model ? I do not know how the MS cluster was made because I was not the one who built it. I don't know if this infrastructure supports vMotion. I could not understand if I could do without shutdown the ms cluster virtual servers.
Hi,
I have successfully migrated from VC 6.0 for Windows to VCSA 6.5 as I wanted to get freed Windows Server license. All is working correctly except Update Manager. I'm still getting error "VMware vSphere Update Manager had an unknown error. Check the events and log files for details." when I tried to scan for updates. I'm new to VCSA, so please which logs exactly I need to look in? on VCSA ? or ESXi itself?
Thanks
It is great getting 75 people to view the thread but no one is offering any advice, surely this is not just a one time thing.
We are trying to configure our host profile to remove the esxadmin from config.hostagent.plugins.hostsvc.esxadminsgroup. We can do it to each host using a script command to change the group to something other than the ESXadmins but how can I do that using a host profile? If we have to reboot anything it defaults back to esxadmins, we need this to stop. I know a script changing it back or setting it after the reboot is an option but we need it to NOT be reset. Any thoughts?