1 2 Previous Next 25 Replies Latest reply on Aug 7, 2018 6:03 PM by neyla12 Go to original post
      • 15. Re: VCSA 6 disk full?
        daphnissov Guru
        Community WarriorsvExpert

        Are you not able to show the df -h results from a fully-booted appliance at this point?

        • 16. Re: VCSA 6 disk full?
          gregarican Novice

          Yes. I attached that a bit earlier. Attaching it again here. After rebooting the VCSA, now the /dev/sda3 shows 56% is use. And the /storage/log shows 87% in use. Which both I would presume are okay based on what I recall. But still not all VCSA services start successfully. When I issue the service-control --start --all command (since now I can run the shell either in a remote session or in the console) the services fail once they hit the VCSA inventory service. And none of the ones after that succeed either.

          • 17. Re: VCSA 6 disk full?
            daphnissov Guru
            vExpertCommunity Warriors

            Show output of du -sh * /storage/log

            • 18. Re: VCSA 6 disk full?
              gregarican Novice

              Here is a snippet of when I am starting all of the services from the CLI. It hits the inventory service and then chokes.



              DC-VCSA01:~ # service-control --start --all

              INFO:root:Service: vmafdd, Action: start

              Service: vmafdd, Action: start

              2018-01-22T17:50:56.781Z   Running command: ['/sbin/chkconfig', u'vmafdd']

              2018-01-22T17:50:56.815Z   Done running command

              2018-01-22T17:50:56.815Z   Running command: ['/sbin/service', u'vmafdd', 'status']

              2018-01-22T17:50:56.828Z   Done running command

              INFO:root:Service: vmware-rhttpproxy, Action: start

              Service: vmware-rhttpproxy, Action: start

              2018-01-22T17:50:56.829Z   Running command: ['/sbin/chkconfig', u'vmware-rhttpproxy']

              2018-01-22T17:50:56.863Z   Done running command

              2018-01-22T17:50:56.863Z   Running command: ['/sbin/service', u'vmware-rhttpproxy', 'status']

              2018-01-22T17:50:56.899Z   Done running command

              INFO:root:Service: vmdird, Action: start

              Service: vmdird, Action: start

              2018-01-22T17:50:56.900Z   Running command: ['/sbin/chkconfig', u'vmdird']

              2018-01-22T17:50:56.934Z   Done running command

              2018-01-22T17:50:56.934Z   Running command: ['/sbin/service', u'vmdird', 'status']

              2018-01-22T17:50:56.946Z   Done running command

              INFO:root:Service: vmcad, Action: start

              Service: vmcad, Action: start

              2018-01-22T17:50:56.947Z   Running command: ['/sbin/chkconfig', u'vmcad']

              2018-01-22T17:50:56.980Z   Done running command

              2018-01-22T17:50:56.980Z   Running command: ['/sbin/service', u'vmcad', 'status']

              2018-01-22T17:50:56.992Z   Done running command

              INFO:root:Service: vmware-sts-idmd, Action: start

              Service: vmware-sts-idmd, Action: start

              2018-01-22T17:50:56.993Z   Running command: ['/sbin/chkconfig', u'vmware-sts-idmd']

              2018-01-22T17:50:57.027Z   Done running command

              2018-01-22T17:50:57.027Z   Running command: ['/sbin/service', u'vmware-sts-idmd', 'status']

              2018-01-22T17:50:57.037Z   Done running command

              INFO:root:Service: vmware-stsd, Action: start

              Service: vmware-stsd, Action: start

              2018-01-22T17:50:57.038Z   Running command: ['/sbin/chkconfig', u'vmware-stsd']

              2018-01-22T17:50:57.072Z   Done running command

              2018-01-22T17:50:57.072Z   Running command: ['/sbin/service', u'vmware-stsd', 'status']

              2018-01-22T17:50:57.097Z   Done running command

              INFO:root:Service: vmware-cm, Action: start

              Service: vmware-cm, Action: start

              2018-01-22T17:50:57.097Z   Running command: ['/sbin/chkconfig', u'vmware-cm']

              2018-01-22T17:50:57.132Z   Done running command

              2018-01-22T17:50:57.132Z   Running command: ['/sbin/service', u'vmware-cm', 'status']

              2018-01-22T17:50:57.229Z   Done running command

              INFO:root:Service: vmware-cis-license, Action: start

              Service: vmware-cis-license, Action: start

              2018-01-22T17:50:57.230Z   Running command: ['/sbin/chkconfig', u'vmware-cis-license']

              2018-01-22T17:50:57.265Z   Done running command

              2018-01-22T17:50:57.265Z   Running command: ['/sbin/service', u'vmware-cis-license', 'status']

              2018-01-22T17:50:57.364Z   Done running command

              INFO:root:Service: vmware-psc-client, Action: start

              Service: vmware-psc-client, Action: start

              2018-01-22T17:50:57.364Z   Running command: ['/sbin/chkconfig', u'vmware-psc-client']

              2018-01-22T17:50:57.400Z   Done running command

              2018-01-22T17:50:57.400Z   Running command: ['/sbin/service', u'vmware-psc-client', 'status']

              2018-01-22T17:50:57.427Z   Done running command

              INFO:root:Service: vmware-sca, Action: start

              Service: vmware-sca, Action: start

              2018-01-22T17:50:57.428Z   Running command: ['/sbin/chkconfig', u'vmware-sca']

              2018-01-22T17:50:57.462Z   Done running command

              2018-01-22T17:50:57.462Z   Running command: ['/sbin/service', u'vmware-sca', 'status']

              2018-01-22T17:50:57.557Z   Done running command

              INFO:root:Service: applmgmt, Action: start

              Service: applmgmt, Action: start

              2018-01-22T17:50:57.558Z   Running command: ['/sbin/chkconfig', u'applmgmt']

              2018-01-22T17:50:57.592Z   Done running command

              2018-01-22T17:50:57.592Z   Running command: ['/sbin/service', u'applmgmt', 'status']

              2018-01-22T17:50:57.632Z   Done running command

              INFO:root:Service: vmware-netdumper, Action: start

              Service: vmware-netdumper, Action: start

              2018-01-22T17:50:57.632Z   Running command: ['/sbin/chkconfig', u'vmware-netdumper']

              2018-01-22T17:50:57.666Z   Done running command

              'vmware-netdumper' startMode is Manual, skipping to start:

              INFO:root:'vmware-netdumper' startMode is Manual, skipping to start:

              INFO:root:Service: vmware-syslog, Action: start

              Service: vmware-syslog, Action: start

              2018-01-22T17:50:57.666Z   Running command: ['/sbin/chkconfig', u'vmware-syslog']

              2018-01-22T17:50:57.700Z   Done running command

              2018-01-22T17:50:57.700Z   Running command: ['/sbin/service', u'vmware-syslog', 'status']

              2018-01-22T17:50:57.745Z   Done running command

              INFO:root:Service: vmware-syslog-health, Action: start

              Service: vmware-syslog-health, Action: start

              2018-01-22T17:50:57.746Z   Running command: ['/sbin/chkconfig', u'vmware-syslog-health']

              2018-01-22T17:50:57.780Z   Done running command

              2018-01-22T17:50:57.780Z   Running command: ['/sbin/service', u'vmware-syslog-health', 'status']

              2018-01-22T17:50:57.879Z   Done running command

              INFO:root:Service: vmware-vapi-endpoint, Action: start

              Service: vmware-vapi-endpoint, Action: start

              2018-01-22T17:50:57.880Z   Running command: ['/sbin/chkconfig', u'vmware-vapi-endpoint']

              2018-01-22T17:50:57.914Z   Done running command

              2018-01-22T17:50:57.914Z   Running command: ['/sbin/service', u'vmware-vapi-endpoint', 'status']

              2018-01-22T17:50:57.967Z   Done running command

              INFO:root:Service: vmware-vpostgres, Action: start

              Service: vmware-vpostgres, Action: start

              2018-01-22T17:50:57.967Z   Running command: ['/sbin/chkconfig', u'vmware-vpostgres']

              2018-01-22T17:50:58.001Z   Done running command

              2018-01-22T17:50:58.001Z   Running command: ['/sbin/service', u'vmware-vpostgres', 'status']

              2018-01-22T17:50:58.077Z   Done running command

              INFO:root:Service: vmware-invsvc, Action: start

              Service: vmware-invsvc, Action: start

              2018-01-22T17:50:58.078Z   Running command: ['/sbin/chkconfig', u'vmware-invsvc']

              2018-01-22T17:50:58.112Z   Done running command

              2018-01-22T17:50:58.113Z   Running command: ['/sbin/service', u'vmware-invsvc', 'status']

              2018-01-22T17:50:58.202Z   Done running command

              2018-01-22T17:50:58.202Z   Running command: ['/sbin/chkconfig', '--force', u'vmware-invsvc', 'on']

              2018-01-22T17:50:58.237Z   Done running command

              2018-01-22T17:50:58.237Z   Running command: ['/sbin/service', u'vmware-invsvc', 'start']

              2018-01-22T17:51:13.267Z   Done running command

              2018-01-22T17:51:13.267Z   Invoked command: ['/sbin/service', u'vmware-invsvc', 'start']

              2018-01-22T17:51:13.267Z   RC = 1

              Stdout = Starting VMware Inventory Service...

              Waiting for VMware Inventory Service.................

              WARNING: VMware Inventory Service may have failed to start.



              Stderr =

              2018-01-22T17:51:13.267Z   {

                  "resolution": null,

                  "detail": [


                          "args": [

                              "Command: ['/sbin/service', u'vmware-invsvc', 'start']\nStderr: "


                          "id": "install.ciscommon.command.errinvoke",

                          "localized": "An error occurred while invoking external command : 'Command: ['/sbin/service', u'vmware-invsvc', 'start']\nStderr: '",

                          "translatable": "An error occurred while invoking external command : '%(0)s'"



                  "componentKey": null,

                  "problemId": null


              ERROR:root:Unable to start service vmware-invsvc, Exception: {

                  "resolution": null,

                  "detail": [


                          "args": [



                          "id": "install.ciscommon.service.failstart",

                          "localized": "An error occurred while starting service 'vmware-invsvc'",

                          "translatable": "An error occurred while starting service '%(0)s'"



                  "componentKey": null,

                  "problemId": null


              Unable to start service vmware-invsvc, Exception: {

                  "resolution": null,

                  "detail": [


                          "args": [



                          "id": "install.ciscommon.service.failstart",

                          "localized": "An error occurred while starting service 'vmware-invsvc'",

                          "translatable": "An error occurred while starting service '%(0)s'"



                  "componentKey": null,

                  "problemId": null


              DC-VCSA01:~ #

              • 19. Re: VCSA 6 disk full?
                gregarican Novice

                Here are those results.

                • 20. Re: VCSA 6 disk full?
                  daphnissov Guru
                  Community WarriorsvExpert

                  Sorry, left off the trailing slash:  du -sh * /storage/log/

                  • 21. Re: VCSA 6 disk full?
                    gregarican Novice

                    That's okay. Thanks for all of the time! Here it is..

                    • 22. Re: VCSA 6 disk full?
                      gregarican Novice

                      Here's the latest time I checked the disk space, and then tried to start all of the VCSA's services. I finally broke down and opened up a trouble ticket with VMware. Since without the VCSA being fully functional I will be missing out of Veeam backups of the guest VM's. Don't want to risk that for any extended amount of time!

                      • 23. Re: VCSA 6 disk full?
                        gregarican Novice

                        Had to reset passwords. As in this -- VMware Knowledge Base . Now we are back in business. Keeping in mind the auto-generated passwords cannot contain certain special characters. If you paste them into the LDAP config file then it won't work. All working now!

                        • 24. Re: VCSA 6 disk full?
                          gregarican Novice

                          This was the other place where I had to reset the password. In this case the root password --> How to reset the root password for VCSA 6.x . What was odd is that I didn't think we set the root password to expire, and it's been the same for almost 2 years now. But after resetting it, then resetting the LDAP machine account password, updating that value in the EAM properties file, then restarting the VCSA services we are in the clear.

                          • 25. Re: VCSA 6 disk full?

                            Thanks for answering.










                            1 2 Previous Next