vCenter Appliance fsck failed

While I have been working with a customer on upgrading their infrastructure to vSphere 5.5, they had a power outage during the night which got their full virtual infrastructure down including storage (Not sure what the story with their UPS/Power generator). After they have brought their virtual infrastructure backup up both their vCenter Appliance and VDP appliance and few other Linux VMs has failed the fsck check while it was booting and it was stuck at the following error:

=========================================

fsck failed.  Please repair manually and reboot.  The root
file system is currently mounted read-only.  To remount it
read-write do:

bash# mount -n -o remount,rw /

Atention:  Only CONTROL-D will reboot the system in this
maintanance mode.  shutdow or reboot will not work.

Give root password for maintenance
(or type Control-D to continue):

==========================================

Below is an actual screenshot of the error for you to compare it with what you got:

VMware vCSA fsck failed

Below is the steps I have followed to fix this on both vCSA and VDP Advanced:

  1. Stay Calm & Don’t Panic!
  2. Take a backup/snapshot in case the below steps does not work for you and you need to revert it back to the current state when you call support or call for help.
  3. Read More

vCenter Server Appliance Error: failed to connect to VMware Lookup Service

While working with VMware vCenter Server Appliance 5.5, I needed to change the IP Address of the appliance as my customer were changing their IP scheme. It was quite to go to the VMware vCSA then to the network tab then Address tab and change the IP Address. After rebooting the appliance to ensure the IP change has taken affect and is working properly and consistent, I was able to login to the vCenter Server Appliance Management portal, but I was not able to connect to using the Web Client and was kept getting the following error:

“Failed to connect to VMware Lookup Service https://<vCenter Appliance IP>/lookupservice/sdk – SSL certificate verification failed”

Or as shown in the below screenshot:

Web Client Error after changing vCenter Appliance IP

 

It seems changing the IP Address of the vCenter Server Appliance does not regenerate the certificate with the new IP and you will have to configure the appliance to generate a new one manually. The good news it is pretty easy to do, and below is the instruction:

  1. Log in to the vCenter Server Appliance Web interface at https://<vCSA IP>:5480/.
  2. Click the Admin tab.
  3. Regenerate certificates:
    • vCenter Server 5.1: Select Toggle certificate setting so that the Certificate regeneration enabled displays Yes.
  4. Read More

vCenter Server Appliance 5.5 limitations

VMware vCenter Server Appliance 5.5 has been gaining huge attraction lately, especially with many of the major limitations affecting the vCenter Appliance in previous verions have been lifted. This is including the limitation where it was only supposed to support 5 hosts and 50 VMs when using the embedded database. In fact the all shiny new VMware vCSA 5.5 support up to 100 hosts and 3000 VMs using the embedded database, which seems to be able to deliver up to the scale required by most customers.

Note: It seems a misleading assumption has been going around that 100 hosts and 3,000 VMs is the maximum supported configuration by VMware vCSA 5.5, where is that is absolutely not true. This limit only apply when using the embedded  built-in vPostgres where it actually can support up to the vCenter maximums of 1,000 hosts and 10,000 VMs when connected to an external Oracle Database. This is clearly documented on page 7 of vSphere 5.5 Maximums guide and a copy of that table is shown below. I believe this misleading belief has spread as many bloggers has mentioned the 100 hosts and 3,000 VMs limit while failing to point out it is not the actual limit of the appliance, but it only apply when using the embedded database. 

VMware vCenter Server Appliance Maximum Configurations

I have actually been using VMware vCenter Server Appliance 5.5 for most of my labs and at various customers as it deliver what they needs, as it can be deployed in fraction of the time and save them from having to build Windows and DB servers, not to mention its easier to maintain and manage.… Read More

Deploying VMware vCenter 5.5 Appliance

Lately for most of my labs and even for many customers I have been deploying the VMware vCenter 5.5 Appliance, as it is much quicker to install and give less chances for error. Further it saves customers a Windows license and not to mention being much easier to maintain, patch and upgrade. Further, with many of the earlier versions limitations being lifted it becoming much more viable option than ever before. For that I have decided to document the process of installing the VMware vCenter 5.5 Appliance in a hope to encourage more of you to try it out.

 VMware vCenter 5.5 Appliance Installation Steps:

1- Download the VMware vCenter 5.5 Appliance OVA (I rather the OVA as all you have to get and deploy is a single file)

2- Deploy the VMware vCenter 5.5 OVA into one of your hosts.

  1. Launch the vSphere Client or vSphere Web Client.
  2. Go to File > Deploy OVF Template.
  3. Browse to the location of the vCenter Server Appliance downloaded .ova or the .ovf file and click Open.
  4. In the OVF Template Details page, click Next.
  5. In Name and Location, enter the name of your vCenter Server Appliance and click Next.
  6. Read More

VMware vCenter Server Appliance Error: VPXD must be stopped to perform this operation.

While playing with VMware vCenter Server Appliance in my home lab, I have been surprised with the following error:

Error: VPXD must be stopped to perform this operation.

This error has came up while trying to change authentication to active directory authentication and kinda seen the same error when trying to change the database to an external database. For some reason the Server service stop button is shadowed as well which mean I could not stop it by the GUI interface. Although my lab setup is not ideal and it might just due to the way I set it up, though I will still document how I resolved this where the same mechanism can be used to stop and restart any other service used by the vCenter Server Appliance. Below are the steps I have followed:

1- SSH to your VMware vCenter Server Appliance using the root account.

2- Execute the following command to see the status of all the service running in the vCenter Appliance:   chkconfig

The output of all services will look something like below:

localhost:~ # chkconfig
after.local               off
apache2                  off
arpd                         off
atftpd                       off
auditd                       on
autoyast                    off
chargen                      off
chargen-udp              off
cron                       on
daytime                    off
daytime-udp              off
dbus                     on
dcerpcd                  on
dhcp6r                   off
dhcp6s                   off
dhcpd                    off
discard                  off
discard-udp              off
earlysyslog              on
echo                     off
echo-udp                 off
eventlogd                on
fbset                     on
gpm                      off
haldaemon                on
haveged                  on
irq_balancer             on
kbd                      on
ldap                     on
lsassd                   off
lwiod                    on
mdadmd                   off
multipathd               off
netlogond                on
netstat                  off
network                  on
network-remotefs         on
nfs                      on
ntp                      off
pcscd                  off
powerd               off
random               on
raw                      off
rpasswdd            off
rpcbind                on
rpmconfigcheck           off
sendmail                       on
servers                           off
services                         off
setserial                        off
skeleton.compat          off
splash                            on
splash_early                on
sshd                               235
stunnel                         off
syslog                           on
syslog-collector         off
systat                          off
time                            off
time-udp                   off
uuidd                         off
vami-lighttp             235
vami-sfcb                 235
vaos                          235
vmware-inventoryservice  on
vmware-logbrowser        off
vmware-netdumper         off
vmware-rbd-watchdog      off
vmware-tools             on
vmware-vpostgres         on
vmware-vpxd              on
vsphere-client           on
xinetd                   off
ypbind                   off

3- Stop the required service in my case was vmware-vpxd using the following command: chkconfig service-name off (ex: chkconfig vmware-vpxd off)

4- carry out your changes

5- Start the service again using the following command: chkconfig service-name on (ex: chkconfig vmware-vpxd on)

I hope this help someone out there from being stuck with such issue… Read More

Sponsors