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

Multiple attempts to log in to an ESXi host with incorrect credentials might cause the hostd service to stop responding (CVE-2019-5528) (67920)

Last Updated: 2/28/2024Categories: TroubleshootingTotal Views: 65164Language:
Chinese (Simplified)JapaneseEnglish

16 like this article

Subscribe to get an email
newsletter with new updates

16 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

ESXi host is marked as Not responding in vCenter Server.

In the /var/log/vobd.log you see entries similar to:

2019-04-20T17:11:03.592Z: [UserLevelCorrelator] 459377077473us: [esx.audit.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after XXX failed login attempts.
2019-04-20T17:11:03.592Z: [GenericCorrelator] 459377077235us: [vob.user.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after XXX failed login attempts.

In the var/log/hostd.log you see entries similar to

2019-04-29T22:44:39.149Z error hostd[10280B70] [Originator@6876 sub=HTTP session map] Out of HTTP sessions: Limited to 500

In the var/log/vmkernel.log you see entries similar to

2019-04-29T16:25:01.263Z cpu3:905847)ALERT: hostd detected to be non-responsive
2019-04-29T18:45:01.697Z cpu30:915767)MemSched: 14635: Admission failure in path: hostd-probe/stats/probe/vmkbacktrace.915767/uw.915767
2019-04-29T18:45:01.698Z cpu13:915765)MemSched: 14635: Admission failure in path: hostd-probe/stats/vsish/vsish.915765/uw.915765
2019-04-29T19:20:01.780Z cpu18:918118)MemSched: 14635: Admission failure in path: hostd-probe/stats/vsish/vsish.918118/uw.918118
2019-04-29T19:20:01.781Z cpu18:918118)MemSched: 14635: Admission failure in path: hostd-probe/stats/vsish/vsish.918118/uw.918118
2019-04-29T19:20:01.782Z cpu30:918112)MemSched: 14635: Admission failure in path: hostd-probe/stats/probe/vmkbacktrace.918112/uw.918112
2019-04-29T19:55:01.868Z cpu18:920299)MemSched: 14635: Admission failure in path: hostd-probe/stats/probe/vmkbacktrace.920299/uw.920299

In  var/run/log/vmsyslogd-dropped.log, you see entries similar to

2019-04-23T10:42:45.992Z: <85>Apr 23 10:42:45 Hostd: pam_tally2(vmware-authd:auth): user root (0) tally 37, deny 5
2019-04-23T10:40:19.548Z: <85>Apr 23 10:40:19 Hostd: pam_tally2(vmware-authd:auth): user root (0) tally 34, deny 5

Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment

Resolution

To resolve this upgrade to ESXi 6.5 U3 and ESXi 6.7 U3.For details on this vulnerability including currently available remediation, please see VMSA-2019-0011 .

Workaround

To work around this issue, follow the steps given below:

Login to affected ESXi host via SSH.

Take a backup of config file by running below command:

cp /etc/vmware/hostd/config.xml /etc/vmware/hostd/config.xml-backup

Edit /etc/vmware/hostd/config.xml using vi editor

Add below line:

<ioTrackers> false </ioTrackers>

Example:
Before change
<config>
<!-- Host agent configuration file for ESX/ESXi -->
<!-- the version of this config file -->
<version>6.6.0.0</version>

After change
<config>
<!-- Host agent configuration file for ESX/ESXi -->
<ioTrackers> false </ioTrackers>
<!-- the version of this config file -->
<version>6.6.0.0</version>

Save and close the file.

Restart the hostd service by running the following command:

/etc/init.d/hostd restart

Related Information

For more information, see VMware ESXi (6.5, 6.7) Crashing During Nessus Scan.

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on
third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any
responsibility for the content of such sites.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
将 vCenter Server Appliance 从 6.5 升级到 6.7 后扫描更新遇到错误 (67771)

KB
•
PowerCLI connect-viserver を使用した vCenter Server へのスマート カード ログインに失敗する (67789)

KB
•
既存の分散スイッチの MTU 設定がクラスタの Quickstart で上書きされる (67888)

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

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant