Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

After restarting the vCenter Server Appliance one or more services may fail to start. (59476)

Last Updated: 1/8/2019Categories: TroubleshootingTotal Views: 15237Language:
Chinese (Simplified)JapaneseEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

vCenter service is not starting

VAMI page reports Health Status in an "Unknown" state

DNS and NTP and root password expiry settings seems to have reverted to default settings

The VCSA vami.log showed the below errors:

2018-10-19T06:04:34.292 [1448]ERROR:root:SSO initialization error: [Errno 99] Cannot assign requested address

vpxd.log shows that the vpxd service is trying to bind to an empty loopback address

2018-10-19T05:46:40.115Z info vpxd[7FAB99932700] [Originator@6876 sub=AuthzStorageProvider] [AuthzStorageProvider::WaitForUpdate] Got exception  from WaitForNexUpdate(): N7Vmacore4Http24MalformedHeaderExceptionE(Server closed connection after 0 response bytes read; <io_obj p:0x0000003e53416d90, h:14, <TCP '[::1]:56772'>, <TCP '[::1]:10080'>>)
--> [context]zKq7AVECAAAAADWhbAAPdnB4ZAAAeF4rbGlidm1hY29yZS5zbwAAEBcbAMppGABIBBwApVwdAG1fHQAc7B0ArocaAAb6JQAe4SMAR6wjAC6vIwA3tysBVHQAbGlicHRocmVhZC5zby4wAAIdjA5saWJjLnNvLjYA[/context]
2018-10-19T05:46:40.292Z error vpxd[7FAB99932700] [Originator@6876 sub=httpUtil] [HttpUtil::ExecuteRequest] Error in sending request - Connection reset by peer
2018-10-19T05:46:40.292Z error vpxd[7FAB99932700] [Originator@6876 sub=ServerAccess] Exception while invoking remote login: N3Vim5Fault9HttpFault9ExceptionE(vim.fault.HttpFault)
--> [context]zKq7AVECAAAAADWhbAASdnB4ZAAAeF4rbGlidm1hY29yZS5zbwAAEBcbAMppGAEO01R2cHhkAAHcBIkBDQyJAUUQ9gE2EvYBkhL2ARET9gFCjKICuBwBbGliYXV0aHpjbGllbnQuc28AAsvUAQBHrCMALq8jADe3KwNUdABsaWJwdGhyZWFkLnNvLjAABB2MDmxpYmMuc28uNgA=[/context]
2018-10-19T05:46:40.439Z warning vpxd[7FAB9B76E700] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x00007fab4823d880, h:12, <TCP '0.0.0.0:0'>, <TCP '[::1]:10080'>>, e: system:111(Connection refused)
2018-10-19T05:46:40.439Z warning vpxd[7FAB99932700] [Originator@6876 sub=VpxdAuthClient] [ConnectAndLogin] Failed to loginBySamlToken: N7Vmacore15SystemExceptionE(Connection refused)
--> [context]zKq7AVECAAAAADWhbAAPdnB4ZAAAeF4rbGlidm1hY29yZS5zbwAAEBcbAMppGADIHysAcRUjAD4eJgAyICYAjT4mAG5KJgDL4CMAR6wjAC6vIwA3tysBVHQAbGlicHRocmVhZC5zby4wAAIdjA5saWJjLnNvLjYA[/context]
2018-10-19T05:46:40.440Z info vpxd[7FAB99932700] [Originator@6876 sub=VpxdAuthClient] fallback to loginByCertificate
2018-10-19T05:46:40.440Z warning vpxd[7FAB9B76E700] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x00007fab4836b010, h:12, <TCP '0.0.0.0:0'>, <TCP '[::1]:10080'>>, e: system:111(Connection refused)
2018-10-19T05:46:40.440Z error vpxd[7FAB99932700] [Originator@6876 sub=httpUtil] [HttpUtil::ExecuteRequest] Error in sending request - Connection refused

Cause

The /etc/hosts file was missing the IPV4 loopback address and localhost entries which caused the services to fail.

$ cat /etc/hosts
# Begin /etc/hosts (network card version)

# End /etc/hosts (network card version)
# VAMI_EDIT_BEGIN
# Generated by Studio VAMI service. Do not modify manually.
192.168.2.11 vc01.test.local vc01
# VAMI_EDIT_END
::1 localhost.localdom localhost

Resolution

Update the /etc/hosts file with the IPV4 loopback address 127.0.0.1 and localhost entries similar to the below.

$ cat etc/hosts
# Begin /etc/hosts (network card version)
127.0.0.1  vc01.test.local vc01  localhost
# End /etc/hosts (network card version)
# VAMI_EDIT_BEGIN
# Generated by Studio VAMI service. Do not modify manually.
192.168.2.11 vc01.test.local vc01
# VAMI_EDIT_END
::1 localhost.localdom localhost

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

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