I'm observing following virgo error while starting virgo server. As a result it is not taking hot deployment.

[2020-05-18T15:13:32.746+05:30] [ERROR]  TCP Connection(2)-127.0.0.1  <DE0002E> Installation of bundle 'com.dell.storage.vcp.dsvcp-ui' version '1.0.0' failed. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.dell.storage.vcp.dsvcp-ui' at version '1.0.0': Cannot resolve: com.dell.storage.vcp.dsvcp-ui

    Resolver report:

        An Import-Package could not be resolved. Resolver error data <Import-Package: com.dell.storage.vcp.mvc; version="1.0.0">. Caused by missing constraint in bundle <com.dell.storage.vcp.dsvcp-ui_1.0.0>

             constraint: <Import-Package: com.dell.storage.vcp.mvc; version="1.0.0">

        An Import-Package could not be resolved. Resolver error data <Import-Package: org.sqlite; version="0.0.0">. Caused by missing constraint in bundle <com.dell.storage.vcp.dsvcp-service_1.0.0>

             constraint: <Import-Package: org.sqlite; version="0.0.0">

at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:46)

at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)

at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:73)

at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)

at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)

at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)

at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:359)

at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:185)

at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:140)

at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:253)

at org.eclipse.virgo.kernel.deployer.management.StandardDeployer.deploy(StandardDeployer.java:52)

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 sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)

at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)

at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193)

at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175)

at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117)

at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54)

at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)

at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)

at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)

at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)

at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)

at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)

at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)

at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)

at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)

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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)

at sun.rmi.transport.Transport$1.run(Transport.java:200)

at sun.rmi.transport.Transport$1.run(Transport.java:197)

at java.security.AccessController.doPrivileged(Native Method)

at sun.rmi.transport.Transport.serviceCall(Transport.java:196)

at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)

at java.security.AccessController.doPrivileged(Native Method)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)

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)

I'm planning to patch both my vCenters from 6.7 U2 to U3g. One VCSA shows 6.7.0.44000 while the other only goes up to 6.7.0.43000.

Yes, I have tried the "Check Updates" button.

My company changed it's name and therefore we have to migrate our Active Directory domain to a new domain.  I am unsure of what I need to do as far as vCenter is concerned.  I am thinking that I need to change the FQDN by following these instructions Changing your vCenter Server's FQDN - VMware vSphere Blog but just wanted to see if anyone out there has gone through a similar migration and has any advice as to what the right approach to this is.

Infos tech

Vcenter Applicance 6.7

PSC embeded

Esxi 6.5 U2

Bonjour à tous,

voilà, je viens sur le forum pour trouver de l'aide au problème que je rencontre. Je viens de mettre à jour mon "Vcenter" avec un certificat Autosigné + Root. Je suis passé par le process du "Certificat Manager" et de l' "ADCS". Jusque là, tout va bien. J'ai bien mis à jour le serveur. Je vérifie le certificat (cadenas sur la page Web) sur le "Vcenter" et sur le "Vmware Appliance Management", tout est OK !

Hi All,

here, I come to the forum to find help with the problem I am having. I just updated my "Vcenter" with a Self-signed + Root certificate. I went through the process of "Certificate Manager" and "ADCS". That's fine. I have successfully updated the server. I check the certificate (padlock on the web page) on the "Vcenter" and on the "Vmware Appliance Management", everything is OK !

Par contre, des que j'ajoute un ESXI à mon "Vcenter", là, il récupère l'ancien certificat Root Vmware (CA)...

On the other hand, I added an ESXI to my "Vcenter", it recovers the old Root Vmware (CA) certificate ...

Au niveau de l'ESXI :

on the ESXI :

J'ai pourtant fait un renouveler certificat et un actualisé du certificat au niveau du "Vcenter", mais rien à faire il garde l'ancien certificat + root Vmware...

J'ai lancé toutes ces commandes afin de localiser le certificat + Root Vmware :

However, I did a certificate renewal and an updated certificate at the "Vcenter" level, but nothing, it keeps the old certificate + root Vmware ...

I launched all these commands in order to locate the + Root Vmware certificate:

J'ai bien retrouvé le "CA Vmware" dans "TRUSTED_ROOTS" que j'ai sauvegardé, dépublié et enfin supprimé avec les commandes suivantes :

I found the "CA Vmware" in "TRUSTED_ROOTS" which I saved, unpublished and finally deleted with the following commands:

Relancer tous les services du "Vcenter/PSC", rebooter même (le Vcenter, l'ESXI)... Mais rien n'y fait, l' "ESXI" récupère toujours le certificat "CA Vmware"...

Relaunch all the services on the "Vcenter / PSC", then reboot (the Vcenter, the ESXI) ... But nothing !!! the "ESXI" always retrieves the "CA Vmware" certificate ...

Que faire d'autre, svp ???

What can i do please ??

Merci à vous pour votre aide précieuse..

Thanks a lot for your help...

Akeena64

I have VCSA 6.5 and try to upgrade it to 6.7U2

During migration prerequsites check phase I have error "Unable to enumerate and validate the root certificates from the TRUSTED_ROOTS VECS store. Make sure that the vmafd service is reachable and started before continuing."

I have check cert store on new VCSA installation by:

service-control --status certificatemanagement

The service is running

Then I check cert store by "vecs-cli store list" and get "Unable to connect to vmafd service"

Then I check syslog and found

Error opening Certificate /etc/vmware/vmware-vmafd/machine-ssl.crt

140367761127064:error:02001002:system library:fopen:No such file or directory:bss_file.c:406:fopen('/etc/vmware/vmware-vmafd/machine-ssl.crt','r')

140367761127064:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:408:

unable to load certificate

Mon, 29 Apr 2019 09:44:24 +0000 [ERROR] CA file /etc/ssl/certs/.0 not found

How I can generate machine-ssl.crt ?

PS I cannot use certificate-manager as I cannot authenticate as administrator@vsphere.local at this point of time.

UPD: I have copied /etc/vmware/vmware-vmafd/* from old VCSA but without success. "vecs-cli store list" still cannot connect to vmafd service

Сообщение отредактировано: a_sand

Hi, first sorry for my bad English.

I have a vCenter version 6.0.0 with two ESXi version 6.0.0 with enterprise plus license here in my company.

It turns out that for some time now a failure started (error 503) when trying to open vCenter through the vSphere Client and I was also unable to access the "http://vCenter:5480".

Researching here in the community I saw that the failure could be caused by a full partition in the vCenter Server Appliance. Through some commands I was able to find and clear some log files that were occupying the entire space of at least two partitions.

My access to vCenter: 5480 is back to normal but I still have no access to vCenter.

Through some more research I found that several Vcenter services are not running. I tried to force the services to start, but I got an error and also restarted the aplliance virtual machine a few times but without success.

Questions:

I think that an update in vCenter to the latest version available and compatible with my license (6.7) could solve the problem. What do you think? Could it affect my virtual machines (approximately 25 VMs) installed on the hosts?

I have the license applied to my vCenter but I don't have it noted. Who installed it was another person who is no longer in the company. I need to get this license somehow. Do you have a command that can get that license number through a command via telnet?

Thank you,

Wendel

So i have build playground with 7.0 versions before actually moving prod to new version. Yesterday i encountered weird thing.

1. web client notification popped up , that there is new update for vCenter (thats really nice thing!)

2. since from default repos for vCenter nothing is being picked up i downloaded iso manually and patched appliance that way.

3. appliance patched without any issues and shows build version - 7.0.0.10300 build 16189094

4. web client still keep popping alert that patch is available and showing that build version is 16189207

what confuses hell out of me why the patched version 7.0.0.10300 (16189094) shows build number lesser than unpatched version 7.0.0.10100 (16189207)

p.s. initially it was installed from iso available in VMUG Adv repo (VMware-VCSA-all-7.0.0-15952498)

suggestions , how to fix that versioning missmatch ?

M.

Good Morning Gents,

I am experiencing an interest issue, Today I have updated VCA server to version 6.7.0.4300 without any problem. Before the process I was able to web browse to vca and login with my domain account. After successfully completed the process I was trying to login in back but now I am getting "Invalid Credentials", I have tried prefixing my domain account with the domain\Username and same problem. I am able to login using administrator@vsphere.local account. I have asked a collegue to try with his account and he is experiencing the same issue.

Any Ideas?

Thanks in advance

I completed upgrading our vCenter Server appliance to 6.7U3.  After running into a number of issues doing that, I've finally got everything back normal.  The goal was to add new host hardware we have, which we installed ESXi 6.7 on.  Since we were running VCSA 6.5, I upgraded that to be able to create a new cluster for the new hosts to be managed by the 6.7 VCSA.

I created the new cluster, enabled DRS, enabled HA, then enabled and set EVC to the highest on the list (Intel Merom).  We're using hosts with Intel Xeon Gold 6143 CPUs.  I followed the wizard for adding new hosts, it seemed to connect and identify them with no issues, but when I start the adding by clicking finish, it fails immediately with the following error message:

A general system error occurred: Unable to push CA certificates and CRLs to host <hostname/IP>

I've tried using both the FQDN and IP, but get the same error.  We have not fully licensed these installations yet and they have whatever the default certificate is when you first install ESXi, which we did a few weeks ago.  The vCenter server is using a valid certificate issued by our enterprise CA.  What am I missing?

Fresh vCenter Server build with Windows 2016

Installing the latest vCenter Server build and receive an error event code 1603 could not completed installation, rolling back install.

Any ideas

Hello All!

I have a problem.I get the followingmessage:

Target: Datacenters

Stateless event alarm

 

Alarm Definition:

([Event alarm expression: Status change])

 

Event details:

vapi-endpoint status changed from green to yellow

The status changes from green to yellow, and then back again, this takes place several times a day.

I read it, but did not find the answer

VMware Validated Design for Software-Defined Data Center 3.0

That's what I see in the

/var/log/vmware/vapi/endpoint/endpoint.log

2016-10-11T17:18:56.052+03:00 | WARN | state-manager1 | ApiInterfacesFactory | Retrieving interfaces for service f7fb8c35-4220-4ba8-ad0b-7639dd20cdf4\com.vmware.cis.ds has failed.

com.vmware.vapi.internal.core.abort.RequestAbortedException: Http request aborted.

at com.vmware.vapi.internal.protocol.common.Util$1.onAbort(Util.java:68)

        at com.vmware.vapi.internal.core.abort.AbortHandleImpl.abort(AbortHandleImpl.java:39)

        at com.vmware.vapi.endpoint.api.TimedApiProvider$1.run(TimedApiProvider.java:58)

        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

        at java.util.concurrent.FutureTask.run(Unknown Source)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

        at java.lang.Thread.run(Unknown Source)

I tried to restart the vmware-vapi-endpoint, but it does not help

I use vCenter Server Appliance 6.0.0  Build 3634794.

Please help solve the problem.

Hello,

I have upgraded vCenter from GA to 7.0.0.10300 (build 16189094). vCenter Management summary tab tells:

- Version: 7.0.0.10300

- Build number: 16189094

VCSA has been rebooted as well (even though upgrade did not ask for that).

When I log into vCenter i get the message: New vCenter server updates are available -> View Updates

In vCenter itself it tells me about version 7.0.0 (Updates Available), build 16189207.

Does anybody have this issue as well? Any idea how to fix it?

Thanks,

Robert

As stated in the 7.0.0a release notes - upgrading from 6.7 3g is not supported.

Whats should I do as my 6.7 VC's are all at 6.7 3g - wait I guess ? or has anyone tried an upgrade to 7.0.0a and it works ? It just isnt a supported upgrade ?

Extract from release notes below :-

IMPORTANT: Upgrade from vCenter Server 6.7 Update 3g to vCenter Server 7.0.0a is not supported. For more information on vCenter Server versions that support upgrade to vCenter Server 7.0.0a, see VMware knowledge base article 67077.

VMware vCenter Server 7.0.0a Release Notes

I've just upgraded vcenter to 6.5 U1 Photon appliance from a physical windows version 5.5, after day long run of migration assistant that seemed have succeeded at first. But now I cannot use HA in my hosts, they are in bad state and cannot migrate, nor boot machines, they have been up and running during the migration and they are still in this state.

My hosts are not showing the physical adapters in the VDS, BUT they are working, they only have VDS, the VMs on them are tagged to the right vlans, but I don't see the hosts vmkernels either, I can ping them, but since vcenter cannot recognize the physical adapters for some reason, it doesn't show them under the port group nor the VDS it's supposed to have the vmkernel on

If I shut down the VMs, I cannot boot them back up because the host's state. And I cannot even migrate them to other hosts.

the hosts are HP ProLiant DL385p Gen8, these are quad pci cards and onboard interfaces (HP Ethernet 1Gb 4-port 331FLR Adapter - HP NC365T 4-port Ethernet Server Adapter).

The hosts were and still are 5.5.0 9919047, they were running HPE version, installed long time ago. It's vcenter that cannot read the right info.

And the new Photon appliance, is running on one of them.

What's next?

I have a previously working vcenter appliance 6.5 that was in a bad state after an unclean shutdown from a thunderstorm. Initially it was not fully booting, but I ran fsck on the volumes that needed it, and it gets all the way to the running info screen. After that vpxd fails to fully start. I can't find any more volumes that are in a bad state, but it appears that I might have some SQL corruption. Note the SQL error below.

Error message when trying to open web client is: 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x00007faab404a230] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)

Output of service-control --status --all

Running:

applmgmt lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-pod vmware-postgres-archiver vmware-rbd-watchdog vmware-rhttpproxy vmware-sca vmware-sps vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-updatemgr vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui

Stopped:

vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-vcha vmware-vpxd vsan-dps

Grep of all lines with error in them from vpxd log file:

2020-05-23T15:13:12.693Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Unable to read from '/etc/motd':N7Vmacore23FileIONotFoundExceptionE(Could not find file  : /etc/motd)

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: AgentUpgrade.autoUpgradeAgents

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: AgentUpgrade.checkPeriodSeconds

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: alarms.upgraded

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Stats.Purge1

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Stats.Purge2

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Stats.Purge3

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Stats.Rollup1

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Stats.Rollup2

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Stats.Rollup3

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Topn.Calc1

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Topn.Calc2

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Topn.Calc3

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Topn.Calc4

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Topn.Purge1

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Topn.Purge2

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Topn.Purge3

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: DBProc.Log.Level.Topn.Purge4

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: TOPN_LOG_BUFFER

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: TOPN_LOGING_MODE

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: TOPN_STATS_DELAY_MINS_1

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: TOPN_STATS_DELAY_MINS_2

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: TOPN_STATS_DELAY_MINS_3

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: TOPN_STATS_DELAY_MINS_4

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: VirtualCenter.CacheSize

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: VirtualCenter.LDAPAdminPrincipal

2020-05-23T15:13:12.700Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Ignoring unknown entry from DB: VirtualCenter.VimWebServicesUrl

2020-05-23T15:13:12.704Z error vpxd[04354] [Originator@6876 sub=MoOptionMgr] Skipping bad entry config.vpxd.enableDebugBrowse from DB. Resetting to default.Exception: Fault cause: vmodl.fault.InvalidArgument

2020-05-23T15:13:15.388Z error vpxd[04354] [Originator@6876 sub=Vsan] Data type vim.cluster.VsanClusterHclInfo already exists.

2020-05-23T15:13:15.388Z error vpxd[04354] [Originator@6876 sub=Vsan] Managed type vim.cluster.VsanClusterHealthSystem already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Data type vim.host.VsanHclControllerInfo already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Managed type vim.host.VsanHealthSystem already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Data type vim.host.VsanHostHclInfo already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Managed type vim.host.VsanDiskManagementSystem already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Data type vim.vsan.host.DiskMapInfoEx already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Data type vim.vsan.host.VsanDiskManagementSystemCapability already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Data type vim.host.VSANCmmdsFaultDomainInfo already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Data type vim.host.VSANCmmdsNodeInfo already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Data type vim.host.VSANCmmdsPreferredFaultDomainInfo already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Data type vim.host.VSANStretchedClusterHostCapability already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Data type vim.host.VSANStretchedClusterHostInfo already exists.

2020-05-23T15:13:15.389Z error vpxd[04354] [Originator@6876 sub=Vsan] Managed type vim.host.VsanStretchedClusterSystem already exists.

2020-05-23T15:13:19.242Z error vpxd[04354] [Originator@6876 sub=profileUtil] [DeserializeFromFile] reading failed: Could not find file  : /var/lib/vmware/hpMetadataCache.xml

2020-05-23T15:13:22.233Z error vpxd[04569] [Originator@6876 sub=Main opID=CheckCertificateExpiry-35702e2f] Unable to get certificate count for APPLMGMT_PASSWORD from VECS localhost, error: 0

2020-05-23T15:13:23.413Z error vpxd[04435] [Originator@6876 sub=vmomi.soapStub[12]] initial service state request failed, disabling pings. error=HTTP Status:400 'Bad Request'

2020-05-23T15:13:23.729Z error vpxd[04354] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for user "VSPHERE.LOCAL\Administrator"

2020-05-23T15:13:23.729Z error vpxd[04354] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for group "CAROLINA\Domain Admins"

2020-05-23T15:13:24.280Z error vpxd[04354] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for user "VSPHERE.LOCAL\Administrator"

2020-05-23T15:13:24.280Z error vpxd[04354] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for group "VSPHERE.LOCAL\Administrators"

2020-05-23T15:13:24.280Z error vpxd[04354] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for user "VSPHERE.LOCAL\vsphere-webclient-80cfe84e-9df1-47e4-93e3-d2dfc3e72d72"

2020-05-23T15:13:24.280Z error vpxd[04354] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for user "VSPHERE.LOCAL\vpxd-80cfe84e-9df1-47e4-93e3-d2dfc3e72d72"

2020-05-23T15:13:24.280Z error vpxd[04354] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for user "VSPHERE.LOCAL\vpxd-extension-80cfe84e-9df1-47e4-93e3-d2dfc3e72d72"

2020-05-23T15:13:24.346Z error vpxd[04668] [Originator@6876 sub=vmomi.soapStub[13]] initial service state request failed, disabling pings. error=HTTP Status:400 'Bad Request'

2020-05-23T15:13:25.152Z error vpxd[04354] [Originator@6876 sub=OsLayer_linux] [VpxOsLayer] Failed to write to config: Permission denied for file  : /etc/vmware-vpx/vpxd.cfg.tmp

2020-05-23T15:14:05.925Z error vpxd[04454] [Originator@6876 sub=[SSO] opID=26e74229] [UserDirectorySso] GetUserInfo exception: N7Vmacore9Authorize25AuthUserNotFoundExceptionE(User localos\com.vmware.vim.eam)

2020-05-23T15:14:05.927Z error vpxd[04454] [Originator@6876 sub=[SSO] opID=26e74229] [UserDirectorySso] NormalizeUserName(com.vmware.vim.eam, false) exception: N7Vmacore9Authorize25AuthUserNotFoundExceptionE(User localos\com.vmware.vim.eam)

2020-05-23T15:14:10.713Z error vpxd[04429] [Originator@6876 sub=HttpSvc.HTTPService] Failed to read request; stream: <io_obj p:0x00007f4f5039b388, h:-1, <UNIX '/var/run/vmware/vpxd-webserver-pipe'>, <UNIX ''> FD Closed>, error: N7Vmacore16TimeoutExceptionE(Operation timed out: Stream: <io_obj p:0x00007f4f5039b388, h:-1, <UNIX '/var/run/vmware/vpxd-webserver-pipe'>, <UNIX ''> FD Closed>, duration: 00:00:45.250489 (hh:mm:ss.us))

2020-05-23T15:16:17.602Z error vpxd[04458] [Originator@6876 sub=MoEnvBrowser opID=75353f56] Can not find option descriptor for key vmx-14

2020-05-23T15:20:00.010Z error vpxd[04467] [Originator@6876 sub=Default] [VdbStatement] Execute result code: -1

2020-05-23T15:20:00.010Z error vpxd[04467] [Originator@6876 sub=Default] [VdbStatement] SQL execution failed:  select rule_topn1_proc()

2020-05-23T15:20:00.010Z error vpxd[04467] [Originator@6876 sub=Default] [VdbStatement] Execution elapsed time: 11 ms

2020-05-23T15:20:00.010Z error vpxd[04467] [Originator@6876 sub=Default] [VdbStatement] Statement diagnostic data from driver is XX001:0:1:ERROR: could not read block 2389 in file "base/16395/32425": read only 0 of 8192 bytes;

2020-05-23T15:20:00.010Z error vpxd[04467] [Originator@6876 sub=Default] [VdbStatement] Connection diagnostic data from driver is XX001:0:110:ERROR: could not read block 2389 in file "base/16395/32425": read only 0 of 8192 bytes

2020-05-23T15:20:00.010Z error vpxd[04467] [Originator@6876 sub=Default] [VdbStatement] Bind parameters:

2020-05-23T15:20:00.010Z error vpxd[04467] [Originator@6876 sub=Default] [Vdb::IsRecoverableErrorCode] Unable to recover from XX001:1

2020-05-23T15:20:00.010Z error vpxd[04467] [Originator@6876 sub=Default] [Vdb::IsRecoverableErrorCode] Unable to recover from XX001:110

2020-05-23T15:20:00.010Z error vpxd[04467] [Originator@6876 sub=Default] [VdbStatement] SQLError was thrown: "ODBC error: (XX001) - ERROR: could not read block 2389 in file "base/16395/32425": read only 0 of 8192 bytes;

After every restart i need to enter the management ip manually for my vcenter vm .

Status of the services

root@bnps-vcsa [ ~ ]# service-control --status

Stopped:

lwsmd pschealth vmafdd vmcad vmcam vmdird vmdnsd vmonapi vmware-analytics vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-pod vmware-postgres-archiver vmware-rbd-watchdog vmware-rhttpproxy vmware-sca vmware-sps vmware-sts-idmd vmware-stsd vmware-updatemgr vmware-vapi-endpoint vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsan-dps vsphere-client vsphere-ui

Running:

applmgmt vmware-statsmonitor vmware-vcha vmware-vmon

Error starting the Vsphere UI

root@bnps-vcsa [ ~ ]# service-control --start vsphere-ui

Operation not cancellable. Please wait for it to finish...

Performing start operation on service vsphere-ui...

Error executing start on service vsphere-ui. Details {

    "resolution": null,

    "problemId": null,

    "detail": [

        {

            "translatable": "An error occurred while starting service '%(0)s'",

            "localized": "An error occurred while starting service 'vsphere-ui'",

            "args": [

                "vsphere-ui"

            ],

            "id": "install.ciscommon.service.failstart"

        }

    ],

    "componentKey": null

}

Service-control failed. Error: {

    "resolution": null,

    "problemId": null,

    "detail": [

        {

            "translatable": "An error occurred while starting service '%(0)s'",

            "localized": "An error occurred while starting service 'vsphere-ui'",

            "args": [

                "vsphere-ui"

            ],

            "id": "install.ciscommon.service.failstart"

        }

    ],

    "componentKey": null

}

I tried the vmon Cli utility also

root@bnps-vcsa [ /usr/lib/vmware-vmon ]# ./vmon-cli -h

Usage: ./vmon-cli [options]

Options:

  -c, --vmonserver <file>  vMon server connection path.

  -i, --start <serviceid>  Start service.

  -k, --stop <serviceid>   Stop Service.

  -r, --restart <serviceid> Restart Service.

  -s, --status <serviceid> Get Service status.

  -d, --dumpcore <serviceid> Dump service process core.

  -U, --update <serviceid> Update service state.

  -S  --starttype <MANUAL|AUTOMATIC|DISABLED> Requires -U option.

  -R  --runasuser <Username> Requires -U option.

  -l, --list               List registered services.

  --list-dependencies <serviceid> List service dependencies.

  --batchstart <profile> Start all services in profile.

  --batchstop  <profile> Stop all services in profile.

  --refreshhealth          Refreshes health state of all services.

  --ignorefail             Ignore batch operation failures.

  --dumpstat             Dump stat info without reboot.

  -h                       Print help information.

root@bnps-vcsa [ /usr/lib/vmware-vmon ]# ./vmon-cli -r vpxd

Restart service request failed. Error: A system error occurred. Check logs for details

root@bnps-vcsa [ /usr/lib/vmware-vmon ]# ./vmon-cli -s vpxd

Name: vpxd

Starttype: AUTOMATIC

RunState: STOPPED

RunAsUser: root

CurrentRunStateDuration(ms): 10111657

HealthState: UNHEALTHY

FailStop: TRUE

MainProcessId: N/A

root@bnps-vcsa [ /usr/lib/vmware-vmon ]# df -h

Filesystem                                                      Size  Used Avail Use% Mounted on

devtmpfs                                                         7.9G     0  7.9G   0% /dev

tmpfs                                                               7.9G     0  7.9G   0% /dev/shm

tmpfs                                                               7.9G  664K  7.9G   1% /run

tmpfs                                                                7.9G     0  7.9G   0% /sys/fs/cgroup

/dev/sda3                                                         11G  6.3G  3.9G  62% /

tmpfs                                                                7.9G  144K  7.9G   1% /tmp

/dev/mapper/netdump_vg-netdump                 985M  1.3M  916M   1% /storage/netdump

/dev/mapper/imagebuilder_vg-imagebuilder    9.8G   23M  9.2G   1% /storage/imagebuilder

/dev/mapper/autodeploy_vg-autodeploy          9.8G   23M  9.2G   1% /storage/autodeploy

/dev/mapper/core_vg-core                               50G  3.6G   44G   8% /storage/core

/dev/mapper/updatemgr_vg-updatemgr         99G  102M   94G   1% /storage/updatemgr

/dev/mapper/seat_vg-seat                              25G  374M   23G   2% /storage/seat

/dev/mapper/dblog_vg-dblog                           15G  262M   14G   2% /storage/dblog

/dev/mapper/archive_vg-archive                      50G  1.4G   46G   3% /storage/archive

/dev/mapper/log_vg-log                                    9.8G  1.7G  7.6G  18% /storage/log

/dev/sda1                                                          120M   31M   81M  28% /boot

/dev/mapper/db_vg-db                                      9.8G  195M  9.1G   3% /storage/db

VPXD Log

root@bnps-vcsa [ /var/log/vmware/vpxd ]# vi vpxd.log

2020-05-24T15:58:50.634+08:00 Section for VMware VirtualCenter, pid=14083, version=6.7.0, build=10244857, option=Release

2020-05-24T15:58:50.634+08:00 info vpxd[51812] [Originator@6876 sub=vpxLro opID=vb-64555:auto-name-37131:01-0] [VpxLRO] -- BEGIN lro-1333550 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:50.635+08:00 info vpxd[51812] [Originator@6876 sub=vpxLro opID=vb-64555:auto-name-37131:01-0] [VpxLRO] -- FINISH lro-1333550

2020-05-24T15:58:50.639+08:00 info vpxd[14168] [Originator@6876 sub=vpxLro opID=vb-64556:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-78] [VpxLRO] -- BEGIN lro-1333551 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:50.639+08:00 info vpxd[14168] [Originator@6876 sub=vpxLro opID=vb-64556:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-78] [VpxLRO] -- FINISH lro-1333551

2020-05-24T15:58:50.849+08:00 info vpxd[14221] [Originator@6876 sub=vpxLro opID=vb-64559:auto-name-37133:01-b] [VpxLRO] -- BEGIN lro-1333554 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:50.849+08:00 info vpxd[14221] [Originator@6876 sub=vpxLro opID=vb-64559:auto-name-37133:01-b] [VpxLRO] -- FINISH lro-1333554

2020-05-24T15:58:50.853+08:00 info vpxd[14122] [Originator@6876 sub=vpxLro opID=vb-64560:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-0] [VpxLRO] -- BEGIN lro-1333555 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:50.853+08:00 info vpxd[14122] [Originator@6876 sub=vpxLro opID=vb-64560:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-0] [VpxLRO] -- FINISH lro-1333555

2020-05-24T15:58:51.064+08:00 info vpxd[14214] [Originator@6876 sub=vpxLro opID=vb-64563:auto-name-37135:01-8b] [VpxLRO] -- BEGIN lro-1333557 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:51.064+08:00 info vpxd[14214] [Originator@6876 sub=vpxLro opID=vb-64563:auto-name-37135:01-8b] [VpxLRO] -- FINISH lro-1333557

2020-05-24T15:58:51.068+08:00 info vpxd[14216] [Originator@6876 sub=vpxLro opID=vb-64564:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-0] [VpxLRO] -- BEGIN lro-1333558 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:51.068+08:00 info vpxd[14216] [Originator@6876 sub=vpxLro opID=vb-64564:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-0] [VpxLRO] -- FINISH lro-1333558

2020-05-24T15:58:51.277+08:00 info vpxd[51826] [Originator@6876 sub=vpxLro opID=vb-64567:auto-name-37137:01-f6] [VpxLRO] -- BEGIN lro-1333560 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:51.277+08:00 info vpxd[51826] [Originator@6876 sub=vpxLro opID=vb-64567:auto-name-37137:01-f6] [VpxLRO] -- FINISH lro-1333560

2020-05-24T15:58:51.280+08:00 info vpxd[14310] [Originator@6876 sub=vpxLro opID=vb-64568:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-7b] [VpxLRO] -- BEGIN lro-1333561 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:51.281+08:00 info vpxd[14310] [Originator@6876 sub=vpxLro opID=vb-64568:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-7b] [VpxLRO] -- FINISH lro-1333561

2020-05-24T15:58:51.492+08:00 info vpxd[14148] [Originator@6876 sub=vpxLro opID=vb-64571:auto-name-37139:01-a2] [VpxLRO] -- BEGIN lro-1333563 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:51.493+08:00 info vpxd[14148] [Originator@6876 sub=vpxLro opID=vb-64571:auto-name-37139:01-a2] [VpxLRO] -- FINISH lro-1333563

2020-05-24T15:58:51.497+08:00 info vpxd[14204] [Originator@6876 sub=vpxLro opID=vb-64572:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-21] [VpxLRO] -- BEGIN lro-1333564 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:51.498+08:00 info vpxd[14204] [Originator@6876 sub=vpxLro opID=vb-64572:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-21] [VpxLRO] -- FINISH lro-1333564

2020-05-24T15:58:51.704+08:00 info vpxd[14478] [Originator@6876 sub=vpxLro opID=vb-64575:auto-name-37141:01-99] [VpxLRO] -- BEGIN lro-1333566 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

2020-05-24T15:58:51.704+08:00 info vpxd[14478] [Originator@6876 sub=vpxLro opID=vb-64575:auto-name-37141:01-99] [VpxLRO] -- FINISH lro-1333566

2020-05-24T15:58:51.707+08:00 info vpxd[14166] [Originator@6876 sub=vpxLro opID=vb-64576:urn:vmomi:VirtualMachine:vm-2536:630367e1-a9b8-4f9b-972a-859f5ac994f6.properties:01-1b] [VpxLRO] -- BEGIN lro-1333567 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 529b2558-c996-48ab-e86e-ec94f894efd5(52503d8a-bf79-5bde-4f8f-2780c3483e3e)

@

"vpxd.log" [noeol] 15152L, 3413762C    

Help me guys how to fix my VCSA.

Hi,

Is it possible to block specific port in vcenter appliance 6.7 . I need to block incoming port 5432 .

Thanks,

Hello everyone,

I have issue that my root account has expired. I'd tried to change password but there was no effect. I can login ssh and console. But I cannot patch and upgrade my vcsa. Are there any suggestions?

I've tried:

- pam_tally2 -r -u root

- passwd root

- I've made password "never expired" in /etc/shadow

But all this took no effect.

vcsa version:

I had to reboot this server for a maintenance.  since then the services are not coming up.  Is it because of /storage/archive being 100% full ?

root@XXXXXXX [ ~ ]# service-control --status

Running:

lwsmd vmafdd vmcad vmdird vmdnsd vmware-analytics vmware-certificatemanagement vmware-cis-license vmware-eam vmware-pod vmware-postgres-archiver vmware-rhttpproxy vmware-sca vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd-svcs vsphere-client vsphere-ui

Stopped:

applmgmt pschealth vmcam vmonapi vmware-cm vmware-content-library vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-rbd-watchdog vmware-sps vmware-topologysvc vmware-updatemgr vmware-vcha vmware-vpxd vmware-vsan-health vmware-vsm vsan-dps

2020-03-09T14:51:41.420Z Done running command

2020-03-09T14:51:41.421Z Successfully started service vmware-vmon

2020-03-09T14:51:41.421Z Running command: ['/usr/bin/systemctl', 'unset-environment', 'VMON_PROFILE']

2020-03-09T14:51:41.430Z Done running command

Successfully started service vmware-vmon

2020-03-09T14:51:41.431Z Running command: ['/usr/lib/vmware-vmon/vmon-cli', '--batchstart', 'ALL']

2020-03-09T14:58:49.248Z Done running command

Service-control failed. Error: Failed to start services in profile ALL. RC=1, stderr=Failed to start topologysvc, vmonapi, applmgmt, cm services. Error: Operation timed out

2020-05-15T05:13:14.486-04:00 | ERROR | state-manager1 | DefaultStateManager | Could not initialize endpoint runtime state.

com.vmware.vapi.endpoint.config.ConfigurationException: Failed to retrieve SSO settings.

        at com.vmware.vapi.endpoint.cis.SsoSettingsBuilder.buildInitial(SsoSettingsBuilder.java:48)

        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: com.vmware.vapi.endpoint.config.ConfigurationException: com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 503

        at com.vmware.vapi.endpoint.cis.ls.LookupServiceClientWrapper.lookup(LookupServiceClientWrapper.java:292)

        at com.vmware.vapi.endpoint.cis.ls.LookupServiceClientWrapper.lookupSso(LookupServiceClientWrapper.java:206)

        at com.vmware.vapi.endpoint.cis.SsoSettingsBuilder.ssoSettings(SsoSettingsBuilder.java:107)

        at com.vmware.vapi.endpoint.cis.SsoSettingsBuilder.buildInitial(SsoSettingsBuilder.java:41)

        ... 10 more

Caused by: 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:156)

        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:53)

        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:106)

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:629)

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:610)

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:360)

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:311)

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:184)

        at com.sun.proxy.$Proxy38.list(Unknown Source)

        at com.vmware.vapi.endpoint.cis.ls.LookupServiceClientWrapper.lookup(LookupServiceClientWrapper.java:288)

        ... 13 more

# df -h

Filesystem                                Size  Used Avail Use% Mounted on

devtmpfs                                  9.8G     0  9.8G   0% /dev

tmpfs                                     9.8G  864K  9.8G   1% /dev/shm

tmpfs                                     9.8G  684K  9.8G   1% /run

tmpfs                                     9.8G     0  9.8G   0% /sys/fs/cgroup

/dev/sda3                                  11G  6.1G  4.0G  61% /

tmpfs                                     9.8G  912K  9.8G   1% /tmp

/dev/mapper/dblog_vg-dblog                 15G  470M   14G   4% /storage/dblog

/dev/mapper/core_vg-core                   50G  831M   46G   2% /storage/core

/dev/mapper/db_vg-db                      9.8G  324M  8.9G   4% /storage/db

/dev/sda1                                 120M   34M   78M  31% /boot

/dev/mapper/netdump_vg-netdump            985M  1.3M  916M   1% /storage/netdump

/dev/mapper/log_vg-log                    9.8G  6.6G  2.7G  71% /storage/log

/dev/mapper/autodeploy_vg-autodeploy      9.8G   23M  9.2G   1% /storage/autodeploy

/dev/mapper/imagebuilder_vg-imagebuilder  9.8G   23M  9.2G   1% /storage/imagebuilder

/dev/mapper/archive_vg-archive             50G   47G   20M 100% /storage/archive

/dev/mapper/updatemgr_vg-updatemgr         99G   64M   94G   1% /storage/updatemgr

/dev/mapper/seat_vg-seat                   25G  1.1G   23G   5% /storage/seat