vcenter-appliance-vcsa-root-partition-full

What a mess! VCSA cannot be updated anymore or is stuck because of a full root Partition.

Luckily there are straightforward procedures to investigate what files are filling the root partition and how to get rid of them.

Typical symptoms?

  • ISO staging of the update fails
  • vCSA update fails at step #/#
  • some vCSA services cannot be started

Filesystem check

Log into your VCSA console, enable the shell and open the shell.

shell.set –enabled true
shell
df -h

VCSA root partition full

Ignore the Use % number in the screenshot above, as the partition has been cleaned up already. But any number higher than 95% will stop your update procedure.

When using Performance Analyzer we have a special Highlights dashboard for VM partitions, that can be used to check the partition utilization as well.

Performance Analyzer / check vCSA partition

Please download the dashboard here, to import it into Performance Analyzer: DownloadMore information at http://manual.opvizor.com

How to resize the partition

If you don’t want to make your hands dirty and clean up the partition, you can resize the related virtual disk and partition by following this KB article: 

https://kb.vmware.com/s/article/2126276

The big issue here is, that you just postpone the file cleanup until the partition fills up again.

How to clean up the partition

audit.log

In case the audit.log is filling the partition, the task is quite simple and described in the following KB article: 

https://kb.vmware.com/s/article/2149278

  1. cd /var/log/audit
  2. ls -lh
  3. rm -rf audit.log

Check the KB article for all steps to make sure the audit.log is not filling up again.

mqueue

Another possible reason for a filled up partition are files in /var/spool/mqueue – a less documented situation.

In general, you can use the following command to find the largest directories checking the current and the first subdirectory: df -h -d1

  1. df -h -d1 /var
  2. if it’s /var/log that is very big, check the audit.log solution
  3. if it’s /var/spool, continue here
  4. find /var/spool/mqueue -name "*" -delete

The reason to use find and delete instead of rm is, that most of the time /var/spool/mqueue contains to many files to be handled by rm.

Check the partitions again using df -h and restart the appliance if needed.

Btw. You should consider creating a snapshot before deleting any files

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.