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

Configuration file has unexpected changes and during backup proxy virtual machine terminates (56453)

Last Updated: 2/23/2024Categories: TroubleshootingTotal Views: 28436Language:
English

12 like this article

Subscribe to get an email
newsletter with new updates

12 people found this helpful Please provide article feedback:

Symptoms

Backup proxy goes to invalid state during backup.

In the hostd.log file, you see entries similar to:

2018-06-08T10:33:14.150Z info hostd[15A03B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/580692bf-a861cb5a-1083-e83935c5e190/smf-xxxproxy-007/smf-xxxproxy-007.vmx opID=5953cf5e-3-a90a user=vpxuser:ADMIN\nwadmin_svc] State Transition (VM_STATE_ON -> VM_STATE_RECONFIGURING)
...
2018-06-08T10:33:14.167Z error hostd[15640B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/580692bf-a861cb5a-1083-e83935c5e190/smf-xxxproxy-007/smf-xxxproxy-007.vmx opID=5953cf5e-3-a90a user=vpxuser:ADMIN\nwadmin_svc] Could not apply pre-reconfigure domain changes: Failed to add file policies to domain :171: world ID :0:Cannot allocate memory
...
2018-06-08T10:33:14.826Z info hostd[15640B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/580692bf-a861cb5a-1083-e83935c5e190/smf-xxxproxy-007/smf-xxxproxy-007.vmx opID=5953cf5e-3-a90a user=vpxuser:ADMIN\nwadmin_svc] State Transition (VM_STATE_RECONFIGURING -> VM_STATE_ON)
...
2018-06-08T10:35:53.120Z error hostd[15A44B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/580692bf-a861cb5a-1083-e83935c5e190/smf-xxxproxy-007/smf-xxxproxy-007.vmx] Expected permission (3) for /vmfs/volumes/5ac38771-f9105baf-f368-c25883f002d0/smf-app-comm-dev-054 not found in domain 171

In the vmkernel.log file, you see entries similar to:

2018-06-08T05:40:53.264Z cpu49:68763 opID=4c6a367c)World: 12235: VC opID d03205b-b9-17ed maps to vmkernel opID 4c6a367c
2018-06-08T05:40:53.264Z cpu49:68763 opID=4c6a367c)WARNING: Heap: 3534: Heap domainHeap-54 already at its maximum size. Cannot expand.

Increasing the FilePolicyMaxPolicies to 500 from default 256 returns the same issue:             vsish -e set /config/VmkAccess/intOpts/FilePolicyMaxPolicies 500

Virtual Machine terminates with the error message similar to:

Configuration file has unexpected changes. Virtual machine has been terminated. Unregister and re-register virtual machine if the configuration file is correct.

To bring this VM up, you should restart the ESXi management agents or un-register and re-register the VM back to inventory in VC.

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

Purpose

This article provides workaround to avoid the Proxy VM from entering into an invalid state.

Cause

A logical error leads to accumulation of entries in a kernel heap of a fixed size. For a proxy VM that performs numerous disk hot-add, eventually the heap space is exhausted. This results with incorrect policy for the VM and causes the management software to terminate the VM.

Resolution

This issue is resolved in ESXi 6.5 P03 and ESXi 6.7 U1. To download go to Customer Connect download

Workaround

To work around this issue:

Migrate the proxy VM periodically to clear up stale security policy rules.

Reload the proxy VM after it is migrated by running the following command in the ESXi shell:

vim-cmd vmsvc/reload <vmid>

Where, <vmid> is the managed object ID of the VM on the host, and can be obtained using the vim-cmd vmsvc/getallvms command.

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
•
MSCS VM で vMotion が発生すると ESXi 6.0 および 6.5 ホストが PSOD - "SCSI_DeviceClusteringClearState" で停止する。 (56492)

KB
•
Download and Install VMware Fusion (2014097)

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 ESXi

Related Versions:

Take Our Survey

Support Assistant