Hi,

I am working on getting a new implementation of VCSA v5.5 up and running and I have the VM created and working, but I am having an issue changing the name of the server.  I am running the /opt/VMware/share/vami/vami_config_net program and setting the new name.  I then exit the program and reboot the VM and the old name comes back instead of the new name.  I have even tried setting the hostname using the Linux HOSTNAME command and it looks like it takes, but once again, as soon as I reboot the server, it reverts back to the old hostname.

Any ideas what is going on?

Thanks,

Sean

Morning,

Got an odd one. We have a virtual Windows vCenter Server. When we take a snapshot (with or without memory) all hosts on the vCenter briefly disconnect.  This happens in the last second of snapshot creation.

The backup of the virtual server takes a snapshot during the evening so the host disconnection is triggered every evening.

The strange thing is if I take a manual snapshot I can replicate the issue.  If I delete the snapshot and then create another the issue no longer occurs.  It seems to only occur after a period of time.

vCenter Version 5.0.0 build 455964.

14 x ProLiant DL380 G7

2 x 8GB Fibre Channel

1GB NICS

100GB RAM

12 x 3GHz CPU

Only 83 VM's.

Any tips on how I can diagnose this?

I'm trying to figure out if it's possible to change the name of the vpxd log file and rotation/compression that vCenter performs.  I want to have vpxd.log asthe only file that ever gets written to and to set log rotation to be the same that any normal syslog service would do by compressing the log and incrementing the compressed filename.  I'll try to explain what I'm trying to change

The vpxd log file is created as vpxd-01.log.  Once it hits the file size threshold, a new file is created with a name that increments up from the previous file, e.g. vpxd-02.log.  Eventually the files are rotated and old log files get compressed at some point after the new files are created.  So a new file is created called vpxd-03.log and vpxd-01.log gets compressed as vpxd.-01.log.gz.  I simply want vpxd message to be written to one log file: vpxd.log.

Does anybody know if this is possible?

I am playing around with the vCenter 5.5 appliance (investigating whether it is feasible to move to the appliance from Windows hosted vCenter).  We are currently running vCenter 5.0, so I have no experience with SSO until now.  I successfully joined the vCenter appliance to AD (I can see the object in AD) and then I added our domain as a SSO source in vCenter.  I made sure to use a FQDN host name for the appliance as I saw a few issues with joining the domain if the host name was not in FQDN format.  When I configured SSO, I used "Active Directory (Integrated Windows Authentication)" and then "Use machine account" - which from what I understand, all that is needed is that I joint the appliance to the domain - which, as I stated, appears to be successfully joined to our domain.  When I added the domain to SSO, there were no errors and I see it in the list now.  Thus as far as I can tell, the setup for SSO was completely error free.

However, when I try to add resources from AD to vCenter (for example to add AD users/groups to the vCenter administrators group or to assign role permissions to objects in vCenter) the browse window for our domain just hangs,  In the web interface I see a little blue progress bar spinning for ever, and in the vSphere Windows GUI client, the browse window just hangs and I have to kill the process.

Did I miss some critical step in SSO setup for AD?  Am I not supposed to use "machine account"?

Any help is appreciated.

NK

I've been trying to publish the Web Client through our SSL VPN which has a nice workspace to publish web links.

Unfortunately, something in the vSphere web client breaks very badly if you do not connect directly to the application - it loads the background image but instead of displaying the login dialog it simply bombs out with an "Error #2032" message.

Anyone found a fix for this?

We have two hosts, one locally and the other remote, and require a second vCenter for the remote location. We are doing this for Business Continuity and will be replicating our VMs between the two sites. Our current local vCenter runs vCenter Server 5.1 Essentials. When I go to the Download page, I see several options for downloads including VMware vCenter Server 5.5.0b and modules, VMware vCenter Server 5.5.0b Appliance, OVF file, System Disk, Data Disk, and Appliance. Which one should I download? Also, our current vCenter is running 5.1 and these downloads are all for 5.5. Will the different versions cause us concern?

Thanks,

Dave

Hi,

I have updated the vCenter 5.5 to the latest version that is available yesterday. It is linux appliance.

I was having problem to get in to web client after the update. I performed the "Regenerate SSL certificates" option thats located under Admin tab. Then the issue is resolved and I am able to get in to web client.

Now, I am seeing the different issue.

Unable to retreive health data from http://localhost/sps/health.xml

Unable to retreive health data from http://localhost/sms/health.xml

These 2 services are running but not able to load it. Also, I am seeing the following exceptions in the log.

From vpxd log:

--------------------

[7F4D4DD3A700 error 'HttpConnectionPool-000340'] [ConnectComplete] Connect failed to <cs p:00007f4cd40b2850, TCP:vc55mjl1.lab.equallogic.com:10443>; cnx: (null), error: N7Vmacore3Ssl18SSLVerifyExceptionE(SSL Exception: Verification parameters:

--> PeerThumbprint: 36:D5:B5:C2:8B:A5:A6:40:39:10:57:A0:0A:CF:B0:75:1B:62:31:1F

--> ExpectedThumbprint: 06:E3:CB:EB:48:12:59:47:1E:AA:05:69:B0:D5:42:14:AD:5B:63:85

--> ExpectedPeerName:xxxxxxxxxxxx

--> The remote host certificate has these problems:

-->

--> * unable to get local issuer certificate)

From vws log:

[2014-01-03 22:09:26,979 Thread-21  ERROR com.vmware.vim.health.impl.XmlUtil] Error retrieving health from url: http://localhost/sps/health.xml

java.io.IOException: Server returned HTTP response code: 503 for URL: http://localhost/sps/health.xml

        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)

        at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)

        at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)

        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

        at org.apache.xerces.jaxp.validation.StreamValidatorHelper.validate(Unknown Source)

        at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(Unknown Source)

        at javax.xml.validation.Validator.validate(Unknown Source)

        at com.vmware.vim.health.impl.XmlUtil.getDocumentFromUrl(XmlUtil.java:96)

        at com.vmware.vim.health.impl.ComponentSpec.retrieveHealthFromUrl(ComponentSpec.java:300)

        at com.vmware.vim.health.impl.ComponentSpec.retrieveHealth(ComponentSpec.java:266)

        at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealthFromUrl(HealthPollerImpl.java:119)

        at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealth(HealthPollerImpl.java:104)

        at com.vmware.vim.health.impl.HealthPollerImpl.computeHealth(HealthPollerImpl.java:203)

        at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealth(HealthPollerImpl.java:102)

        at com.vmware.vim.health.impl.HealthPollerImpl.pollHealth(HealthPollerImpl.java:85)

        at com.vmware.vim.health.impl.HealthPollerImpl.access$100(HealthPollerImpl.java:28)

        at com.vmware.vim.health.impl.HealthPollerImpl$PollerThread.run(HealthPollerImpl.java:55)

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

[2014-01-03 22:09:26,979 Thread-21  ERROR com.vmware.vim.health.impl.ComponentSpec] Unable to retrieve health for com.vmware.vim.sps from http://localhost/sps/health.xml

[2014-01-03 22:09:26,979 Thread-21  ERROR com.vmware.vim.health.impl.ComponentSpec] Unable to retrieve health for com.vmware.vim.sps from any of its health URLs

[2014-01-03 22:09:26,981 Thread-21  ERROR com.vmware.vim.health.impl.XmlUtil] Error retrieving health from url: http://localhost/sms/health.xml

java.io.IOException: Server returned HTTP response code: 503 for URL: http://localhost/sms/health.xml

        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)

        at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)

        at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)

        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

        at org.apache.xerces.jaxp.validation.StreamValidatorHelper.validate(Unknown Source)

        at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(Unknown Source)

        at javax.xml.validation.Validator.validate(Unknown Source)

        at com.vmware.vim.health.impl.XmlUtil.getDocumentFromUrl(XmlUtil.java:96)

        at com.vmware.vim.health.impl.ComponentSpec.retrieveHealthFromUrl(ComponentSpec.java:300)

        at com.vmware.vim.health.impl.ComponentSpec.retrieveHealth(ComponentSpec.java:266)

        at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealthFromUrl(HealthPollerImpl.java:119)

        at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealth(HealthPollerImpl.java:104)

        at com.vmware.vim.health.impl.HealthPollerImpl.computeHealth(HealthPollerImpl.java:203)

        at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealth(HealthPollerImpl.java:102)

        at com.vmware.vim.health.impl.HealthPollerImpl.pollHealth(HealthPollerImpl.java:85)

        at com.vmware.vim.health.impl.HealthPollerImpl.access$100(HealthPollerImpl.java:28)

        at com.vmware.vim.health.impl.HealthPollerImpl$PollerThread.run(HealthPollerImpl.java:55)

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

I have loooked at the hosts file and make sure DNS is right. Also, Performed Regenerate certificates on appliance. Any ideas where to look for to troubleshoot??

Appreciated ,

Thanks!!

I'm trying to install VMware vCenter Server 5.5 on a windows server 2008 R2 that is a virtual machine inside VMworkstation and I keep getting the error

"Unable to contact Lookup Service. Check vm_ssoreg.log in the system temporary folder for more details..."

My setup all within VMworkstation:

-windows server2008r2 primary domain controller host name/ip= dc1/10.10.10.100

-windows server2008r2 secondary domain controller host name/ip = dc2/10.10.10.105

-windows server2008r2 ->trying to install vCenter Server host name/ip = vctr/10.10.10.110

All the vm's above are on the same NAT'd for workstation settings

I've read tons of articles on this error on the only things I could find are:

-password has non ASCII character -> not my issue

-DNS is not correct -> using nslookup all ips resolve to correct host names

-There is update 5.1.0 1a but I cannot download it from vmware.com bc I don't have permission

I'd really like to evaluate this product but can't get past this error if anyone can help PLEASE let me know!

thanks in advance

We have 9 physical server nodes/hosts and we're preparing to setup a VMware vCenter test lab (for learning/practicing with using vCenter Server) for performance evaluation, prior to making a decision on whether to use vSphere for our client's hardware production use.

We've read through vSphere Installation and Setup manual, but we are facing several problems.

We have eight diskless nodes (that are each booting ESXi 5.5 off of a 8GB USB stick)

We have one main server node (that is booting ESXi 5.5 off a 16GB USB stick)

- The main server node has four 4TB hard drives installed in it (all are blank/empty/unformatted)

This is what we've done so far:

1) Installed ESXi 5.5 on all 9 nodes (on each USB stick)

This is what we still need to do:

1) Create four 4TB VMFS datastores (or create a 16TB vSAN using four 4TB datastores?)

2) Install vCenter Server Appliance VM (with vCenter Single Sign-On, vSphere Web Client, vSphere Inventory Service and vCenter Server) on the newly created datastore.

The problem we are having now, is we are trying to create a 4TB VMFS datastore on each of the four 4TB hard drives, or possibly setup a vSAN using the four 4TB drives (into one large 16TB cluster?).

We want to install vCenter Server Appliance on the 4TB VMFS datastore (or vSAN), and use the vCenter Server Appliance to manage/configure each of the 9 ESXi 5.5 server nodes.

After reading the instructions, we seem to be extremely confused, because the instructions seem to create a "chicken and the egg" problem.  What comes first, the chicken or the egg?  The instructions say to install the vCenter Server Appliance on a datastore.  We can't create a 4TB datastore using the C# vSphere client, so how do we create a 4TB VMFS datastore?

The instructions are very unclear, and we can't figure out how (step-by-step) to create a single 4TB VMFS datastore (using the vSphere Client), and how do we install a vCenter Server Appliance onto a 4TB VMFS datastore without having a vCenter Server Appliance (with Web Client) installed to create the 4TB VMFS datastore?

I really wish that the VMware vCenter Client (C# based client) was updated to support vSphere 5.5, and would allow you to create 4TB VMFS datastores, and allow you to install the vCenter Appliance onto a 4TB VMFS datastore from the C# vSphere Client.

Any ideas as to how we can format our first 4TB VMFS datastore using the vSphere Client?  We do not have any datastores currently created, and although we have four 4TB hard drives inside the machine, we are not sure how to even create a 4TB VMFS datastore on the 4TB drives, since the VMware vSphere Client doesn't seem to support vSphere 5.5 features (including 4TB datastores), and there is no way to install the Web Client without having the vCenter Server Appliance (with Web Client) running?  Correct?

How do we get a 4TB VMFS datastore created if the vSphere Client doesn't support creating 4TB VMFS datastores?  Can you install a vSphere Web Client locally, on a local machine?  Is that the only way to get a 4TB VMFS datastore created?  

Thank-you for all your help,

Hi,

I got problem that Web Client is not able to connect to vCenter. It is showing message:

HTTP Status 404 - /vsphere-client/

--------------------------------------------------------------------------------

type Status report

message /vsphere-client/

description The requested resource (/vsphere-client/) is not available.

--------------------------------------------------------------------------------

Apache Tomcat/7.0.26

I have tried to restart Web Clent Server but not helped.

Please help!

I recently upgraded from vCenter 5.1 to 5.5. After the upgrade I began to get health warnings for the VMware vCenter Storage Monitoring Service that say "Service initialization failed". I have rebooted the vCenter server and restarted the services several times and that has not cleared the issue. When I look in the SMS.LOG file there is no activity in it since the date I did the upgrade (a week or more ago). All prior activity in the SMS.LOG looks to be fine up up until the upgrade occured though. I have found at least a half-dozen KB articles that describe various reasons why this error might occur but they all pertain to older versions of vCenter. Just to be thorough though I reviewed the symptoms in the articles and none of them really seem to be the same as what I am seeing. My one hypothesis is that perhaps the SMS didn't get properly re-installed during the upgrade because I don't see any SMS sub directory in the \Program Files\VMware\Infrastructure\tomcat\webapps directory but I'm not even sure if this directory should exist on a 5.5 installation.

Would appreciate if anyone has any troubleshooting advice for this type error.

Thanks,

Mike

Hi All,

I recently moved our vCenter installation to another server "vCenterServer" from the original server "Win12-ban", I have left the database on "Win12-ban" and created a DSN on "vCenterServer" which tests successfully when connecting into the database from the "vCenterServer" database. When I originally set this all up it worked a dream, I was originally using my own domain account to start the service (rather than the local system account), but now none of these accounts will start the service. I really want to be using the local account as I want to be able to see performance stats within vcenter.

The error message I get when trying to start the service is:

Followed by this in the event viewer:

Task Category: None

The description for Event ID 1000 from source VMware VirtualCenter Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Error getting configuration info from the database

I have tested the DSN from the machine with vCenter installed and it tests successfully, which suggests there is a connection from the vCenter Server to the database, has anyone encountered similar issues?

Hello

In Horizon View Administrator, within the System Health, the Connection Server has a warning advising the service is not working properly.

In addition within the pools, the desktop provisioning isn't working, although there is no error, nor is it disabled. However it is not automatically provisioning new desktops when it should. Within the event logs on the Connection Server, the 1404 entry BROKER_POOL_EMPTY, Unable to launch from Pool, the Pool is empty is recorded for every attempted login by an assigned account.

This is an existing connection server and setup that has been running for months with no issue. Does anyone know what may cause this issue?

Many Thanks

Hey

we have a few ESXi hosts running the original 5.0.0 version, and a few running the latest 5.1 U1 or whatever, and the latest vCenter for this too.

the vCenter server is on one of the hosts running 5.0.0 and these won't allow HA to be enabled properly. The issue is a known bug, and you have to go into maintenance mode and do funky stuff on the cli to get it working. However, I simply want to move all my vms off the old 5.0.0. hosts and onto the new ones, as the old ones will be decommissioned. I can do all the vms by simply shutting them down and migrating when off, but I won't be able to do this in vCenter with the vCenter vm off!

can I power it down, connect to the ESXi host directly, remove it from it's inventory (does this option even exist on the ESXi host direct?), and register it on the new 5.1.0 U1 host and fire it up?

will vCenter complain or fail when it comes back up?

they all share the same datastores, so I don't need to move the backend.

thoughts?

thanks

Roger

Hello All,

I know it is possible to register a new vCenter Server to an  existing SSO server. In my case, SSO server is part of one domain, and the new vCenter server will be part of another domain. Is it still possible in this scenario? We are with vSphere 5.1 update 1

Thanks,

Sree

Hi All,

VCenter was installed previously by a colleague that has now left the company, I am trying to move vCenter server to another machine and leave the current database in place on the current machine.

When running the "Simple" install I choose existing SSO database, and I'm asked for RSA_USER and RSA_DBA users, I can see them on our SQL server but do not have the passwords (have tried the defaults we usually use).

What is the best way of getting around this as I want to use the existing database?

Hi,

there is an option in vCenter for every VM to "lock the guest operating system when the last remote user disconnects". Is it possible to enable this globally, because I won't enable it for every VM.

vSphere Documentation Center

Regards Wolfgang

Hi,

A new security feature has been introduced with vCenter 5.5. Now by default, there is a password expiration. So the administrator account (root) password will expire automatically after 90 days of powering on the VCSA. That's a good idea but sometimes you forgot good security practices...

To unlock your root account :

1) Reboot your VCSA

2) Interrupt boot at grub level

3) Type p

4) Enter default password (vmware)

5) Edit  line started by kernel (type e)

6) At endline, add init=/bin/bash

7) Press enter then b (=boot)

If it's ok, your are root

8) Edit /etc/shadow

9) For the root user account, delete "x" in the 2nd field and delete the numeric value in the 5th field (default value is 90)

10) Save your file ( you could have a warning with a readonly file, but the file is really written)

11) Reboot

12) Try to log on  https://@IP or FQDN_VCSA5.5:5480 with your root account (login:root password=vmware)

13) Enjoy 

Optional (but recommended)

14) Modify your settings, enable password expires and configure a smtp server in order to be prevented

Since the upgrade of vSphere server from version 5.0 to 5.1 some users are no longer able to login, but the vSphere web client works fine.

They get the error: The server 'xxx' took to long to respond. (The command was timed out as the remote server was taking too long to resond.)

The client log file shows this:

at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName, Object[])
   at Vmomi.SessionManager.LoginBySSPI(String, String)
   at VmomiSupport.VcServiceImpl.LoginBySSPI(LoginSpecInternal2)
   at VmomiSupport.VcServiceImpl.Login(LoginSpec)
   at VirtualInfrastructure.LoginMain.Process(BackgroundWorker, DoWorkEventArgs)
   at VirtualInfrastructure.LoginWorkerImpl.Worker_DoWork(Object, DoWorkEventArgs)
...
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object)
[viclient:Error   :P: 3] 2012-09-18 10:06:52.925  RMI Error Vmomi.SessionManager.LoginBySSPI - 5
<Error type="VirtualInfrastructure.Exceptions.RequestTimedOut">
  <Message>The request failed because the remote server 'esxvc02' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)</Message>
  <InnerException type="System.Net.WebException">
    <Message>The command has timed out as the remote server is taking too long to respond.</Message>
    <Status>Timeout</Status>
  </InnerException>
  <Title>Connection Error</Title>
  <InvocationInfo type="VirtualInfrastructure.MethodInvocationInfoImpl">
    <StackTrace type="System.Diagnostics.StackTrace">
      <FrameCount>17</FrameCount>
    </StackTrace>
    <MethodName>Vmomi.SessionManager.LoginBySSPI</MethodName>
    <Target type="ManagedObject">SessionManager:SessionManager [esxvc02]</Target>
    <Args>
      <item></item>
      <item></item>
    </Args>
  </InvocationInfo>
  <WebExceptionStatus>Timeout</WebExceptionStatus>
  <SocketError>Success</SocketError>
</Error>
[viclient:Critical:M: 7] 2012-09-18 10:06:52.940  Connection State[esxvc02]: Disconnected
[viclient:SoapMsg :M: 7] 2012-09-18 10:06:52.940  Attempting graceful shutdown of service ...
[viclient:SoapMsg :M: 7] 2012-09-18 10:06:52.956  Pending Invocation Count: 0
[viclient:SoapMsg :M: 7] 2012-09-18 10:06:52.956  Graceful shutdown of service: Success
[        :Error   :M: 7] 2012-09-18 10:06:52.956  Error occured during login
VirtualInfrastructure.Exceptions.LoginError: The server 'esxvc02' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
   at VirtualInfrastructure.LoginMain.Process(BackgroundWorker worker, DoWorkEventArgs e)
   at VirtualInfrastructure.LoginWorkerImpl.Worker_DoWork(Object sender, DoWorkEventArgs e)
...
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server 'esxvc02' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
   at VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync(ManagedObject mo, MethodName methodName, Object[] parameters, Int32 timeoutSecs)
   at VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod(ManagedObject mo, MethodName methodName, Object[] pars)
   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName methodName, Object[] pars)
   at Vmomi.SessionManager.LoginBySSPI(String base64Token, String locale)
   at VmomiSupport.VcServiceImpl.LoginBySSPI(LoginSpecInternal2 loginSpec)
   at VmomiSupport.VcServiceImpl.Login(LoginSpec loginSpec)
   at VirtualInfrastructure.LoginMain.Process(BackgroundWorker worker, DoWorkEventArgs e)
System.Net.WebException: The command has timed out as the remote server is taking too long to respond.

In my vpxd.log file I see at the same time:

2012-09-18T10:06:53.036+02:00 [11704 error 'SoapAdapter.HTTPService'] HTTP Transaction failed on stream TCPStreamWin32(socket=TCP(fd=16104) local=127.0.0.1:8085,  peer=127.0.0.1:59602) with error class Vmacore::SystemException(An established connection was aborted by the software in your host machine. )

Someone knows how to resolve this?

Thanks,

Bart

Is vCenter 5.1 supported using SQL 2012 SP1 x64 Enterprise supported? I can find SQL 2012 x64 enterprise but not any info on SP1 support.