Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

VCSA inodes getting full due to large files queued for mails /var/spool/clientmqueue (67636)

Last Updated: 2/28/2024Categories: TroubleshootingTotal Views: 8671Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

Unable to log into vCenter Web Client, /storage/core at high/100% utilization filled with core.sendmail.

Filesystem utilization:

root@xxxx [ /storage/core ]# df -h
Filesystem                                Size  Used Avail Use% Mounted on
devtmpfs                                  7.9G     0  7.9G   0% /dev
tmpfs                                     7.9G   20K  7.9G   1% /dev/shm
tmpfs                                     7.9G  692K  7.9G   1% /run
tmpfs                                     7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda3                                  11G  5.7G  4.5G  56% /
tmpfs                                     7.9G  1.6M  7.9G   1% /tmp
/dev/mapper/netdump_vg-netdump            985M  1.3M  932M   1% /storage/netdump
/dev/sda1                                 120M   27M   87M  24% /boot
/dev/mapper/dblog_vg-dblog                 15G  1.9G   12G  14% /storage/dblog
/dev/mapper/imagebuilder_vg-imagebuilder  9.8G   23M  9.2G   1% /storage/imagebuilder
/dev/mapper/autodeploy_vg-autodeploy      9.8G   33M  9.2G   1% /storage/autodeploy
/dev/mapper/updatemgr_vg-updatemgr         99G  780M   93G   1% /storage/updatemgr
/dev/mapper/log_vg-log                    9.8G  1.8G  7.5G  19% /storage/log
/dev/mapper/core_vg-core                   50G   49G    1G  98% /storage/core
/dev/mapper/db_vg-db                      9.8G  1.5G  7.8G  16% /storage/db
/dev/mapper/seat_vg-seat                   25G  8.8G   15G  38% /storage/seat

The below files are generated every 5 minutes under /storage/core:

-r-x------ 1 root      root       41M Feb  6 15:16 core.sendmail.26320
-r-x------ 1 root      root       41M Feb  6 15:21 core.sendmail.28221
-r-x------ 1 root      root       41M Feb  6 15:26 core.sendmail.30153
-r-x------ 1 root      root       41M Feb  6 15:31 core.sendmail.31610
-r-x------ 1 root      root       41M Feb  6 15:36 core.sendmail.33434
-r-x------ 1 root      root       41M Feb  6 15:41 core.sendmail.35229

You might see the below errors in /var/log/vmware/messages:

2019-02-06T15:40:50.234078+00:00 vcsa1 sendmail[4979]: x21B1Rqb037830: to=<[email-masked]>, delay=16:56:23, xdelay=00:00:00, mailer=esmtp, pri=120832, relay=yyyyyyy.com., dsn=4.0.0, stat=Deferred: Connection timed out with yyyyyyy.com.

Purpose

To fix the source of the problem which created a huge number of core.sendmail files in /storage/core and /var/spool/clientmqueue.

Cause

Open vCenter Web Client, verify Mail server settings:

Select vCenter > Configure > General > Edit > Mail.

The relay configured(relaymail.example,com) was not reachable as it was decommissioned.

As a result, a number of mails were queued as a SMTP relay was defined which VC was not able to communicate with.

Due to large queued mails, sendmail service started crashing and filling /storage/core.

Impact / Risks

vCenter vpxd service crashes and Web Client is inaccessible

Resolution

To stop the core.sendmail files from being generated, we need to stop the sendmail.service and reconfigure mail server relay.

Run below command to stop the service:

#systemctl stop sendmail.service

Run below command to delete files in /var/spool/clientmqueue:

#cd /var/spool/clientmqueue
#echo * | xargs -n 100 rm

or

#find /var/spool/clientmqueue/* -exec rm {} \;

Above commands clear the entire folder to show zero contents eventually:

# ls -ltrh /var/spool/clientmqueue/
total 0

Confirm that no new core files were being created:

-r-x------ 1 root      root       41M Feb  6 15:41 core.sendmail.35242
root@xxxx [ /storage/core ]# date
Wed Feb  6 16:12:33 UTC 2019

Clear out the old core files.

Final filesystem utilization:

========================
# df -h

Filesystem                                Size  Used Avail Use% Mounted on
devtmpfs                                  7.9G     0  7.9G   0% /dev
tmpfs                                     7.9G   20K  7.9G   1% /dev/shm
tmpfs                                     7.9G  692K  7.9G   1% /run
tmpfs                                     7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda3                                  11G  5.7G  4.5G  56% /
tmpfs                                     7.9G  1.6M  7.9G   1% /tmp
/dev/mapper/netdump_vg-netdump            985M  1.3M  932M   1% /storage/netdump
/dev/sda1                                 120M   27M   87M  24% /boot
/dev/mapper/dblog_vg-dblog                 15G  1.9G   12G  14% /storage/dblog
/dev/mapper/imagebuilder_vg-imagebuilder  9.8G   23M  9.2G   1% /storage/imagebuilder
/dev/mapper/autodeploy_vg-autodeploy      9.8G   33M  9.2G   1% /storage/autodeploy
/dev/mapper/updatemgr_vg-updatemgr         99G  780M   93G   1% /storage/updatemgr
/dev/mapper/log_vg-log                    9.8G  1.8G  7.5G  19% /storage/log
/dev/mapper/core_vg-core                   50G   53M   47G   1% /storage/core
/dev/mapper/db_vg-db                      9.8G  1.5G  7.8G  16% /storage/db
/dev/mapper/seat_vg-seat                   25G  8.8G   15G  38% /storage/seat

Workaround

If you are unable to pinpoint the source of the core.sendmail files, just stop the sendmail.service and clear out the core.sendmail files after clearing out the /var/spool/clientmqueue directory.

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
•
「ホストは VMware vSphere Update Manager のパッチ ストアからファイルをダウンロードできません。ネットワーク接続およびファイアウォールの設定を確認してください。詳細は esxupdate のログを確認してください。(Host cannot download files from VMware vSphere Update Manager patch store. Check the network connectivity and firewall setup, and (67705)

KB
•
“由于数据库可用空间不足而关闭 VC (Shutting down the VC as there is not enough free space for the Database)”错误 (67017)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.5.x

Take Our Survey

Support Assistant