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

Aria Operations for logs /storage/core partition is 100% on nodes causing cassandra DB failing to start (52873)

Last Updated: 4/1/2024Categories: TroubleshootingTotal Views: 2380Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

*Aria Operations for logs deletes old buckets when available space on the /storage/core partition is less than 3%. Deletion is done using a FIFO model. This partition should never reach 100% because Aria Operations for logs manages that partition.
*But in some cases if the storage/core has already reached 100% will take the node offline.
When you check the file system free space, you see content similar to:

Filesystem Size Used Avail Use% Mounted on
/dev/sda3 16G 2.4G 13G 16% /
udev 7.9G 112K 7.9G 1% /dev
tmpfs 7.9G 648K 7.9G 1% /dev/shm
/dev/sda1 128M 38M 84M 31% /boot
/dev/mapper/data-var 20G 7.3G 12G 39% /storage/var
/dev/mapper/data-core 483G 483G 0 100% /storage/core

Cause

* See if the nfs archive is configured properly and working fine with below pointers.
1. NFS server reachable by Log Insight?
2. Is there sufficient space available?
3. Have permissions been properly configured to allow Log Insight to write and access the NFS server?
4. Is there sufficient end-to-end NFS throughput between the Log Insight appliance and the NFS server?

* Nfs is configured properly but that isn't enough to say that we will not face to any problem with archiving because if somehow nfs will become unavailable(even more than 10 minutes) or the archive storage will become full the same issue will come on. In general, LI grinding to a halt is documented and expected behavior if NFS is not maintained.

Impact / Risks

If storage/core has already reached 100% will take the node offline.

Resolution

Important: Before starting with below steps, ensure to validate the stored buckets

Steps:
1. Run the below command on both affected node.
Note: This might take a while for the command to finish running. The results of the command will be saved in the /tmp/validate.txt file:
cd /usr/lib/loginsight/application/sbin ./validate-bucket --validate > /tmp/validate.txt
2. Once the validate is completed refer the /tmp/validate.txt and make sure no corrupted buckets. If any follow Phase 1 of the action plan, if there are no corrupted buckets follow Phase 2.

Phase 1:

1. stop log insight
/etc/init.d/loginsight stop
2. list the buckets, Look for the guid of the old buckets by timestamp
/usr/lib/loginsight/application/sbin/bucket-index show
3. Run the following command to delete a bucket
/usr/lib/loginsight/application/sbin/bucket-index delete [BUCKET-ID]
4. start loginsight
/etc/init.d/loginsight start

The "./validate-bucket --validate" would reveal if there are any corrupted buckets remove those instead of looking for the oldest buckets.

Phase 2:

1. Deploy a new Aria Operations for logs node following the steps outlined in below document.
https://docs.vmware.com/en/VMware-Aria-Operations-for-Logs/8.14/Administering-Operations-for-Logs/GUID-F73595DC-1511-4A19-9AE4-02C8FEDF5CF5.html

2. Once you have the new Aria Operations for logs node deployed, the next is to import the buckets from old node into the new one without losing any data. Steps below.

1)ssh to Log Insight you want to import events from and go to “/storage/core/loginsight/cidata/store” – this is where the data buckets live.
2)run “service loginsight stop” to stop Log Insight. Ensure the service has stopped by running “service loginsight status”.
3)copy the buckets you want to import to target Log Insight - the destination directory must be the same; i.e. “/storage/core/loginsight/cidata/store”
4)ssh to Log Insight that will be importing the events and stop the service by running “service loginsight stop”. Ensure the service has stopped by running “service loginsight status”.
5)run “/usr/lib/loginsight/application/sbin/bucket-index add <bucket_id>”
6)Repeat the step above for all the copied buckets.

3. Ensure you complete the steps for both the current worker nodes to new nodes.
4. Once the above is completed. Join the 2 new nodes to the existing Deployment following the below document
https://docs.vmware.com/en/VMware-Aria-Operations-for-Logs/8.14/Administering-Operations-for-Logs/GUID-B793B5C7-C856-4324-8202-EBB35265BA7B.html

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
同一 vCenter 的不同 vmkernel 中可能会显示重复的 MAC 地址 (52035)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Log Insight

VMware Aria Operations for Logs

VMware Aria Operations

Related Versions:

VMware vRealize Log Insight 4.x

VMware Aria Operations for Logs 8.14.x

VMware Aria Operations 8.16

VMware Aria Operations 8.12.x

Take Our Survey

Support Assistant