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

SRM services stop due to unmanaged SRA log files (78289)

Last Updated: 4/15/2020Categories: How toTotal Views: 7367Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Site Recovery Manager (SRM) virtual appliance services unexpectedly stop

Log bundles cannot be generated.

The SRM appliance support partition is full.

Cause

The SRM appliance has two main disks: system and support.

The support disk contains an lvm ext4 file system.
The support partition stores the logs of VMware-related services.
The mount point of the partition is "/opt/vmware/support"

Storage Replication Adapter(SRA) logs don't currently have restriction for the size of the logs they produce. Having logs that are not managed will cause the support partition of the disk to fill up. This will result in the unplanned failure of the SRM server services due to the lack of any space available on disk for the log files.

Some SRAs lack appropriate safe guards on their log rotation method. This requires a manual clean up of the logs. There is no defined log naming convention or a limit on the number of logs each SRA may generate. In order to achieve clean up for the general case, assume the worst-case scenario, that each SRA logs to one log file and does not rotate it at all.

Resolution

This issue is fixed in: VMware Site Recovery Manager 8.2.0.1 |  13 AUG 2019 | Build 14338491 | Download

Workaround

A script has been developed which uses the preinstalled logrotate linux utility. This script is attached to this article.
The attached script will do the manual clean up and setup logrotate to monitor the files.
After log rotation, the old logs will be stored in an archive until the next log rotation. The archive will be stored under "/opt/vmware/support/logs/srm/" folder.

How to install the script

1. Download the script "clean-sras-logs.sh" in the "Attachments" section to the right.
2. As root user, place the script in "/opt/vmware/bin" with the name clean-sras-logs.sh

3. Set the script to be executable:

chmod 755 /opt/vmware/bin/clean-sras-logs.sh

4. Manually execute the script to rotate the log files inside the SRAs log partition.

/opt/vmware/bin/clean-sras-logs.sh

How to enable cron job to execute SRAs log rotation every day

1. As root user, create an empty file inside "/etc/cron.d/" with the filename sras.cron:

touch /etc/cron.d/sras.cron

2. Fill the content with the below text using a text editor :

0 0 * * * root /bin/bash /opt/vmware/bin/clean-sras-logs.sh

3. Restart the crond service:

systemctl restart crond

Related Information

To uninstall this workaround:

How to disable cron job to execute SRAs log rotation every day

1. As root user, remove the file /etc/cron.d/sras.cron:

cd /etc/cron.d
rm sras.cron

Restart the crond service:

systemctl restart crond

Remove the script

1. As root user, remove the file /opt/vmware/bin/clean-sras-logs.sh

cd /opt/vmware/bin
rm clean-sras-logs.sh

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

clean-sras-logs

Additional Resources

KB
•
更改 SRM 站点清单映射后，无法更新现有保护组（受保护的虚拟机）上的清单映射 (78232)

KB
•
Pulse IoT Center の提供終了 (EoA) に関する FAQ (78172)

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

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Site Recovery Manager

Related Versions:

VMware vCenter Site Recovery Manager 8.x

Take Our Survey

Support Assistant