Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Cloud Foundation Workload Domain expansion fails at the Task "Configure new vCenters and ESXi hosts from workload domains in vRLI" (55834)

Last Updated: 4/5/2019Categories: InformationalTotal Views: 3146Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Workload Domain expansion fails at the task "Configure new vCenters and ESXi hosts from workload domains in vRLI".

LogInsight VMs are not allowing logins, either by SSH (root) or any user through the UI (including admin).

The root ( / ) filesystem is filling up or full (100% Use) on LogInsight VMs.

Installation of Content Packs in Log Insight fails.

Cause

The Log Insight log gathering function of the sos utility (on the SDDC Manager Controller VM) might not complete successfully leaving behind partial log bundles under /tmp/repo folder on the Log Insight VM.

Resolution

This issue is resolved in VCF 2.2.1 and later.

Workaround

You can workaround this issue using the following steps:

Attempt to log in to the affected Log Insight node as the root user (ssh or console). If you are able to log in, proceed to step 2.  Otherwise see the procedure for booting off a Linux ISO in the Related Information section.

Issue the following command to remove the /tmp/repo directory:

rm -rf /tmp/repo

Issue the  df -h  command to validate that the root (/) file system is no longer full.

Repeat steps 1-3 for any other affected Log Insight nodes.

Related Information

Note: If you are unable to log in as the root user (from Workaround step 1) and are certain you are using the correct root password, the root ( / ) filesystem is full on the affected Log Insight node.  You will therefore need to clean out the root ( / ) file system by booting from another Linux ISO and mounting the /dev/sda3 ( / ) filesystem from the booted ISO using the following procedure:

Acquire a Linux ISO to mount to the affected Log Insight node (VM).  In this example, we will be using an Arch Linux ISO as it is less than 1 GB (~600MB) in size.

Shut down the VM and edit the properties to mount the ISO you have uploaded to a local datastore accessible by the Log Insight VM(s).  Be sure to set the boot to BIOS option under "Boot Options" in order to reconfigure the BIOS to boot the CDROM first (instead of the First HDD).  This will make it easier to boot from the ISO as the VM BIOS screen/POST operation is incredibly quick.

Boot the affected Log Insight VM into the shell provided by the Linux ISO.   For Arch Linux, this is option 3 and will automatically start as the root user ( #  prompt).  If you are using a different distribution of Linux, you may need to become root with the command sudo su - before proceeding.

Issue the  fdisk -l  command to list all the available partitions, make sure /dev/sda3 is listed.  That will be the root ( / ) filesystem of the Log Insight VM.

Mount the root ( / ) partition using the following command:  mount /dev/sda3 /mnt

Issue the command df -h to verify /mnt  (/dev/sda3) is at 100% utilization (Note: the ISO you have booted off of will also show 100%, you want to pay attention to the /dev/sda partitions).

Change to the tmp filesystem on /dev/sda3 by issuing the command: cd /mnt/tmp

Issue the command: rm -rf repo  to remove the repo directory and all of it's contents.

Verify the filesystem has has been freed up sufficiently by issuing the df -h command again.  The /mnt (/dev/sda3) partition should no longer be at 100% (it should be substantially less).  Change back to the ISO root directory and unmount the /mnt (/dev/sda3) partition with the commands:

cd /
umount /mnt

Shut down the Log Insight VM and detach the ISO.  Follow the same process as in step 2 to change the boot order back to the original settings (HDD First).

Boot the Lo gInsight VM and verify functionality by logging in as root via ssh.

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Log Insight

VMware Cloud Foundation

Related Versions:

VMware vRealize Log Insight 4.3.x

VMware Cloud Foundation 2.3.x

VMware Cloud Foundation 2.2.x

Take Our Survey

Support Assistant