Cloud Director vmware-vcd-watchdog not running

Products

• VMware Cloud Director

Issue/Introduction

• The vmware-vcd service fails after running for 1-3 hours.
• Listing the directories located in /var/lock does not list the /subsys directory.
• The service does restart after the systemctl start vmware-vcd command is run.
• Similar messages appear in the journalctl -u vmware-vcd output:
  
  Apr 30 19:34:55 vcd.example.com vmware-vcd[844981]: touch: cannot touch '/var/lock/subsys/vmware-vcd-watchdog': No such file or directory
  
  
• The /opt/vmware/vcloud-director/logs/vmware-vcd-watchdog.log only has one status check from the service start time, and does not perform additional status checks every 60 seconds as expected.

Environment

VMware Cloud Director 10.x

Cause

/var/lock/subsys directory does not exist on the Cloud Director Cell as it has manually been removed.

 

Resolution

To manually create the /var/lock/subsys directory:

• Open an SSH session to the affected VMware Cloud Director Cell and log in as root.
• Change directory to /var/lock by running the command:
  
  cd /var/lock
  
  
• Create the subsys directory by running the command:
  
  mkdir subsys
  
  
• Restart the vmware-vcd service.
  
  systemctl start vmware-vcd