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

vIDM appliance has no space left on device /db for audit data (55417)

Last Updated: 4/22/2022Categories: Best PracticesTotal Views: 9481Language:
English

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Symptoms

This article provides steps to add space in the vIDM appliance adding config to limit audit data.

vIDM appliance /db file system is almost full, for example usage exceeds about 90% and more.

You will see these errors:

check /db file system usage by df command as follows
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/mapper/db_vg-db 10076 8318 1246 87% /db

Getting vIDM log-bundle fails with the error: No space left on device.

Cause

vIDM appliance uses device /db for Elasticsearch, RabbiMQ and internal DB PostgreSQL.
/db
|- data
|- elasticsearch
|- log
|- lost+found
|- temp
A large number of audit data for Elasticsearch uses almost all space on device /db file system.
As the default settings vIDM appliance keeps audit data forever, the vIDM file system will eventually fill up.

Resolution

To resolve this issue, add a policy to limit audit data in the /usr/local/horizon/conf/runtime-config.properties file:

Login to the vIDM appliance.

Edit the /usr/local/horizon/conf/runtime-config.properties file.

vi /usr/local/horizon/conf/runtime-config.properties

Add these two rows to the file:

analytics.deleteOldData=true -----> The default value is false.
analytics.maxQueryDays=90 -----> The default value is 90, which indicates the number of days to keep the audit date. It is recommended to be 90 days to get 12 week statistics.

Reboot the vIDM appliance to reflect the new setting.

Remove the audit data manually which has already expired more than 90 days using the curl command for cleanup.You can use wildcards to delete the audit data:

Examples:
curl -XDELETE http://localhost:9200/v3_2016*
Explanation : Deletes everything from 2016.
curl -XDELETE http://localhost:9200/v3_2016-12*
Explanation:Deletes everything from December 2016.

Backup : If the curl command fails, run the following commands:

rabbitmqctl list_queues | grep analytics.null
Explanation : Lists the RabbitMQ queue

rabbitmqctl purge_queue -.analytics.null
Explanation : Purges the queue
For versions vIDM 3.3.4 and higher, Workspace ONE Access 20.10 and higher, you will need to do the following workaround as the command above will fail on the new Photon releases.

wget 'https://raw.githubusercontent.com/rabbitmq/rabbitmq-management/v3.7.20/bin/rabbitmqadmin'
chmod +x rabbitmqadmin
sed -i 's|#!/usr/bin/env python|#!/usr/bin/env python3|' rabbitmqadmin
mv rabbitmqadmin /usr/sbin/
rabbitmqadmin -q list queues | grep analytics
rabbitmqadmin purge queue name=-.analytics.127.0.0.1

Note:

* in the file name is wildcard.

Do not use rm commands to remove the audit data unless all nodes are stopped.

Related Information

There is also a related KB on increasing the size of the /db file system.
* VMware Identity Manager Linux appliance disk containing Postgres database, analytics data, and support log bundle (/db) is full (2082650)
----------------------------------------
rm command is distributed, replicated data store, so removing the files when elasticsearch is running will cause problems. It is recommended to use the “curl” command to perform the removal safely.

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
•
Horizon Agent、Remote Experience 及び Persona Management でサポートされるゲスト OS (2150295)

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 Workspace ONE Access

VMware Identity Manager

VMware Aria Automation

Related Versions:

VMware Identity Manager 3.3.x

VMware Identity Manager 2.x

Take Our Survey

Support Assistant