For troubleshooting and maintenance purposes, it may be necessary to change the status of VMware vCloud Director service.
If you want to start the VMware vCloud Director service without rebooting the host, you can start them yourself any time after the configuration script has completed.
To manually start or restart the VMware vCloud Director service:
- Log in to the target host as root.
- Open a console, shell, or terminal window and run the appropriate command.
- To start the VMware vCloud Director service, run the command:
[root@vcloud-http /]# service vmware-vcd start
Starting vmware-vcd-watchdog: [ OK ]
Starting vmware-vcd-cell [ OK ]
- To check the status of the VMware vCloud Director service, run the command:
[root@vcloud-http /]# service vmware-vcd status
- To stop the VMware vCloud Director service, run the command:
[root@vcloud-http /]# service vmware-vcd stop
If the VMware vCloud Director service does not start:
- Check the status of VMware vCloud Director.
- Change ( cd) to the /opt/vmware/cloud-director/logs for 1.x or /opt/vmware/vcloud-director/logs for 1.5.x and run the command:
# grep -i "Application Initialization" cell.log
You see the status of the VMware vCloud Director initializing as it loads the subsystems and a status of complete and the time taken to start.
Note: You may have to run this command a couple of times.
- Watch the percentage numbers increase as the different subsystems load. When you see the line Application Initialization: Complete. Server is ready in X:XX (minutes:seconds), VMware vCloud Director has loaded successfully.
- Check that the VMware vCloud Director processes are running by running the command:
# ps -ef | grep vcloud
- Check the runlevel information for VMware vCloud Director by running the command:
# chkconfig --list | grep -i vmware-vcd
vmware-vcd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
- Ensure that a vcloud user has been created in /etc/passwd , /etc/group , and /etc/shadow .