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

Agentless Management Service (AMS) version 11.4.x causing a full ams-bbUsg.txt and host not responding (78595)

Last Updated: 2/22/2021Categories: TroubleshootingTotal Views: 52291Language:
Chinese (Simplified)JapaneseEnglish

20 like this article

Subscribe to get an email
newsletter with new updates

20 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

An ESXi host upgrade fails due to /tmp being full.

An ESXi host is not responding in the vCenter Server inventory.

The ams-bbUsg.txt file consumes a large amount of /tmp

In the vobd.log, you see similar to:

2020-04-10T05:25:45.458Z: [VisorfsCorrelator] 9661642434308us: [vob.visorfs.ramdisk.full] Cannot extend visorfs file /tmp/bbFile2.txt because its ramdisk (tmp) is full.
2020-04-10T05:25:45.503Z: [VisorfsCorrelator] 9661642479481us: [vob.visorfs.ramdisk.full] Cannot extend visorfs file /tmp/bbFile2.txt because its ramdisk (tmp) is full.
2020-04-10T05:25:45.504Z: [VisorfsCorrelator] 9661642480515us: [vob.visorfs.ramdisk.full] Cannot extend visorfs file /tmp/ams-bbUsg.txt because its ramdisk (tmp) is full.
2020-04-10T05:26:14.662Z: [VisorfsCorrelator] 9661671637154us: [vob.visorfs.ramdisk.full] Cannot extend visorfs file /tmp/ams-sysmod.txt because its ramdisk (tmp) is full.
2020-04-10T05:26:14.662Z: [VisorfsCorrelator] 9661816145006us: [esx.problem.visorfs.ramdisk.full] The ramdisk 'tmp' is full.  As a result, the file /tmp/ams-sysmod.txt could not be written.

In the vmkernel.log, you see similar to:

2020-04-10T04:57:46.064Z cpu0:246728737)WARNING: VisorFSRam: 206: Cannot extend visorfs file /tmp/bbFile2.txt because its ramdisk (tmp) is full.
2020-04-10T04:57:46.065Z cpu2:2100680)MemSchedAdmit: 470: Admission failure in path: tmp/tmp
2020-04-10T04:57:46.065Z cpu2:2100680)MemSchedAdmit: 477: tmp (2409) extraMin/extraFromParent: 1/1, tmp (2408) childEmin/eMinLimit: 65536/65536
2020-04-10T04:57:46.065Z cpu2:2100680)WARNING: VisorFSRam: 206: Cannot extend visorfs file /tmp/ams-bbUsg.txt because its ramdisk (tmp) is full.
2020-04-10T04:58:24.288Z cpu20:2098113)ScsiDeviceIO: 3068: Cmd(0x45a29fb873c0) 0x1a, CmdSN 0x30e8a1 from world 0 to dev "mpx.vmhba1:C2:T1088:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2020-04-10T04:58:31.712Z cpu6:246732134)MemSchedAdmit: 470: Admission failure in path: tmp/tmp
2020-04-10T04:58:31.712Z cpu6:246732134)MemSchedAdmit: 477: tmp (2409) extraMin/extraFromParent: 1/1, tmp (2408) childEmin/eMinLimit: 65536/65536

vMotion of a virtual machine fails

You see an error similar to:

General System Error Occurred.

Note: A similar issue can occur if the mili2d.log fills up ramdisk at /var/, see The ramdisk '/var' is full. As a result, the file /var/log/EMU/mili/mili2d.log could not be written. (65193)

Cause

HPE servers running VMware ESXi version 6.X with Agentless Management Service (AMS) version 11.4.x will enter not responding state because AMS data fills up /tmp.

Impact / Risks

None of the VC features will be applicable if the host is in not responding state.

VM backup will get impacted.

Upgrade via VUM/CLI will fail.

Resolution

A resolution is available at https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-a00073323en_us

Workaround

To work around this issue, clear the ams-bbUsg.txt file contents:

Connect to affected host through SSH session.

List the files in /tmp using du -sh *

[root@VMwareESXi-2:/tmp] du -sh *
255.6M  ams-bbUsg.txt
4.0K    ams-ent.txt
4.0K    ams-fc.txt
4.0K    ams-fsys.txt
64.0K   ams-hrswrun.txt
4.0K    ams-ip.txt
0       ams-ipv4.txt

Empty the ams-bbUsg.txt file with this command: echo > ams-bbUsg.txt

Related Information

VMware Skyline Health Diagnostics for vSphere - FAQ
https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_a38161c3e8674777a8c664e05a#tab-history

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
vCenter 6.5/6.7 から 7.0 へのアップグレード時に、「vCenter Server Appliance FQDN が VMware Endpoint Certificate Store の証明書に一致しない」(vCenter Server Appliance FQDN does not match the certificate in VMware Endpoint Certificate Store) というエラーが表示される (78657)

KB
•
VUM 扫描失败：VMware vSphere Update Manager 存在未知错误。请查看事件和日志文件 (76357)

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 vSphere ESXi

VMware vSphere

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere 6.5.x

Take Our Survey

Support Assistant