Hi,

We are looking for a HP Health Provider to use with Proactive HA in vSphere 6.5, but we are not able to find out.

Does anyone know if HP has developed a Health Provider?

thanks

Hi,

We currently have 2 identical hardware ESXI 6.0 hosts connected to Vcenter 6.0.

One esxi 6.0 host has an additional VLAN for Voice and is in a disconnected state on Vcenter. I can ping the default VLAN IP and DNS name from every device on the network except from the Vcenter server. From the Vcenter server I can not  ping the default  VLAN by IP or DNS name, but can ping the Voice VLAN.

There are 2 vswitches and Vswitch0 has the only Vkernal for Management Network and the Vlan is set to 0

Any ideas would be appreciated

Hi Guys,

I wanted to understand if its possible to deploy VCSA in HA deployment across 3 different sites using different IP Subnets, but all can route to each other, as follows:

VCSA-Active

Mgmt IP: a.a.a.a

HA IP: x.x.x.x

VCSA-Passive

Mgmt IP: b.b.b.b

HA IP: y.y.y.y

Witness

Mgmt IP: c.c.c.c

HA IP: z.z.z.z

If the above is possible then:

- When a failover happens from Active to Passive, do clients stop using IP a.a.a.a and start using IP b.b.b.b to reach vCenter services? Or would I need to manually make a change in DNS to point the VCSA FQDN from a.a.a.a to b.b.b.b and get that refreshed out across my network?

- Is there a guide that explains how to set it up this way?

As usual, thanks

Dryv

Hi All,

What are the different type of UUID in virtual machines

Hello to All!

We have problem with few of our 2008 R2 VM running on ESXi 6.0 host. vNIC is getting disappears from the virtual machine automatically without any intervention and there is no event indicating the removal of the network card found in vCenter task and event, and in Windows Event-viewer except in the below from vmware.log file.

2017-01-31T16:26:09.188Z| vcpu-0| I120: Powering off Ethernet0

2017-01-31T16:26:09.189Z| vcpu-0| I120: Hot removal done.

we have fixed this issue on two VM's by referring vmware kb-1012225, but still dont know why this happening.

Anyone have an idea! Thanks in Advance...

We recently updated our vSphere Server 5.5 to 6.0 and the NetApp VSC Plugin from 5.0 to 6.0.

Now the Plugin won't show up in the WebClient as it did before the upgrade.

Has anyone the same issue? Is there a solution for it?

The backup jobs defined before the upgrade are running.

Thanks

Hi,

i was trying to be happy to upgrade (in lab actually) my 6.5d vcenter to U1 on windows 2012r2, but the upgrade fails.

and it fails when it is trying to install VCSSServiceManager, after a lot of components update (more or less 1/4 of setup process).

as i can see, there is a script that invokes services restarts, and the services go down but they don't come up and the setup fails.

the rollback too.

as sequence, i can see in my vminst.log

E: RunFirstLastUpdateboot: Failed to run boot script "c:\windows\system32\cmd.exe /S /C "%programfiles%\vmware\vcenter server\bin\run-updateboot-script.bat" --action update >> %temp%\vminst-con.log 2>&1""

so i opened thevminst-con.log as suggested, and i can see:

ERROR starting service: VMWareST, Exception: (2, 'StartService', 'The system cannot find the file specified.' )

it is right, because if i try to start the suggested service i obtain the same result.

what do i should do?

thanks.

Hi Guys,

I need to create a plan for upgrading our existing Vmware infrastructure from Vcenter 5.0 to vCenter 6.0 as 5.0 is now out of support.  Our infrastructure is spread across multiple sites with a mix of Windows Server 2008 based vCenter 5.0 Servers & vCenter appliance running 5.1

Site 1 is running vCenter Server 5.0 on a Windows Server 2008 R2 VM, database path = localhost\VIM_SQLEXP. This server is managing 3 x ESXi hosts running 5.0

I would like to upgrade this server to vCenter 6.0 and also upgrade from Server 2008 R2 to 2012 R2 at the same time if possible.  Can someone please explain how I would achieve this? I planned to create a new Server 2012R2 VM and install vCenter 6.0 but Vmware support have advised that the database from server 2008 would not be compatible.

Has anyone had success doing this and able to offer advice?

Regards

John

How to find all mac addresses?

Has anyone else noticed that the option to "Use the Customization Wizard to temporarily adjust the specification before deployment" that exists in the C# client when deploying a machine from a template using the Customization Wizard is missing from the web client?

Has anyone else found that option as useful as I do to make one-off changes to a customization at deployment time that I don't want to save as a new customization?

Has anyone out there found an acceptable work around to this?  If it still hasn't made it into 5.5 I don't even think it's on their radar.

Hello Friends,

I have deployed VCSA 6.5 last month at my client place but now they are facing very much issues while accessing the web client. I have also found that it takes too much time to fully load the vSphere web client.
All the operations are performed at very slow. Many times i have seen that if i perform anything it will get completed but it doesn't appear in recent tasks.

In short we are facing very slow performance with vSphere Web client in vCSA 6.5.

If anyone is having the same please share the information or steps by which we can improve the performance.

Hi all,

I have an issue with the order in which the vCenter servers are displayed in the vSphere webclient on a fresh installed 6.5 environment.

Here is how I set it up:

I have 2 sites, siteA and siteB. First I deployed a PSC in site A and created an SSO domain. Then I deployed a vCenter (appliance) in Site A and linked it to the SSO domain. After that I installed the PSC in SiteB and linked it to the SSO domain in Site A. Last I installed the vCenter (appliance) in Site B and linked it to the PSC in site B.

Now when I log in the vSphere web client SiteB is on top of the vCenter servers list. It does not matter to which vCenter we connect it always shows SiteB on top.

The HTML client and the VI client are showing the right order where siteA is on top en siteB on the bottom.

How is this possible and how do I correct this?

I want to have siteA on top and siteB below that.

Thanks, Peter.

Hi

I am experiencing a problem since updating our VC to version 6.5. I have a defined set of roles that map to IT roles at our company, each role gives more rights to match the duties each job is expected to perform.

I migrated the roles across more or less like for like when going from 5.5 to 6.5 (leaving the additional nodes for areas like certificates with just full admins).

My problem is that I have a mid level role with staff who need to be able to place a host into maintenance and shut it down. Previously, and also according to the manuals, this should be granted by the privilege Host/Config/Maintenance. The role also has most other Host area privileges including Host/Config/Power although that should not be relevant. The staff can place the hosts in and out of maintenance but can't shut them down or reboot them.

Does anyone know what privilege I am missing?

Hello,

I have set up a test environment in my house with ESXi and VCSA. I don't have much memory (4GB for the VCSA) and i don't need most of the advantages that VCSA provides but i like and i am testing the functionality especially of the new HTML5 environment. However, after few days, both environments stop working. The issue goes away with a good old restart. I am assuming 4GB is not enough for the appliance, but is there a way i can disable features that i am using so the memory can be enough?

Thanks!

  I recently removed a physical host from a vCenter Server virtual appliance and am not able to add it back to vCenter Server because I get an error about the datastore already existing.  I am running a simple vCenter Server environment with two physical hosts and shared storage.  I have only been administering vCenter for a few months, so I am relatively new to the technology and processes.  I have searched the Internet for a few days now, but have not found any documentation of anyone experiencing the same problem as I (which I find odd considering how simple my configuration and problem), so I wanted to get some help from the VMware community.

  I got an error message one day that vCenter Server couldn't connect to one of the two hosts so I removed the host (instead of disconnecting and connecting as I should have done).  Now I am not able to connect the host to vCenter server because the shared storage datastore conflicts with the same datastore used by the existing host in vCenter Server.  The error message I get is ""Datastore 'datastore_name' conflicts with an existing datastore in the datacenter that has the same URL (ds:///vmfs/volumes/UUID/), but is backed by different physical storage."  I try to unmount the datastore from the host, but get the following error message: "The resource 'Datastore Name: datastore_name VMFS uuid: UUID' is in use."  The error stack says, "Call "HostStorageSystem.UnmountVmfsVolume" for object "storageSystem" on ESXi "IP address" failed.  Cannot unmount volume 'Datastore Name: datastore_name VMFS uuid: 'UUID' because file system is busy. Correct the problem and retry the operation."  I have tried removing all virtual machines from inventory, putting the hosts in maintenance mode, rebooting the physical hosts, but none of my troubleshooting is helping.

  I am not sure what steps to take to get this datastore unassociated with the host so that I can add it back into vCenter Server.  Any help you can provide me is appreciated.

Good day, and I hope yours is better than mine...

Just downloaded and set up VCSA 6.0 U2.  Finally got it to join my domain*.  Added admin group from domain and gave them permissions.  Every time I tried to use NT authentication (the checkbox) it would error out.

I found and followed articles 2020970 and 21112283.  Now I am unable to log into the web client nor the vSphere client.

web client yeilds this

A server error occurred.

[500] SSO error: Cannot connect to the VMware Component Manager https://vcenter.sso.unitedpolicefcu.com/cm/sdk?hostid=827ac00b-1131-452e-b9fa-6b69a3a3f7ef

Check the vSphere Web Client server logs for details.

          vsphere client says

Windows session credentials cannot be used to log into this server   (which is what started the 2 KBs above)

or

Cannot complete login due to incorrect user name or password  (I tried SSO Admin, domain user, appliance root user)

I have tried the certificate replacement steps (option 8, then 8, then 3, then 4, then 8 again).  Each ends with errors similar to this:

2016-03-29T18:35:36.382Z   Updating certificate for "com.vmware.vim.eam" extension

Status : 0% Completed [Operation failed, performing automatic rollback]

Error while performing Cert Replacement operation, please see /var/log/vmware/vmcad/certificate-manager.log for more information.

Performing rollback of Root Cert...

Get site name

hq

followed by this at the end of the roll back

Updated 0 service(s)

Rollback Status : 40% Completed [Rollback machine Cert...]                 

Rollback Status : 50% Completed [Rollback vsphere-webclient Cert...]                 

Rollback Status : 60% Completed [Rollback vpxd Cert...]                 

Rollback Status : 70% Completed [Rollback vpxd-extension Cert...]                 

2016-03-29T18:36:23.960Z   Updating certificate for "com.vmware.vim.eam" extension

Error while reverting certificate for store : vpxd-extension

Rollback Status : 0% Completed [Rollback operation failed]

Error while performing rollback operation, please try Reset operation...

please see /var/log/vmware/vmcad/certificate-manager.log for more information.

Thanks for the help from Stumped in Miami.

*  And for those of you getting Error 11 on trying to join the domain go into the SCVA web portal, drill down to the actual network settings and switch the DNS to manual.  Sorry I can't be specific on the actual path to this setting.  Although I gave it specific DNS at set up and a static IP I finally found that it had reverted to getting DNS from DHCP...  Hope this helps.

Hi Guys.

I am having an issue that is really starting to piss me off. I have moved from Windows vCenter to the VCSA appliance. Now on the whole it's a good experience. However one thing that is pissing off is this.

I can select say 5 machines on a host, right click and migrate to another host with no issues. I then select another 5 machines, right click select migrate and nothing. It's like the GUI has not received the request. Sometimes I can kick it back in to life by refreshing the IE page but often not.

Has anyone else experienced this?

I am running the latest VSA 6.5 , Windows 8.1 with IE 11. I am running IE as it handles the certificates for the VCSA from our internal CA.

Anyone else with this issue?

I am stumped. At first, I was able to at least login to vsphere and do operations. The client would close like every 15 minutes so it got really annoying. Now I am stuck with no launch to vsphere. I must log into each host individually. ESXi hosts without a vsphere is so limited. Please advise.

Here is the /var/log/messages

vsphere-fmrif:~ # tail -f /var/log/messages
May 31 09:50:32  vsphere-fmrif watchdog-vpxd: [4773] Begin '/usr/sbin/vpxd', min-uptime =  30, max-quick-failures = 5, max-total-failures = 1000000, bg_pid_file =  ''
May 31 09:50:32 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May  31 09:50:34 vsphere-fmrif kernel: [   59.780777] warning: process  `vpxd-worker' used the deprecated sysctl system call with 1.1.
May 31 09:50:40 vsphere-fmrif sshd[4944]: Accepted password for root from 128.231.212.117 port 51160 ssh2
May 31 09:50:44 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 12 seconds (quick failure 1) 134
May 31 09:50:44 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:50:45 vsphere-fmrif kernel: [   70.438974] warning: process `vpxd' used the deprecated sysctl system call with 1.1.
May 31 09:50:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 2) 134
May 31 09:50:51 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:50:52 vsphere-fmrif kernel: [   77.370397] warning: process `vpxd' used the deprecated sysctl system call with 1.1.
May 31 09:50:58 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 3) 134
May 31 09:50:58 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:50:58 vsphere-fmrif kernel: [   83.923261] warning: process `vpxd' used the deprecated sysctl system call with 1.1.
May 31 09:51:05 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 4) 134
May 31 09:51:05 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May  31 09:51:06 vsphere-fmrif kernel: [   91.720959] warning: process  `vpxd-worker' used the deprecated sysctl system call with 1.1.
May 31 09:51:12 vsphere-fmrif auditd[3012]: Audit daemon rotating log files
May 31 09:51:13 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 8 seconds (quick failure 5) 134
May 31 09:51:13 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:51:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 6 seconds (quick failure 6) 134
May 31 09:51:19 vsphere-fmrif watchdog-vpxd: End '/usr/sbin/vpxd', failure limit reached

/var/log/warn

May 31 02:40:23 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:41:26 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:42:28 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:43:31 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:44:33 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:45:36 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:46:38 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:47:41 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:48:44 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:49:46 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:50:49 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:51:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:52:54 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:53:56 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:54:59 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:56:01 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:57:04 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:58:06 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:59:09 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:00:12 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:01:14 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:01:52 vsphere-fmrif portmap[25177]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:01:52 vsphere-fmrif portmap[25178]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:01:53 vsphere-fmrif portmap[25179]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:02:17 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:03:07 vsphere-fmrif portmap[25275]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:03:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:04:04 vsphere-fmrif portmap[25358]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:04:19 vsphere-fmrif portmap[25368]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:04:22 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:05:25 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:06:01 vsphere-fmrif portmap[25531]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:06:27 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:06:31 vsphere-fmrif portmap[25603]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:07:00 vsphere-fmrif portmap[25618]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:07:30 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:08:32 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:09:35 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:10:38 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:11:40 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:12:20 vsphere-fmrif portmap[26072]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:12:43 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:12:54 vsphere-fmrif portmap[26144]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:13:45 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:13:48 vsphere-fmrif portmap[26227]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:14:17 vsphere-fmrif portmap[26242]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:14:48 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:15:09 vsphere-fmrif portmap[26348]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:15:17 vsphere-fmrif portmap[26354]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:15:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:16:03 vsphere-fmrif portmap[26435]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:16:53 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:16:53 vsphere-fmrif portmap[26472]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:16:59 vsphere-fmrif portmap[26519]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:17:56 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:18:30 vsphere-fmrif portmap[26621]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:18:58 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:20:01 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:21:03 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:21:37 vsphere-fmrif portmap[26897]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:22:06 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:23:09 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:24:11 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:24:22 vsphere-fmrif portmap[27146]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:25:14 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:26:16 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:26:40 vsphere-fmrif portmap[27330]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:27:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:28:21 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:29:24 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:30:27 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:31:29 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:32:32 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:33:35 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:34:37 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:35:40 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1

/var/log/vmware/vpx/vpxd.log

 

From earlier:

vsphere-fmrif:~ # tail -f -n 100 /var/log/vmware/vpx/vpxd.log

Section for VMware VirtualCenter, pid=25488, version=5.0.0, build=build-455964, option=Release

 

------ In-memory logs start --------

2012-05-31T09:11:29.623-04:00 [7FFFF3B09700 info 'Hooks'] Hooks Initialized

 

------ In-memory logs end   --------

2012-05-31T09:11:29.633-04:00 [7FFFF3B09700 info 'Default'] Initialized channel manager

2012-05-31T09:11:29.641-04:00 [7FFFF3B09700 info 'Default'] Current working directory: /storage/log/vmware/vpx

2012-05-31T09:11:29.642-04:00 [7FFFF3B09700 info 'Default'] Log path: /var/log/vmware/vpx

2012-05-31T09:11:29.642-04:00 [7FFFF3B09700 info 'Default'] Initializing SSL

2012-05-31T09:11:29.645-04:00  [7FFFF3B09700 info 'Default'] Vmacore::InitSSL: doVersionCheck = true,  handshakeTimeoutUs = 120000000

2012-05-31T09:11:29.646-04:00 [7FFFF3B09700 info 'Default'] Changed working directory to /var/log/vmware/vpx

2012-05-31T09:11:29.666-04:00 [7FFFF3B09700 info 'Default'] Starting VMware VirtualCenter 5.0.0 build-455964

2012-05-31T09:11:29.666-04:00 [7FFFF3B09700 info 'Default'] Log directory: /var/log/vmware/vpx.

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] Account name: root

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:835] Calling: InfoDeclSchema(gDB)

2012-05-31T09:11:29.667-04:00  [7FFFF3B09700 info 'Default'] [Init:837] Calling:  VpxCallbackDesc::Init(MakeFunctor(this,  &ServerApp::RequestShutdown))

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:838] Calling: VpxCryptInit()

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:839] Calling: VpxLRO::Init()

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:840] Calling: VpxLroList::Init(ltud)

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 640 max LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved internal LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved blocker LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved short LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 8 reserved long LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 600-second completed task lifetime

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 60-second minimum completed task lifetime

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 200 maximum completed tasks

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 600-second unregistered task lifetime

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:841] Calling: VpxdCharacterizeThreadpool(ltud)

2012-05-31T09:11:29.667-04:00  [7FFFF3B09700 info 'ThreadPool'] [SetConfig] Thread info: IoMin: 2,  IoMax: 1990, TaskMin: 59, TaskMax: 1990, Max Thread: 3980, Keepalive:  61, thread kill: 600, max fds: -1

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:842] Calling: VpxdCertificate_Load(gDB, CERTIFICATE_VMDBPATH )

2012-05-31T09:11:29.668-04:00  [7FFFF3B09700 info 'Default'] [Init:843] Calling:  VpxdVdb::Init(VpxdVdb::GetVcVdbInstId(), false, false, NULL)

2012-05-31T09:11:29.668-04:00 [7FFFF3B09700 info 'Default'] Registry Item DB 5 value is ''

2012-05-31T09:11:32.078-04:00  [7FFFF3B09700 info 'Default'] [VdbSchemaLoader::LookupSchemaFromDB]  Loaded schema and index information from DB

2012-05-31T09:11:32.099-04:00 [7FFFF3B09700 info 'Default'] [Init:844] Calling: VpxdDbSchemaHash::CheckSchema()

2012-05-31T09:11:32.100-04:00  [7FFFF3B09700 info 'Default'] [VpxdDbSchemaHash::CheckSchema]: schema  file: /usr/lib/vmware-vpx/VCDB_db2.sql

2012-05-31T09:11:32.104-04:00 [7FFFF3B09700 info 'Default'] [Init:845] Calling: VpxdDbMonitoring::Init()

2012-05-31T09:11:32.120-04:00 [7FFFF3B09700 info 'Default'] [Init:848] Calling: VpxdLdap::Init()

2012-05-31T09:11:32.121-04:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Making sure LDAP instance VMwareVCMSDS is running

2012-05-31T09:11:32.121-04:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Checking service ldap for running

2012-05-31T09:11:32.179-04:00 [7FFFF3B09700 info 'Default'] [Init:849] Calling: VpxResultFilter::Init()

2012-05-31T09:11:32.179-04:00  [7FFFF3B09700 info 'Default'] Looking for vpx result filter at  /usr/lib/vmware-vpx/vpxResultFilter.xml

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:853] Calling: VpxdLock::Init(gDB)

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:854] Calling: VpxdMoLock::Init()

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:855] Calling: VpxdStateLock::Init()

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:856] Calling: VpxdMoDataTable::Init()

2012-05-31T09:11:32.184-04:00  [7FFFF3B09700 info 'Default'] [Init:858] Calling:  VpxdHeartbeat::Init(MakeFunctor(this, &ServerApp::RequestShutdown))

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:859] Calling: VpxdHostCnx::Init(gDB)

2012-05-31T09:11:32.189-04:00 [7FFFEAA06710 info 'Default' opID=SWI-75fe915a] Pre-loading symbols...

2012-05-31T09:11:32.190-04:00 [7FFFEAA06710 info 'Default' opID=SWI-75fe915a] Done pre-loading symbols.

2012-05-31T09:11:32.196-04:00 [7FFFF3B09700 info 'Default'] [Init:861] Calling: VpxdVmomi::Init()

2012-05-31T09:11:32.198-04:00  [7FFFF3B09700 info 'Default'] Looking for vpx result filter at  /usr/lib/vmware-vpx/vpxResultFilter.xml

2012-05-31T09:11:32.200-04:00 [7FFFF3B09700 info 'Default'] [Init:862] Calling: QueryServiceProviderHelper::Init()

2012-05-31T09:11:32.201-04:00 [7FFFF3B09700 info 'QueryServiceProvider'] Initializing QueryServiceProviderHelperImpl

2012-05-31T09:11:32.240-04:00 [7FFFF3B09700 info 'QueryServiceProvider'] Starting with generation number: 5230290

2012-05-31T09:11:32.240-04:00 [7FFFF3B09700 info 'Default'] [Init:863] Calling: ServiceDirectory_Init()

2012-05-31T09:11:32.240-04:00  [7FFFF3B09700 info 'Default'] [ServiceDirectory] Local instance UUID:  DB25B17D-3703-4779-BAFB-845B64AC33AA

2012-05-31T09:11:32.245-04:00 [7FFFF3B09700 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 2578 ms

2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 error 'Default'] [VpxdMain] Failed to initialize: Name or service not known

2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...

2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 info 'Default'] Wrote uptime information

2012-05-31T09:12:32.701-04:00 [7FFFF3B09700 info 'Default'] Forcing shutdown of VMware VirtualCenter now

and the process itself

vsphere-fmrif:~ # service vmware-vpxd status
vmware-vpxd is stopped
tomcat is stopped
vsphere-fmrif:~ # service vmware-vpxd start
Waiting for embedded DB2 database to startup: .success
Cleaning session lock table: success
Verifying EULA acceptance: success
Shutting down ldap-server..done
Starting ldap-server..done
Starting vmware-vpxd: success
Waiting for vpxd to initialize: ....failed

Hi,

Unable to power off/reset/shutdown a VM, current version of ESXi 5.5, could some one please help us on this.

Thanks in Advance

I just instaled a vCenter 6.0, and i have noticed that the Administrator@vsphere.local does no have permissions to create user/groups