{"id":601,"date":"2012-06-11T11:16:10","date_gmt":"2012-06-11T18:16:10","guid":{"rendered":"http:\/\/inverseflux.com\/?p=601"},"modified":"2018-09-24T20:27:52","modified_gmt":"2018-09-25T03:27:52","slug":"vsphere-5-health-xml-error-503","status":"publish","type":"post","link":"http:\/\/inverseflux.com\/blog\/2012\/06\/vsphere-5-health-xml-error-503\/","title":{"rendered":"vSphere 5 &#8211; health.xml error 503"},"content":{"rendered":"<p>Well, it has been awhile since I&#8217;ve actually blogged anything. So, here we go!<\/p>\n<p>For a the past few days I&#8217;ve combating an issue upon upgrading to VMWare vSphere 5.0 &#8211; more specifically the Web Client (Server) install. After various upgrade issues, a ton of problems showed up which led to a fresh install. Post install, everything actually was working fine&#8230; except one thing: VMWare vSphere Profile-driven Storage Service, under Administration -&gt; vCenter Server Status would show error cannot reach http:\/\/localhost\/sps\/health.xml with everything else green.<\/p>\n<p>Check the logs on the vCenter server, vws.log shows:<\/p>\n<p>Server returned HTTP response code 503 for URL: http:\/\/localhost\/sps\/health.xml<\/p>\n<p>Restarts of entire server, services, etc were not fixing this. Started looking at config files to make changes&#8230; then it dawned on me. 503, it&#8217;s busy &#8211; meaning that port is in use, which it is and WORKING for the other services. So, rather then restarting ALL the services all at once&#8230; I restart JUST the &#8220;vSphere Web Client&#8221; and the error went away.<\/p>\n<p>This tells me, that the vSphere Web Client service was trying to load at an odd time\/before the web server was up.<\/p>\n<p>HTH.<\/p>\n<p>Cheers.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Well, it has been awhile since I&#8217;ve actually blogged anything. So, here we go! For a the past few days I&#8217;ve combating an issue upon upgrading to VMWare vSphere 5.0 &#8211; more specifically the Web Client (Server) install. After various upgrade issues, a ton of problems showed up which led to a fresh install. Post [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[5,8],"tags":[30,74,75,76],"class_list":["post-601","post","type-post","status-publish","format-standard","hentry","category-general","category-techno","tag-error-503","tag-vmware","tag-vsphere","tag-vsphere-web-client"],"_links":{"self":[{"href":"http:\/\/inverseflux.com\/blog\/wp-json\/wp\/v2\/posts\/601","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/inverseflux.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/inverseflux.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/inverseflux.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/inverseflux.com\/blog\/wp-json\/wp\/v2\/comments?post=601"}],"version-history":[{"count":1,"href":"http:\/\/inverseflux.com\/blog\/wp-json\/wp\/v2\/posts\/601\/revisions"}],"predecessor-version":[{"id":919,"href":"http:\/\/inverseflux.com\/blog\/wp-json\/wp\/v2\/posts\/601\/revisions\/919"}],"wp:attachment":[{"href":"http:\/\/inverseflux.com\/blog\/wp-json\/wp\/v2\/media?parent=601"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/inverseflux.com\/blog\/wp-json\/wp\/v2\/categories?post=601"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/inverseflux.com\/blog\/wp-json\/wp\/v2\/tags?post=601"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}