{"id":141,"date":"2018-10-19T09:43:28","date_gmt":"2018-10-19T07:43:28","guid":{"rendered":"https:\/\/vmoller.dk\/?p=141"},"modified":"2018-10-19T09:47:22","modified_gmt":"2018-10-19T07:47:22","slug":"vmware-appliance-management-interface-vami-unable-to-login","status":"publish","type":"post","link":"https:\/\/vmoller.dk\/index.php\/2018\/10\/19\/vmware-appliance-management-interface-vami-unable-to-login\/","title":{"rendered":"VMware Appliance Management Interface (VAMI) \u2013 Unable to login"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-143 size-full\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc1.jpg\" alt=\"\" width=\"457\" height=\"391\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc1.jpg 457w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc1-300x257.jpg 300w\" sizes=\"auto, (max-width: 457px) 100vw, 457px\" \/><\/p>\n<p>This morning I faced a strange issue in my vSphere Lab when a wanted to login to VAMI interface \u2013 of course to install the newly released \u201cvSphere 6.7 U1\u201d update.<\/p>\n<p>I opened the VAMI URL for my Platform service controller (PSC): https:\/\/&lt;FQDN&gt;:5480 and typed in my root credentials as a normally would. However, the only thing that showed on the screen was a message saying: \u201cUnable to login\u201d.<\/p>\n<p>After this I tried to type in my password multiple times to make sure that I was actually typing in the correct one, but still, I just got the same error message.<\/p>\n<p><!--more-->Next, logically step for me was to try to same credentials on the console of the PSC, so I opened my vCenter (that actually still worked!), located my PSC and accessed the console from there. At my first attempt my root password was actually rejected (I might type it in wrong) but second attempt actually let me log in.<\/p>\n<p>From there I saw the message &#8220;[ERROR]: Failed to connect to service.&#8221; and that gave me a clue that some services was not running as intended!<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-144 size-full\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc2.jpg\" alt=\"\" width=\"445\" height=\"235\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc2.jpg 445w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc2-300x158.jpg 300w\" sizes=\"auto, (max-width: 445px) 100vw, 445px\" \/><\/p>\n<p>In the console, I tried to list all the services using this command:<\/p>\n<blockquote>\n<pre>service-control --status<\/pre>\n<\/blockquote>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-145 size-full\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc3.jpg\" alt=\"\" width=\"803\" height=\"119\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc3.jpg 803w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc3-300x44.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc3-768x114.jpg 768w\" sizes=\"auto, (max-width: 803px) 100vw, 803px\" \/><\/p>\n<p>And there I could actually see that \u201capplmngt\u201d and \u201cvmware-statsmonitor\u201d services was actually stopped.<\/p>\n<p>I typed the following command to start all services that where not in the running state:<\/p>\n<blockquote>\n<pre>service-control --start --all<\/pre>\n<\/blockquote>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-146\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc4-300x195.jpg\" alt=\"\" width=\"300\" height=\"195\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc4-300x195.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/10\/psc4.jpg 476w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/p>\n<p>After that, login on the VAMI web interface worked again! Hooray!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This morning I faced a strange issue in my vSphere Lab when a wanted to login to VAMI interface \u2013 of course to install the newly released \u201cvSphere 6.7 U1\u201d update. I opened the VAMI URL for my Platform service controller (PSC): https:\/\/&lt;FQDN&gt;:5480 and typed in my root credentials as a normally would. However, the [&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":[13,11,12,6,7],"tags":[14,24,15,4],"class_list":["post-141","post","type-post","status-publish","format-standard","hentry","category-vami","category-vcenter","category-vcsa","category-vmware","category-vsphere","tag-vami","tag-vcenter","tag-vcsa","tag-vsphere"],"_links":{"self":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/141","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/comments?post=141"}],"version-history":[{"count":4,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/141\/revisions"}],"predecessor-version":[{"id":149,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/141\/revisions\/149"}],"wp:attachment":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/media?parent=141"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/categories?post=141"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/tags?post=141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}