Loading

×Sorry to interrupt
CSS Error

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

Rebooting an ESX host and restarting the Management agents takes longer than normal (1014270)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 35804Language:
JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

ESX host reboot is slow.

Restarting the Management agents takes up to 10 minutes.

Note: For more information about starting Management agents, see Restarting the Management agents on an ESX or ESXi Server (1003490) .

The /var/log/vmware/hostd.log contains entries similar to:

2009-07-28 18:05:37.048 F64BDB90 warning 'Proxysvc Req00002' Connection to localhost:8309 failed with error N7Vmacore15SystemExceptionE(Connection refused).

In the hostd.log file, you see a log spew with the error:

[2010-09-29 23:17:00.591 F5804B90 warning 'Proxysvc Req00008'] Error reading from client while waiting for header: N7Vmacore15SystemExceptionE(Connection reset by peer)

Resolution

This issue occurs when ESX does not have access to a DNS server. This may be the case if the ESX host is in a DMZ network or if the DNS servers used by ESX are running on virtual machines that are not powered on.

To resolve this issue:

Open /etc/resolv.conf in a text editor. For more information, see Editing files on an ESX host using vi or nano (1020302).

Comment out nameserver entries by placing a # in front of the entry. This prevents the ESX host from attempting to contact the DNS servers and allows it to boot.

Save and close the file.

Verify that the DNS Server IP in the /etc/resolv.conf file is valid by pinging the server. For more information, see Testing network connectivity with the Ping command (1003486).

When the entry has been verified, correct the nameserver entry using a text editor.

Restart the hostd service. For more information, see Restarting the Management agents on an ESX or ESXi Server (1003490).

Note: If you are running ESX 3.0.x or earlier, see Virtual Machines Unexpectedly Reboot after Issuing the "mgmt-vmware restart" Command (7301769).

To prevent this issue in the future, you can manually set up name resolution on the ESX host itself without the presence of a DNS server. For more information, see Identifying issues with and setting up name resolution on ESX Server (1003735).

Related Information

ESX ホストと管理エージェントの再起動に通常よりも時間がかかる

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

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 ESX Server

Related Versions:

VMware ESX 4.1.x

VMware ESX 4.0.x

Take Our Survey

Support Assistant