{"id":343,"date":"2020-08-23T21:13:25","date_gmt":"2020-08-23T19:13:25","guid":{"rendered":"http:\/\/www.gerjon.com\/?p=343"},"modified":"2020-08-23T21:33:38","modified_gmt":"2020-08-23T19:33:38","slug":"vmware-vcenter-7-0-no-healthy-upstream-server","status":"publish","type":"post","link":"https:\/\/www.gerjon.com\/?p=343","title":{"rendered":"VMware vCenter 7.0 &#8220;no healthy upstream server&#8221;"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Background<\/h2>\n\n\n\n<p>So recently I was updating my homelab with ESX 7.0 and a brand spanking new vCenter install. I choose to completely wipe my old homelab on the ESX environment and completely reinstall it. <\/p>\n\n\n\n<p>I started with the ESX installation through this manual (<a rel=\"noreferrer noopener\" href=\"https:\/\/kb.vmware.com\/s\/article\/2004784\" target=\"_blank\">https:\/\/kb.vmware.com\/s\/article\/2004784<\/a>) and deployed a domain controller on the new VMware host.<\/p>\n\n\n\n<p>So when the domain controller was up and running and all was well I started deploying the vCenter appliance using this manual <a rel=\"noreferrer noopener\" href=\"http:\/\/(http:\/\/arnaudpain.com\/2020\/05\/26\/vmware-vcenter-7-0-install-step-by-step\/#sthash.Zk3q8m3p.dpbs\" target=\"_blank\">(http:\/\/arnaudpain.com\/2020\/05\/26\/vmware-vcenter-7-0-install-step-by-step\/#sthash.Zk3q8m3p.dpbs<\/a>).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problem<\/h2>\n\n\n\n<p>This worked and now I wanted to configure the vCenter. so browsed to the site.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" width=\"932\" height=\"366\" src=\"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/Vcenter-start.png?resize=932%2C366&#038;ssl=1\" alt=\"\" class=\"wp-image-345\" srcset=\"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/Vcenter-start.png?w=960&amp;ssl=1 960w, https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/Vcenter-start.png?resize=300%2C118&amp;ssl=1 300w, https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/Vcenter-start.png?resize=768%2C302&amp;ssl=1 768w\" sizes=\"auto, (max-width: 932px) 100vw, 932px\" \/><\/figure>\n\n\n\n<p>After starting the HTML5 client I got this error:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" width=\"461\" height=\"86\" src=\"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/no-healthy-upstream.png?resize=461%2C86&#038;ssl=1\" alt=\"\" class=\"wp-image-346\" srcset=\"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/no-healthy-upstream.png?w=461&amp;ssl=1 461w, https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/no-healthy-upstream.png?resize=300%2C56&amp;ssl=1 300w\" sizes=\"auto, (max-width: 461px) 100vw, 461px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting tips<\/h2>\n\n\n\n<p>Trying to figure out what was wrong I logged on the administration site and checked if all services where running you can do this with the following steps<\/p>\n\n\n\n<p>1.log in&nbsp;<a href=\"https:\/\/vcfqdn:5480\/\">https:\/\/VCFQDN:5480<\/a>&nbsp;&nbsp; check if the services VMware vCenter Server , an VMware vSphere Client are running<\/p>\n\n\n\n<p>2. if VMware vSphere Client service can not start , check the <strong>var\/log\/vmware\/vsphere-ui\/logs\/*runtime.log.stderr<\/strong> logfile<\/p>\n\n\n\n<p>It could also be a problem with the SSL certificate expiring, then the STS service will probably fail. \\sso check the certificates (which is always a good tip :-))!<\/p>\n\n\n\n<p>Otherwise there could be a problem with free diskspace on the vCenter appliance, you can check that by connecting via SSH to the vCenter appliance and pasting this command: (after getting shell access)<\/p>\n\n\n\n<p><strong>hostname -f &amp;&amp; date &amp;&amp; uptime &amp;&amp; vpxd -vl &amp;&amp; chage -l root &amp;&amp; df -h &amp;&amp; service-control &#8211;status.<\/strong> <\/p>\n\n\n\n<p>It should give enough room on all volumes e.g. like this screenshot. If one of the disks is full it will give 100% in use. then you need to enlarge the disk (or figure out why it&#8217;s full ;-))<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" width=\"754\" height=\"527\" src=\"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-3.png?resize=754%2C527&#038;ssl=1\" alt=\"\" class=\"wp-image-353\" srcset=\"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-3.png?w=754&amp;ssl=1 754w, https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-3.png?resize=300%2C210&amp;ssl=1 300w\" sizes=\"auto, (max-width: 754px) 100vw, 754px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Solution<\/h2>\n\n\n\n<p>After some searching online and checking with one of the vExperts (@<a rel=\"noreferrer noopener\" href=\"https:\/\/twitter.com\/laurensvanduijn\" target=\"_blank\">laurensvanduijn<\/a> thanks for the tip!)  it was (as always) DNS. Before configuring the vCenter applicance you need a valid DNS record for the vCenter pointing to the correct IP adress (which i had).<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" width=\"930\" height=\"641\" src=\"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-1.png?resize=930%2C641&#038;ssl=1\" alt=\"\" class=\"wp-image-349\" srcset=\"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-1.png?w=930&amp;ssl=1 930w, https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-1.png?resize=300%2C207&amp;ssl=1 300w, https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-1.png?resize=768%2C529&amp;ssl=1 768w\" sizes=\"auto, (max-width: 930px) 100vw, 930px\" \/><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p>And a valid PTR record in DNS for the vCenter appliance (which i didn&#8217;t have). <\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" width=\"826\" height=\"232\" src=\"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-2.png?resize=826%2C232&#038;ssl=1\" alt=\"\" class=\"wp-image-350\" srcset=\"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-2.png?w=826&amp;ssl=1 826w, https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-2.png?resize=300%2C84&amp;ssl=1 300w, https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2020\/08\/image-2.png?resize=768%2C216&amp;ssl=1 768w\" sizes=\"auto, (max-width: 826px) 100vw, 826px\" \/><\/figure>\n\n\n\n<p>These things need to be in place <strong>BEFORE<\/strong> deploying the vCenter appliance, adding them afterwards didn&#8217;t solve my issue. So after creating the PTR record in DNS and redeploying the vCenter appliance. It started working as expected!<\/p>\n\n\n\n<p>flowchart for future reference \ud83d\ude42 <\/p>\n\n\n\n<figure class=\"wp-block-image\"><img data-recalc-dims=\"1\" decoding=\"async\" src=\"https:\/\/i0.wp.com\/talesofatech.com\/wp-content\/uploads\/2017\/03\/YKvOiA4.png?w=932&#038;ssl=1\" alt=\"\"\/><\/figure>\n\n\n\n<p>Flowchart created by Mike S. (<a rel=\"noreferrer noopener\" href=\"https:\/\/talesofatech.com\/2017\/03\/rule-1-its-always-dns\" target=\"_blank\">https:\/\/talesofatech.com\/2017\/03\/rule-1-its-always-dns<\/a>\/)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Background So recently I was updating my homelab with ESX 7.0 and a brand spanking new vCenter install. I choose to completely wipe my old homelab on the ESX environment and completely reinstall it. I &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,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[14],"tags":[],"class_list":["post-343","post","type-post","status-publish","format-standard","hentry","category-vmware"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p59CpB-5x","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts\/343","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=343"}],"version-history":[{"count":0,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts\/343\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=343"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=343"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=343"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}