VMware vCloud Director services do not start automatically upon a reboot
search cancel

VMware vCloud Director services do not start automatically upon a reboot

book

Article ID: 341489

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

The VMware vCloud Director (vmware-vcd) services do not start automatically after a reboot because of an issue in the systemd-219-19.el7 module of Red Hat Enterprise Linux 7.2. For further details, see Red Hat Bugzilla – Bug 1285492.


Environment

VMware Cloud Director for Service Provider 8.10.x

Resolution

Follow these steps to resolve the issue:

  1. Create a file similar to the following:

    $ cat /usr/lib/systemd/system/vmware-vcd.service

    [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


  2. Enable the service:

    $ systemctl enable vmware-vcd

  3. Start the service:

    $ systemctl start vmware-vcd


  4. Check the status:

    $ systemctl status vmware-vcd