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

"stats-monitor service" service not starting after VCSA reboot (55640)

Last Updated: 2/22/2024Categories: TroubleshootingTotal Views: 27083Language:
English

13 like this article

Subscribe to get an email
newsletter with new updates

13 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

stats-monitor service not starting after reboot of VCSA

Manual start of service is working

CPU, Memory, and Database does not have any graphs

Manual start of statsmonitor is working fine

In the StatsMonitor.log (latest-log) file, located in located in the directory /var/log/vmware/applmgmt, you see entries similar to

2017-11-07T12:20:38.485+01:00 info StatsMonitor[7F2A12D51700] [Originator@6876 sub=ThreadPool] Entering worker thread loop
2017-11-07T12:20:38.485+01:00 info StatsMonitor[7F2A12D10700] [Originator@6876 sub=ThreadPool] Thread enlisted
2017-11-07T12:20:38.485+01:00 info StatsMonitor[7F2A12D10700] [Originator@6876 sub=ThreadPool] Entering IO thread loop
2017-11-07T12:20:38.485+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=ThreadPool] Thread pool fair initial threads spawned. IO: 2, Min workers: 4, Max workers: 13, Reservation ratio: 9
2017-11-07T12:20:38.485+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=ThreadPool] Thread enlisted
2017-11-07T12:20:38.485+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=Default] Syscommand enabled: true
2017-11-07T12:20:38.485+01:00 info StatsMonitor[7F2A12CCF700] [Originator@6876 sub=ThreadPool] Thread enlisted
2017-11-07T12:20:38.485+01:00 info StatsMonitor[7F2A12CCF700] [Originator@6876 sub=ThreadPool] Entering IO thread loop
2017-11-07T12:20:38.485+01:00 info StatsMonitor[7F2A12C8E700] [Originator@6876 sub=ThreadPool] Thread enlisted
2017-11-07T12:20:38.485+01:00 info StatsMonitor[7F2A12C8E700] [Originator@6876 sub=ThreadPool] Entering fair thread loop
2017-11-07T12:20:38.599+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=Default] ReaperManager Initialized
2017-11-07T12:20:38.599+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=StatsMonitor] Setting up signal handlers
2017-11-07T12:20:38.599+01:00 error StatsMonitor[7F2A12E15780] [Originator@6876 sub=StatsMonitor] Failed to register handler for signal: 0
2017-11-07T12:20:38.599+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=StatsMonitor] Initializing
2017-11-07T12:20:38.600+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=LinuxStatsProvider(738847377312)] Registered 162 stats (sources:114, derivatives:48)
2017-11-07T12:20:38.601+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=StatsMonitor] Found 12 file systems and 7 dirs in config for monitoring.
2017-11-07T12:20:38.601+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=LinuxStorageStatsProvider(738847702096)] Registered 3 stats
2017-11-07T12:20:38.601+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=StatsMonitor] SqliteStorageEngine using SQLite version: 3.17.0
2017-11-07T12:24:35.215+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=StatsMonitor] Received signal 15
2017-11-07T12:24:35.215+01:00 info StatsMonitor[7F2A12E15780] [Originator@6876 sub=StatsMonitor] Shutting down

Cause

This issue occurs due to start up timeout for StatsMonitor Service. The startup DB health check completed in a given time, occasionally, the IO might be too slow to start the service.

Resolution

This issue is resolved in vCenter Server 6.5 U3f and vCenter Server 6.7 U3

You can download newer versions from here if needed: Download VMware vSphere

You can download product patches from here if needed: VMware Product Patches

Workaround

To workaround this issue, take a snapshot of VCSA without memory:

Take SSH to VCSA using root login.

Modify statsmonitor service config for vMon to set higher startup timeout by running this command:

sed -i '/StartTimeout/d' /etc/vmware/vmware-vmon/svcCfgfiles/statsmonitor.json
sed -i '/ApiHealthFile/a "StartTimeout": 600,' /etc/vmware/vmware-vmon/svcCfgfiles/statsmonitor.json

Run the kill -HUP $(cat /var/run/vmon.pid) command.

Stop and start statsmonitor service explicitly by running this command:

/usr/lib/vmware-vmon/vmon-cli -k statsmonitor

/usr/lib/vmware-vmon/vmon-cli -i statsmonitor

reboot the VCSA and check after 10-15 mins and the Statsmonitor Service should start up automatically.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
VMware End Of Availability of Perpetual Licensing and SaaS Services (96168)

KB
•
vSphere 用 Intel プロセッサにおける「L1 Terminal Fault」(L1TF - VMM) 投機的実行の脆弱性に対する VMware の対応 CVE-2018-3646 (55806)

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 vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

Take Our Survey

Support Assistant