vmware-vcd-watchdog and vmware-vcd-cell services do not auto start on RHEL 7 server
search cancel

vmware-vcd-watchdog and vmware-vcd-cell services do not auto start on RHEL 7 server

book

Article ID: 343111

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction





Symptoms:
  • After rebooting the RHEL 7 server running vCloud Director 8.10, vmware-vcd-watchdog and vmware-vcd-cell services do not start automatically.
  • You can run the 'service vmware-vcd start' command successfully.


Environment

VMware Cloud Director for Service Provider 9.x
VMware Cloud Director for Service Provider 10.x

Cause

This issue occurs because the starting service on bootup has changed from /etc/init.d to systemctl in RHEL 7. Whereas, the VMware vCloud Director services are still in /etc/init.d (/etc/init.d/vmware-vcd) and the services do not start on OS bootup.

For more information, see the:
Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.

Resolution

Currently, there is no resolution.

To workaround this issue, create the script file to enable the vCloud director services:
  1. Create the /usr/lib/systemd/system/vmware-vcd.service file using text editor.
  2. Add these entries in the vmware-vcd.service file and save the file.

    [Unit]

    Description=VMware vCD services
    SourcePath=/etc/init.d/vmware-vcd

    [Service]
    Type=forking
    Restart=no
    TimeoutSec=5min
    IgnoreSIGPIPE=no
    KillMode=process
    GuessMainPID=no
    RemainAfterExit=yes
    ExecStart=/etc/init.d/vmware-vcd start
    ExecStop=/etc/init.d/vmware-vcd stop

    [Install]
    WantedBy=multi-user.target


  3. Run this command to enable the service:

    systemctl enable vmware-vcd

  4. Run this command to start the service:

    systemctl status vmware-vcd