Black lab data network in October 2019
After deploying VMware recommend using the Linux version of vCenter Server, VCSA has been widely used in a production environment, especially for the migration from Windows to Linux version version of the tool, use VCSA reached a new height.
With the increased use of time, many managers find problems, VCSA virtual machine run more slowly, and some even directly linked to death, or virtual machine fails to start after starting the service, the most common error is the following tips:
报错提示一
503 Service Unavailable (Failed to connect to endpoint: [[N7Vmacore4Http16LocalServiceSpecE:0x00005649e04415e0] _serverNamespace = / _isRedirect = false _pipeName =/var/run/vmware/vpxd-webserver-pipe)
报错提示二
503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00005649e04415e0] _serverNamespace = /ui action = Allow _port = 5090)
报错提示三
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 cause these problems in most cases occurs due to insufficient disk space cause problems, VCSA use SUSE Linux system, some of the executives familiar with Linux on direct hands-delete some files VCSA virtual machines to increase the use of space, remember remember: do not use traditional Linux thinking to manage VCSA, delete file may lead to VCSA completely unusable. Such as deleting a portion of the log, but after some log VCSA delete system can not be rebuilt, and these log files are deleted if it will lead to VCSA service can not start.
The correct approach is VMDK for expansion operations, VCSA 6.0 introduced the Logical Volume Manager (LVM), VCSA 5.5 and 6.7 are well supported, dynamic growth VCSA disk space.
VCSA 6.X most likely to lack of space is the virtual machine disk / storage / log (corresponding to the VMDK 5) / storage / db (corresponding to the VMDK 6), / storage / dblog ( corresponding to the VMDK 7)
Again: Do not delete the log files.
Proper treatment:
1, a new operating VCSA 6.7, substantially the same 6.X other editions.
2, see VCSA 6.7 VMDK virtual machine virtual machine information, version 6.7 uses a total of 13 VMDK, each VMDK explained with reference to Tables I, II, III explained.
表一 VCSA 6.0版本使用11个VMDK
VMDK 默认大小 挂载点 解释
VMDK1 12 GB / (10 GB)
/boot (132 MB)
SWAP (1 GB) 存储着内核映像和引导加载配置的引导目录
VMDK2 1.3 GB /tmp 临时目录，用于存储生成的临时文件或供 vCenter Server 中的服务使用
VMDK3 25 GB SWAP 交换目录，系统内存不足时使用此目录交换到磁盘
VMDK4 25 GB /storage/core 核心目录，存储 vCenter Server 中 VPXD 进程的核心转储
VMDK5 10 GB /storage/log 日志目录，vCenter Server 在此目录中存储环境的所有日志
VMDK6 10 GB /storage/db VMware Postgres 数据库存储位置
VMDK7 5 GB /storage/dblog VMware Postgres 数据库日志记录位置
VMDK8 10 GB /storage/seat VMware Postgres 的状态、事件、告警和任务 (SEAT) 目录
VMDK9 1 GB /storage/netdump VMware Netdump Collector 存储库，用于存储 ESXi 转储
VMDK10 10 GB /storage/autodeploy VMware Auto Deploy 存储库，存储用于 ESXi 主机无状态引导的 thinpackage
VMDK11 5 GB /storage/invsvc VMware Inventory Service 目录，xDB、Inventory Service 引导程序配置文件和 tomcat 配置文件位于此目录中
表二 VCSA 6.5版本使用12个VMDK
VMDK 默认大小 挂载点 解释
VMDK1 12GB / (10GB)
/boot (132MB)
SWAP (1GB) 内核映像和引导加载程序配置的存储目录。
VMDK2 1.8GB /tmp 用于存储vCenter Server服务生成或使用的临时文件的目录
VMDK3 25GB SWAP 系统内存不足以交换到磁盘时使用的目录
VMDK4 25GB /storage/core 存储来自vCenter Server的VPXD 进程的核心转储的目录
VMDK5 10GB /storage/log vCenter Server和Platform Services Controller存储环境所有日志的目录
VMDK6 10GB /storage/db VMware Postgres数据库存储位置
VMDK7 5GB /storage/dblog VMware Postgres数据库日志记录位置
VMDK8 10GB /storage/seat VMware Postgres的统计，事件，警报和任务（SEAT）目录
VMDK9 1GB /storage/netdump 存储ESXi转储的VMware Netdump收集器存储库
VMDK10 10GB /storage/autodeploy VMware Auto Deploy存储库，该存储库存储用于无状态启动ESXi主机的瘦程序包
VMDK11 10GB /storage/imagebuilder VMware Image Builder存储库，用于存储vSphere映像配置文件，软件仓库和VIB软件包，例如驱动程序VIB和更新VIB。
VMDK12 100GB /storage/updatemgr VMware Update Manager存储库，用于存储虚拟机和ESXi主机的修补程序和更新
表三 VCSA 6.0版本使用13个VMDK
VMDK 默认大小 挂载点 解释
VMDK1 12GB / (10GB)
/boot (132MB)
SWAP (1GB) 内核映像和引导加载程序配置的存储目录。
VMDK2 1.8GB /tmp 用于存储vCenter Server服务生成或使用的临时文件的目录
VMDK3 25GB SWAP 系统内存不足以交换到磁盘时使用的目录
VMDK4 25GB /storage/core 存储来自vCenter Server的VPXD 进程的核心转储的目录
VMDK5 10GB /storage/log vCenter Server和Platform Services Controller存储环境所有日志的目录
VMDK6 10GB /storage/db VMware Postgres数据库存储位置
VMDK7 5GB /storage/dblog VMware Postgres数据库日志记录位置
VMDK8 10GB /storage/seat VMware Postgres的统计，事件，警报和任务（SEAT）目录
VMDK9 1GB /storage/netdump 存储ESXi转储的VMware Netdump收集器存储库
VMDK10 10GB /storage/autodeploy VMware Auto Deploy存储库，该存储库存储用于无状态启动ESXi主机的瘦程序包
VMDK11 10GB / storage / imagebuilder VMware Image Builder repository for storing image profile vSphere, depots and VIB packages, such as drivers and updates VIB VIB.
VMDK12 100GB / storage / updatemgr VMware Update Manager repository for storing virtual machine and ESXi host patches and updates
VMDK13 50GB / storage / write-ahead log archive VMware Postgres database (WAL) position
Step 3 Log VCSA 6.7 virtual machine, use the command df -Th viewing space.
Step 4, see the corresponding VMDK capacity information.
Step 5, increase the capacity VMDK, each additional space 10G.
Step 6, after the increase virtual disk space, use the direct command automatically expand all increased physical volumes of the logical volume vpxd_servicecfg storage lvm autogrow is not wrong, is a command
Step 7, expansion and success.
Step 8, using the command /usr/lib/applmgmt/support/scripts/autogrow.sh also be expansion.
Step 9, after the effect of increasing 50G.
Step 10, use the command to start the service, all the services all started normally.
Step 11, using a browser to access VCSA 6.7, back to normal.
Finally, a reminder: do not use traditional thinking to manage Linux VCSA, delete file may lead to VCSA completely unusable.