Shulou(Shulou.com)06/02 Report--

Black data Network Lab October 2019

VMware recommended deployment using the Linux version of vCenter Server,VCSA has been widely used in enterprise production environments, especially after providing tools to migrate from the Windows version to the Linux version, the use of VCSA has reached a new level.

With the increase of usage time, many managers find problems. The VCSA virtual machine runs more and more slowly, some of them even hang up directly, or the service cannot be started after the virtual machine is started. The most common is the following error message:

Error message number one

Service Unavailable (Failed to connect to endpoint: [[N7Vmacore4Http16LocalServiceSpecE:0x00005649e04415e0] _ serverNamespace = / _ isRedirect = false _ pipeName = / var/run/vmware/vpxd-webserver-pipe)

Error message number two

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00005649e04415e0] _ serverNamespace = / ui action = Allow _ port = 5090)

Error message number three

HTTP Status 404-Not Found

Type Status Report

Message ProxyServlet: / ui/

Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

In fact, most of these problems are caused by insufficient disk space. VCSA uses the SUSE Linux system, and some managers who are familiar with Linux directly start to delete some files of the VCSA virtual machine to increase the use space. Remember: do not use traditional Linux thinking to manage VCSA, directly delete files may lead to VCSA completely unusable. For example, some logs are deleted, but the system cannot be rebuilt after some logs of VCSA are deleted, and if these log files are deleted, the VCSA service cannot be started.

The correct way to deal with it is to expand the capacity of VMDK. Logical volume management (LVM) is introduced into VCSA 6.0. VCSA 5.5,6.7 can support it well and dynamically increase the disk space of VCSA.

VCSA 6.x virtual machine disk space is most likely to run out of / storage/log (corresponding to VMDK 5) / storage/db (corresponding to VMDK 6), / storage/dblog (corresponding to VMDK 7)

Again: do not delete log files directly.

Correct handling:

1. Build a new VCSA 6.7 for operation, and the other 6.x versions are basically the same.

2. Check the VMDK information of VCSA 6.7 virtual machine. A total of 13 VMDK are used in version 6.7. The explanations of each VMDK refer to Table 1, Table 2 and Table 3.

Table 1. VCSA version 6.0 uses 11 VMDK

VMDK default size mount point interpretation

VMDK1 12 GB / (10 GB)

/ boot (132 MB)

SWAP (1 GB) stores the kernel image and the boot directory of the boot load configuration

VMDK2 1.3 GB / tmp temporary directory for storing generated temporary files or for use by services in vCenter Server

VMDK3 25 GB SWAP swap directory, which is used to swap to disk when the system runs out of memory

VMDK4 25 GB / storage/core core directory, which stores core dumps of VPXD processes in vCenter Server

VMDK5 10 GB / storage/log log directory, where vCenter Server stores all logs for the environment

VMDK6 10 GB / storage/db VMware Postgres database storage location

VMDK7 5 GB / storage/dblog VMware Postgres database logging location

VMDK8 10 GB / storage/seat VMware Postgres status, event, alarm, and task (SEAT) directory

VMDK9 1 GB / storage/netdump VMware Netdump Collector repository for storing ESXi dumps

VMDK10 10 GB / storage/autodeploy VMware Auto Deploy repository, which stores thinpackage for stateless boot of ESXi hosts

VMDK11 5 GB / storage/invsvc VMware Inventory Service directory, where xDB, Inventory Service bootstrapper configuration files, and tomcat configuration files are located

Table 2 VCSA version 6.5 uses 12 VMDK

VMDK default size mount point interpretation

VMDK1 12GB / (10GB)

/ boot (132MB)

SWAP (1GB) the storage directory for the kernel image and boot loader configuration.

Directory where VMDK2 1.8GB / tmp is used to store temporary files generated or used by the vCenter Server service

Directory used when VMDK3 25GB SWAP system memory is insufficient to swap to disk

VMDK4 25GB / storage/core directory where core dumps from vCenter Server's VPXD processes are stored

Directory of all logs in the VMDK5 10GB / storage/log vCenter Server and Platform Services Controller storage environment

VMDK6 10GB / storage/db VMware Postgres database storage location

VMDK7 5GB / storage/dblog VMware Postgres database logging location

VMDK8 10GB / storage/seat VMware Postgres statistics, events, alerts and tasks (SEAT) directory

VMDK9 1GB / storage/netdump stores the VMware Netdump collector repository for ESXi dumps

The VMDK10 10GB / storage/autodeploy VMware Auto Deploy repository, which stores thin packages for stateless startup of ESXi hosts

VMDK11 10GB / storage/imagebuilder VMware Image Builder repository for storing vSphere image configuration files, software repositories and VIB packages, such as driver VIB and update VIB.

VMDK12 100GB / storage/updatemgr VMware Update Manager repository to store patches and updates for virtual machines and ESXi hosts

Table 3. VCSA version 6.0 uses 13 VMDK

VMDK default size mount point interpretation

VMDK1 12GB / (10GB)

/ boot (132MB)

SWAP (1GB) the storage directory for the kernel image and boot loader configuration.

Directory where VMDK2 1.8GB / tmp is used to store temporary files generated or used by the vCenter Server service

Directory used when VMDK3 25GB SWAP system memory is insufficient to swap to disk

VMDK4 25GB / storage/core directory where core dumps from vCenter Server's VPXD processes are stored

Directory of all logs in the VMDK5 10GB / storage/log vCenter Server and Platform Services Controller storage environment

VMDK6 10GB / storage/db VMware Postgres database storage location

VMDK7 5GB / storage/dblog VMware Postgres database logging location

VMDK8 10GB / storage/seat VMware Postgres statistics, events, alerts and tasks (SEAT) directory

VMDK9 1GB / storage/netdump stores the VMware Netdump collector repository for ESXi dumps

The VMDK10 10GB / storage/autodeploy VMware Auto Deploy repository, which stores thin packages for stateless startup of ESXi hosts

VMDK11 10GB / storage/imagebuilder VMware Image Builder repository for storing vSphere image configuration files, software repositories and VIB packages, such as driver VIB and update VIB.

VMDK12 100GB / storage/updatemgr VMware Update Manager repository to store patches and updates for virtual machines and ESXi hosts

Prepaid log (WAL) location of the VMDK13 50GB / storage/archive VMware Postgres database

Step 3, log in to the VCSA 6.7VM and use the command df-Th to view the space size.

Step 4, check the corresponding VMDK capacity information.

Step 5, increase the VMDK capacity, each by 10 gigabytes.

Step 6, after increasing the virtual disk space, directly use the command to automatically expand all the logical volumes that have added physical volumes vpxd_servicecfg storage lvm autogrow is not wrong, it is a command

Step 7, the expansion is successful.

Step 8, you can also expand the capacity by using the command / usr/lib/applmgmt/support/scripts/autogrow.sh.

Step 9, add the effect after 50g.

Step 10, use the command to start the service, and all services start normally.

Step 11, use a browser to access VCSA 6.7 and return to normal.

Finally, one more warning: do not use traditional Linux thinking to manage VCSA, directly deleting files may cause VCSA to be completely unusable.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.