9 Replies Latest reply on May 15, 2018 2:19 PM by r0j

    vRA buggered bad - root / full, services no status, error 404s

    5mall5nail5 Enthusiast

      Hey all -

       

      Went into our non-load balanced vRA setup to find some funkiness in the UI about Model Manager within the Infrastructure tab.  I rebooted the IaaS VM and the error persisted.  So, I rebooted the vRA appliance.

       

      Coming back up, elastisearch came by saying it could not start and other services either took a long time or did not start.  Once up, I logged in as root and check disk space with df -h to find that / was full.  I added a disk to the VM, took a snapshot, and moved some log files - /var/log was 35G.  Rebooted, figured everything would be fine, except it's still not happy.

       

      I spent a couple hours searching logs for blatant errors but everything is pretty generic.  When I try to log into https://fqdn-vra/ I get the "VMware vRealize Automation Appliance" page.  So that works.  When I click the "vRealize Automation console" link I get a page with a heading "Identity Manager" and "The page you were looking for is not available. You may need to contact your administrator with this error: 404 Page Not Found."

       

      So, clearly vIDM or whatever is not running.  Checking services on https://fqdn-vra:5480 is full of a bunch of FAILED and no status.


      Failed:

      branding-service

      console-proxy-service

      container-service

      content-management

      forms-service

      healthbroker-proxy-server

      management-service

      portal-service

      properties-service

      release-management

      reservation-service

      shell-ui-app

       

      Registered:

      component-registry

      licensing-service

      plugin-service

      pricing-api

      vcbm-service

       

      Everything else has no status.

       

      Right now, at this point, / has 10% free, so I don't think it's a disk space issue any longer.  All of the other mount points in df -h have very low % utilized.

       

      in VAMI under vRA Host Settings, the cert is not expired, SSO info says "Configured - working connected", the DB is connected, under licensing it shows "Error connecting to server. Is vRA running?"

       

      Maybe someone has seen this before or is good at troubleshooting vRA?  Appreciate any help!